Seaf-server not running after upgrade to pro 7.0.8

Hi all,

I am running a seafile pro cluster, just upgraded it from 6.2.4 to 7.0.8. I did run the upgrade scripts and made sure to upgrade to openjdk8. I see the following in the controller.log, every 10m seconds:

[09/02/19 15:57:23] seafile-controller.c(594): pid file /srv/seafile/pids/ does not exist
[09/02/19 15:57:23] seafile-controller.c(616): seaf-server need restart…
[09/02/19 15:57:23] Disconnected from daemon
[09/02/19 15:57:23] seafile-controller.c(688): restarting ccnet server …
[09/02/19 15:57:23] seafile-controller.c(190): starting ccnet-server …
[09/02/19 15:57:23] seafile-controller.c(94): spawn_process: ccnet-server -F /srv/seafile/conf -c /srv/seafile/ccnet -f /srv/seafile/logs/ccnet.log -d -L /srv/seafile -P /srv/seafile/pids/
[09/02/19 15:57:23] seafile-controller.c(109): spawned ccnet-server, pid 16850
[09/02/19 15:57:23] net.c(200): bind fails: Address already in use
[09/02/19 15:57:23] seafile-controller.c(923): Failed to bind health check port 11001: Address already in use.
[09/02/19 15:57:24] seafile-controller.c(781): ccnet daemon connected.
[09/02/19 15:57:24] seafile-controller.c(224): starting seaf-server …
[09/02/19 15:57:24] seafile-controller.c(94): spawn_process: seaf-server -F /srv/seafile/conf -c /srv/seafile/ccnet -d /srv/seafile/seafile-data -l /srv/seafile/logs/seafile.log -P /srv/seafile/pids/ -f -L /srv/seafile
[09/02/19 15:57:24] seafile-controller.c(109): spawned seaf-server, pid 16853
[09/02/19 15:57:24] seafile-controller.c(605): path /proc/16838 doesn’t exist, restart progress [3]
[09/02/19 15:57:24] seafile-controller.c(94): spawn_process: /usr/bin/python2.7 -m seafevents.main --config-file /srv/seafile/conf/seafevents.conf --logfile /srv/seafile/logs/seafevents.log -P /srv/seafile/pids/
[09/02/19 15:57:24] seafile-controller.c(109): spawned /usr/bin/python2.7, pid 16854
[09/02/19 15:57:24] seafile-controller.c(749): seafdav is not enabled

seaf-server appears to be crashing. however I was not able yet to find out why.

I am running seafile on debian jessie, before the upgrade without problems.

any hints welcome.


It’s look like you didn’t stop server before upgrade or shutdown script not worked. It’s saying that seafile server already running on PIDs 16850, 16853, 16854 and of course port 110001 is used.

thanks for your answer. I agree, the log file seems to suggest that. the problem, however, was that was missing on my system. (hint: running prints error messages for such library problems).