Seafile 9.0.10 Seafdav will not start

I've installed Seafile 9.0.10 in Jail and enabled Seafdav. It's generating errors every 10 second in controller.log:
Code:
2023-06-02 00:32:53 seafile-controller.c(475): pid file /usr/local/www/haiwen/pids/seafdav.pid does not exist
2023-06-02 00:32:53 seafile-controller.c(583): seafdav need restart...
2023-06-02 00:32:53 seafile-controller.c(95): spawn_process: /usr/local/bin/python3.9 -m wsgidav.server.server_cli --server gunicorn --root / --log-file /usr/local/www/haiwen/logs/seafdav.log --pid /usr/local/www/haiwen/pids/seafdav.pid --port 8080 --host 192.168.1.105
2023-06-02 00:32:53 seafile-controller.c(129): spawned /usr/local/bin/python3.9, pid 47949
2023-06-02 00:32:54 seafile-controller.c(137): usage: wsgidav [-h] [-p PORT] [-H HOST] [-r ROOT_PATH]
               [--auth {anonymous,nt,pam-login}]
               [--server {paste,gevent,cheroot,cherrypy,ext-wsgiutils,flup-fcgi,flup-fcgi_fork,wsgiref,gunicorn}]
               [--ssl-adapter {builtin,pyopenssl}] [-v | -q]
               [-c CONFIG_FILE | --no-config] [-V]
wsgidav: error: unrecognized arguments: --log-file /usr/local/www/haiwen/logs/seafdav.log --pid /usr/local/www/haiwen/pids/seafdav.pid
This worked very well with Debian as I have migrated seafile-data and mysql database over to Seafile on FreeBSD 13.2. I'm not sure why it's generating this error.
 
Last edited by a moderator:
Finally I solved the problem. It seems that seafobj and wsgidav folders are missing in seafile-sever/seahub/thirdpart folder. I installed, deleted the package and then re-installed the package. Somehow the re-installation omitted seafobj and wsgidav folders so that's why controller.log was getting errors every 10 seconds.

I did a clean install and those two folders did appear in thirdpart folder and seafdav worked very well. I'm going to report this bug to net-mgmt/seafile-server maintainer on Bugzilla.
 
Back
Top