Seahub failed to start after upgrading from 6.2.5 to 6.3.4


#1

Hello together,

I upgraded my Seafile server from verison 6.2.5 to 6.3.4 and now seahub is not starting :confused:. I’m runnig debian 9 and I had enjoyed it, but now it’s not working. This is error message when i try to start seahub:

● seahub.service - Seafile hub
Loaded: loaded (/etc/systemd/system/seahub.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-01-31 15:14:10 EET; 7min ago
Process: 12090 ExecStart=/usr/share/seafile/seafile-server-latest/seahub.sh start-fastcgi (code=exited, status=1/FAILURE)
Main PID: 12090 (code=exited, status=1/FAILURE)

Jan 31 15:13:58 server seahub.sh[12090]: Starting seahub (fastcgi) at 127.0.0.1:8000 …
Jan 31 15:14:05 server seahub.sh[12090]: Unknown command: ‘runfcgi’
Jan 31 15:14:05 server seahub.sh[12090]: Type ‘manage.py help’ for usage.
Jan 31 15:14:05 server seahub.sh[12090]: Warning: File comment has changed since version 6.3, while table base_filecomment is not migrated yet, please consid
Jan 31 15:14:05 server seahub.sh[12090]:
Jan 31 15:14:10 server seahub.sh[12090]: Error:Seahub failed to start.
Jan 31 15:14:10 server systemd[1]: seahub.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 15:14:10 server systemd[1]: Failed to start Seafile hub.
Jan 31 15:14:10 server systemd[1]: seahub.service: Unit entered failed state.
Jan 31 15:14:10 server systemd[1]: seahub.service: Failed with result ‘exit-code’.

This is message when I type “journalctl -xe”.

– Unit seahub.service has begun starting up.
Jan 31 15:13:58 server seahub.sh[12090]: LC_ALL is not set in ENV, set to en_US.UTF-8
Jan 31 15:13:58 server seahub.sh[12090]: Starting seahub (fastcgi) at 127.0.0.1:8000 …
Jan 31 15:14:05 server seahub.sh[12090]: Unknown command: ‘runfcgi’
Jan 31 15:14:05 server seahub.sh[12090]: Type ‘manage.py help’ for usage.
Jan 31 15:14:05 server seahub.sh[12090]: Warning: File comment has changed since version 6.3, while table base_filecomment is not migrated yet, please consid
Jan 31 15:14:05 server seahub.sh[12090]:
Jan 31 15:14:10 server seahub.sh[12090]: Error:Seahub failed to start.
Jan 31 15:14:10 server systemd[1]: seahub.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 15:14:10 server systemd[1]: Failed to start Seafile hub.
– Subject: Unit seahub.service has failed
– Defined-By: systemd
– Support: *link for debian support*

– Unit seahub.service has failed.

– The result is failed.
Jan 31 15:14:10 server systemd[1]: seahub.service: Unit entered failed state.
Jan 31 15:14:10 server systemd[1]: seahub.service: Failed with result ‘exit-code’.
Jan 31 15:14:20 server sshd[12261]: Did not receive identification string from ::1 port 34054

Any idea what I can do?

Greetings,
Petar


#2

FAST-CGI is no longer supported on Seafile 6.3. You should use WSGI mode instead.

https://manual.seafile.com/changelog/server-changelog.html


#3

It doesn’t look like you ran the database upgrade script.