Seafdav.pid does not exist after CentOS Update

Just updated my CentOS 7.4 to 7.5 without touching Seafile-Server ver. 6.2.2 configuration.
For now the /opt/seafile-server/logs/controller.log filled by:

[05/29/18 19:54:18] seafile-controller.c(186): starting seaf-server ...
[05/29/18 19:54:18] seafile-controller.c(73): spawn_process: seaf-server -F /opt/seafile-server/conf -c /opt/seafile-server/ccnet -d /opt/seafile-server/seafile-data -l /opt/seafile-server/logs/seafile.log -P /opt/seafile-server/pids/seaf-server.pid
[05/29/18 19:54:18] seafile-controller.c(88): spawned seaf-server, pid 8854
[05/29/18 19:54:18] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/29/18 19:54:18] seafile-controller.c(73): spawn_process: /usr/bin/python2.7 -m wsgidav.server.run_server --log-file /opt/seafile-server/logs/seafdav.log --pid /opt/seafile-server/pids/seafdav.pid --port 8080 --host 127.0.0.1
[05/29/18 19:54:18] seafile-controller.c(88): spawned /usr/bin/python2.7, pid 8855
[05/29/18 19:54:28] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/29/18 19:54:28] seafile-controller.c(422): seafdav need restart...
[05/29/18 19:54:28] seafile-controller.c(73): spawn_process: /usr/bin/python2.7 -m wsgidav.server.run_server --log-file /opt/seafile-server/logs/seafdav.log --pid /opt/seafile-server/pids/seafdav.pid --port 8080 --host 127.0.0.1
[05/29/18 19:54:28] seafile-controller.c(88): spawned /usr/bin/python2.7, pid 8912
[05/29/18 19:54:38] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/29/18 19:54:38] seafile-controller.c(422): seafdav need restart...
[05/29/18 19:54:38] seafile-controller.c(73): spawn_process: /usr/bin/python2.7 -m wsgidav.server.run_server --log-file /opt/seafile-server/logs/seafdav.log --pid /opt/seafile-server/pids/seafdav.pid --port 8080 --host 127.0.0.1
[05/29/18 19:54:38] seafile-controller.c(88): spawned /usr/bin/python2.7, pid 8919
.
. every 10 seconds
.

and therefore seafdav (webdav) doesn’t work.
At these forum you can find some posts about these topic, but nothing solved my problem.
May be som python issue? Package was updated:

Updated     python-2.7.5-58.el7.x86_64                                  @base
    Update             2.7.5-68.el7.x86_64                                  @base

Any assistance for me?

Has SeaFile acces to the path? Seems the pid is spawning but not running.

Yes. it has and the other one are created:

ls -la /opt/seafile-server/pids/
total 8
drwxr-xr-x  2 seafile seafile  46 May 29 20:48 .
drwxr-xr-x 12 seafile seafile 224 Nov  4  2017 ..
-rw-r--r--  1 seafile seafile   5 May 29 20:48 ccnet.pid
-rw-r--r--  1 seafile seafile   5 May 29 20:48 seaf-server.pid

Seems like a recurring problem but don’t always notice:

cat /opt/seafile-server/logs/controller.log |grep exist
.
. starting from 2*/02/17 to 03/08/17
.
[03/08/17 23:11:11] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[03/08/17 23:11:21] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[03/08/17 23:11:31] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[03/08/17 23:11:41] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[03/08/17 23:11:51] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[03/08/17 23:12:01] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[03/08/17 23:12:11] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[03/08/17 23:13:20] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/12/17 21:03:47] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[07/10/17 22:34:20] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[10/29/17 21:42:23] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[10/29/17 21:43:40] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 21:56:08] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 21:56:21] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 22:03:18] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 22:12:57] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 22:19:19] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 22:23:53] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 22:31:17] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 22:48:59] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 23:07:07] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/04/17 23:13:21] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/05/17 23:27:04] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/05/17 23:35:06] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[11/05/17 23:43:54] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:56:30] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:56:40] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:56:50] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:57:00] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:57:10] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:57:20] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:57:30] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:57:40] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:57:50] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:58:00] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
[05/24/18 21:58:10] seafile-controller.c(396): pid file /opt/seafile-server/pids/seafdav.pid does not exist
.
. update running and current issue
.

Could you upgrade to 6.2.5?

Never change a “running” system… :wink:

1 Like

Youre right, but yours not running as you want. And if you never want to touch it you shouldn’t update Python. I would make a backup and upgrade. There were some others with similar issues, but I think it was on Arch.

Yes, at least one was on Arch.
Will check the update path 6.2.2 to 6.2.5 asap and be back…

OK, update solved the issue…!
Thanks to force the update :wink:

2 Likes

No problem!

But if you made one update, you could make all.
You already changed something.