Greetings Seafolks,
I have been using seafile for couple of years, so far without issues. My setup uses WebDAV behind nginx with https. After upgrade to Ubuntu 18.04, it seems that seafdav is no longer started, I am unable to figure out why. I would be glad for any hints, where to enable debug messages, more logging etc.
seafdav.conf reads.
[WEBDAV]
enabled = true
port = 8080
fastcgi = false
share_name = /seafdav
Nginx config is
location /seafdav {
proxy_pass http://127.0.0.1:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Forwarded-Proto https;
proxy_http_version 1.1;
proxy_connect_timeout 36000s;
proxy_read_timeout 36000s;
proxy_send_timeout 36000s;
send_timeout 36000s;
# This option is only available for Nginx >= 1.8.0.
client_max_body_size 0;
proxy_request_buffering off;
access_log /var/log/nginx/seafdav.access.log;
error_log /var/log/nginx/seafdav.error.log;
}
controller.log does not mention that it would start webdav
[05/14/19 09:01:01] seafile-controller.c(169): starting ccnet-server ...
[05/14/19 09:01:01] seafile-controller.c(73): spawn_process: ccnet-server -F /usr/local/seafile/conf -c /usr/local/seafile/ccnet -f /usr/local/seafile/logs/ccnet.log -d -P /usr/local/seafile/pids/ccnet.pid
[05/14/19 09:01:01] seafile-controller.c(88): spawned ccnet-server, pid 22638
[05/14/19 09:01:02] seafile-controller.c(571): ccnet daemon connected.
[05/14/19 09:01:02] seafile-controller.c(201): starting seaf-server ...
[05/14/19 09:01:02] seafile-controller.c(73): spawn_process: seaf-server -F /usr/local/seafile/conf -c /usr/local/seafile/ccnet -d /usr/local/seafile/seafile-data -l /usr/local/seafile/logs/seafile.log -P /usr/local/seafile/pids/seaf-server.pid
[05/14/19 09:01:02] seafile-controller.c(88): spawned seaf-server, pid 22643
However it would have these log lines in the past
[03/12/19 08:13:00] seafile-controller.c(73): spawn_process: /usr/bin/python2.7 -m wsgidav.server.run_server --log-file /usr/local/seafile/logs/seafdav.log --pid /usr/local/seafile/pids/seafdav.pid --port 8080 --host 0.0.0.0
To verify the config file is at least read, I set “enabled = bla” in seafdav.conf. This makes line appear in controller.log
[05/14/19 09:26:58] seafile-controller.c(544): seafdav not enabled.
I also had a look at previous topic related to wsgidav.server.run_server, but they seem to be on wrong track and evolve around system-wide / pip installed wsgidav module vs the vendored version in thirdpart/ folder.
Sorry for this lengthy post. To summarize: what next steps can I do to debug this issue? Where to enable debug-logs? How to start seafdav from the commandline, so I could get some kind of backtrace, etc?
Thanks a lot,
Jens