Seafile Boot Script Failed

Seafile Server
1

systemctl on debian 10 fails when i try to run the script from the tutorial page. The server runs great, it even takes the seafile.server scipt I made, however, beyond loading it, it fails.

● seafile.service loaded failed failed Seafile
● seahub.service loaded failed failed Seafile hub

Seafile.service

[Unit]
Description=Seafile
After=network.target mysql.service

[Service]
Type=forking
ExecStart=/opt/seafile/seafile-server-8.0.8/seafile.sh start
ExecStop=/opt/seafile/seafile-server-8.0.8/seafile.sh stop
LimitNOFILE=infinity
User=seafile
Group=seafile

[Install]
WantedBy=multi-user.target

Seahub.service

[Unit]
Description=Seafile hub
After=network.target seafile.service

[Service]
Type=forking
# change start to start-fastcgi if you want to run fastcgi
ExecStart=/opt/seafile/seafile-server-8.0.8/seahub.sh start
ExecStop=/opt/seafile/seafile-server-8.0.8/seahub.sh stop
User=seafile
Group=seafile

[Install]
WantedBy=multi-user.target
2

If you do not see any telling messages in the logs below /opt/seafile/logs then edit conf/gunicorn.conf.py to read “daemon = False” and run the seafile-server-latest/seahub.sh start from a terminal. You should see what is going wrong in the output there. Fix that and change daemon mode to True again.

3 
LC_ALL is not set in ENV, set to en_US.UTF-8
Starting seahub at port 8000 ...
[2023-06-25 11:41:21 +0000] [2213] [INFO] Starting gunicorn 20.1.0
[2023-06-25 11:41:21 +0000] [2213] [INFO] Listening at: http://0.0.0.0:8000 (2213)
[2023-06-25 11:41:21 +0000] [2213] [INFO] Using worker: sync
[2023-06-25 11:41:21 +0000] [2216] [INFO] Booting worker with pid: 2216
[2023-06-25 11:41:21 +0000] [2217] [INFO] Booting worker with pid: 2217
[2023-06-25 11:41:21 +0000] [2218] [INFO] Booting worker with pid: 2218
[2023-06-25 11:41:21 +0000] [2219] [INFO] Booting worker with pid: 2219
[2023-06-25 11:41:21 +0000] [2220] [INFO] Booting worker with pid: 2220
^C[2023-06-25 11:44:12 +0000] [2213] [INFO] Handling signal: int
[2023-06-25 11:44:12 +0000] [2218] [INFO] Worker exiting (pid: 2218)
[2023-06-25 11:44:12 +0000] [2217] [INFO] Worker exiting (pid: 2217)
[2023-06-25 11:44:12 +0000] [2219] [INFO] Worker exiting (pid: 2219)
[2023-06-25 11:44:12 +0000] [2220] [INFO] Worker exiting (pid: 2220)
[2023-06-25 11:44:12 +0000] [2216] [INFO] Worker exiting (pid: 2216)
[2023-06-25 11:44:12 +0000] [2213] [INFO] Shutting down: Master
Error:Seahub failed to start.

I gave that a shot… i waited a good few minutes before forcing it to stop. Not sure what booting worker means, google doesn’t help much either. Changing the log back to true. I’m about to accept the fact that a sticky note writen on the side of the server that says:

**IF POWER GOES OUT**

cd /opt/seafile/seafile-server-8.0.8
sudo ./seafile.sh start
sudo ./seahub.sh start
4

These are exactly the same console messages that I see, where seahub works just fine.

When starting from systemd, /var/log/syslog reads:

… systemd[1]: Starting seahub.service - Seafile Hub...
… seahub.sh[145961]: LC_ALL is not set in ENV, set to en_US.UTF-8
… seahub.sh[145961]: Starting seahub at port 8000 ...
… seahub.sh[145961]: Seahub is started
… seahub.sh[145961]: Done.
… systemd[1]: Started seahub.service - Seafile Hub.

Your unit files are looking fine. Does journalctl -xeu seahub.service show all green?