I hope we have a plugin for Pydio or something better if OwnCloud cease to exist one day.
Pydio plugin won't come from me. I don't like it at all. That is why I wrote the plugin for syncthing (I know it isn't quite the same).
I hope we have a plugin for Pydio or something better if OwnCloud cease to exist one day.
Pydio plugin won't come from me. I don't like it at all. That is why I wrote the plugin for syncthing (I know it isn't quite the same).
I tried below command and got the following statement:
I managed in the meantime to run the command, but still Seafile doesn't boot by start.
Can you take a look in /etc/rc3.d again?
S0xmysql should be before S0yseafile-server, i.e x should be lower than y.
Are you sure, you have the same mysql error in the logs as mentioned before?
Does
or
really start seafile for you?
root@NAS:~# ls /etc/rc3.d/
K01cpufrequtils S01samba S02smartmontools
K01loadcpufreq S01sudo S02ssh
K01rsync S01wd_keepalive S03avahi-daemon
K02nfs-kernel-server S02acpid S03bootlogs
K02proftpd S02anacron S03postfix
K02snmpd S02collectd S03seafile-server
K02tftpd-hpa S02cron S15rpcbind
README S02dbus S16nfs-common
S01couchpotato S02ddclient S16quotarpc
S01crashplan S02mdadm S17monit
S01headphones S02mysql S17openmediavault-beep
S01motd S02nginx S17rc.local
S01php5-fpm S02ntp S17rmnologin
S01rrdcached S02openmediavault-engined S17stop-bootlogd
S01rsyslog S02openvpnas S17watchdog
S01sabnzbd S02plexmediaserver
Alles anzeigen
Well I know it because when the server isn't running and I try both commands nothing happen. Please find attached the seafile.log
Hi Guys, do I really need to re-install OMV from Scratch to get Seafile running?
From the logs it looks like you started seafile successfully yesterday evening:
[05/25/16 22:25:44] ../common/session.c(132): using config file /root/seafile/conf/ccnet.conf
SQLException: Failed to start connection pool -- Lost connection to MySQL server at 'reading initial communication packet', system error: 111
raised in ConnectionPool_start at src/db/ConnectionPool.c:287
-e
About to perform stop for seafile at 2016-05-26T21:05:42+0200
Stopping seafile server ...
Done.
-e
About to perform start for seafile at 2016-05-26T21:07:13+0200
[05/26/16 21:07:14] ../common/session.c(132): using config file /root/seafile/conf/ccnet.conf
Starting seafile server, please wait ...
Seafile server started
Done.
Alles anzeigen
Still having problems?
But I can't get the WEB UI shown when calling 192.168.xx.100:8000
I'm having the same problem, won't start on boot. I've not proceeded past step 3 (ie, SSL)... this is the most recent incarnation. Starts fine w/o error when I start it manually, just won't start on boot.
#!/bin/sh
### BEGIN INIT INFO
# Provides: seafile-server
# Required-Start: $local_fs $remote_fs $network mysql
# Required-Stop: $local_fs mysql
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Starts Seafile Server
# Description: starts Seafile Server
### END INIT INFO
# Change the value of "user" to your linux user name
user=root
# Change the value of "script_path" to your path of seafile installation
# usually the home directory of $user
seafile_dir=/root/seafile
script_path=${seafile_dir}/seafile-server-latest
seafile_init_log=${seafile_dir}/logs/seafile.init.log
seahub_init_log=${seafile_dir}/logs/seahub.init.log
# Change the value of fastcgi to true if fastcgi is to be used
fastcgi=false
# Set the port of fastcgi, default is 8000. Change it if you need different.
fastcgi_port=8000
#
# Write a polite log message with date and time
#
echo -e "\n \n About to perform $1 for seafile at `date -Iseconds` \n " >> ${seafile_init_log}
echo -e "\n \n About to perform $1 for seahub at `date -Iseconds` \n " >> ${seahub_init_log}
case "$1" in
start)
sudo -u ${user} ${script_path}/seafile.sh ${1} >> ${seafile_init_log}
if [ $fastcgi = true ];
then
sudo -u ${user} ${script_path}/seahub.sh ${1}-fastcgi ${fastcgi_port} >> ${seahub_init_log}
else
sudo -u ${user} ${script_path}/seahub.sh ${1} >> ${seahub_init_log}
fi
;;
restart)
sudo -u ${user} ${script_path}/seafile.sh ${1} >> ${seafile_init_log}
if [ $fastcgi = true ];
then
sudo -u ${user} ${script_path}/seahub.sh ${1}-fastcgi ${fastcgi_port} >> ${seahub_init_log}
else
sudo -u ${user} ${script_path}/seahub.sh ${1} >> ${seahub_init_log}
fi
;;
stop)
sudo -u ${user} ${script_path}/seahub.sh ${1} >> ${seahub_init_log}
sudo -u ${user} ${script_path}/seafile.sh ${1} >> ${seafile_init_log}
;;
*)
echo "Usage: /etc/init.d/seafile-server {start|stop|restart}"
exit 1
;;
esac
Alles anzeigen
KM0201, Do you mean to say you are using the latest Seafile or the one in the Guide?
KM0201, Do you mean to say you are using the latest Seafile or the one in the Guide?
The one in the guide... I assumed that was the newest I've been meaning to try this for a while and kept putting it off, and finally had a day to mess w/ it.
I haven't updated the guide since it was created. I've been testing the version in the guide (seafile-server_5.0.4) on a new clean updated OMV 2.2.4 and it works well. I will test the latest Seafile next (if there is a later one!)
I would recommend to anyone following the guide to use the Seafile version in the guide till ive updated it.
Also, fastcgi needs to be set to false until part 4 of the guide otherwise the GUI wont load in your browser on port 8000.
The MySQL settings Zoki recommended earlier had no effect on my system, I suppose it may help others.
Alles anzeigenI haven't updated the guide since it was created. I've been testing the version in the guide (seafile-server_5.0.4) on a new clean updated OMV 2.2.4 and it works well. I will test the latest Seafile next (if there is a later one!)
I would recommend to anyone following the guide to use the Seafile version in the guide till ive updated it.
Also, fastcgi needs to be set to false until part 4 of the guide otherwise the GUI wont load in your browser on port 8000.
The MySQL settings Zoki recommended earlier had no effect on my system, I suppose it may help others.
I used the guide version.... When I said the "latest incarnation" I meant that was the latest startup script I had tried.... fastcgi is set to false. I think whatever is wrong, is wrong w/ the script... the server starts just fine, runs fine, etc.. if I start it manually... but obviously I'd like it to start on boot.. and that is the issue.
My observations are when doing below command:
8. Start the Seafile Server:cd /root/seafile/seafile-server-* (if not already in that location)
./seafile.sh start
./seahub.sh start
I can reach the server also via http://local-IP:8000 and it doesn't matter if I have fastcgi set to true or false.
So let me explain what is happening:
My MySQL server starts after Seafile and I don't have any problems but I suppose It can't hurt to add it to the script anyway.
root@OMV-TEST-VM-2:~# ls /etc/rc3.d/
K01ntp S01seafile-server S03bootlogs
K01rsync S01sudo S03cpufrequtils
K02nfs-kernel-server S01wd_keepalive S04collectd
K02postfix S02acpid S15rpcbind
K02proftpd S02anacron S16nfs-common
K02samba S02cron S16quotarpc
K02smartmontools S02dbus S17monit
K02snmpd S02loadcpufreq S17openmediavault-beep
K02tftpd-hpa S02mdadm S17rc.local
README S02mysql S17rmnologin
S01motd S02nginx S17stop-bootlogd
S01php5-fpm S02openmediavault-engined S17watchdog
S01rrdcached S02ssh
S01rsyslog S03avahi-daemon
root@OMV-TEST-VM-2:~#
Alles anzeigen
Strange! The init script starts seafile.sh which opens a connection to the database.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!