Seahub just stopped working, with no logs or any meaningful errors

Seafile Server
1

Hi, so the title self-explains it. The docker tried starting seahub but it got this:

seafile  | Error:Seahub failed to start.
seafile  | Please try to run “./seahub.sh start” again
seafile  | Traceback (most recent call last):
seafile  |   File “/scripts/start.py”, line 94, in 
seafile  |     main()
seafile  |   File “/scripts/start.py”, line 80, in main
seafile  |     call(‘{} start’.format(get_script(‘seahub.sh’)))
seafile  |   File “/scripts/utils.py”, line 71, in call
seafile  |     return subprocess.check_call(*a, **kw)
seafile  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
seafile  |   File “/usr/lib/python3.12/subprocess.py”, line 413, in check_call
seafile  |     raise CalledProcessError(retcode, cmd)
seafile  | subprocess.CalledProcessError: Command ‘/opt/seafile/seafile-pro-server-13.0.7/seahub.sh start’ returned non-zero exit status 1.

When I bash-ed into the docker and tried running it normally, I got

Starting seahub at port 8000 …
Error:Seahub failed to start.
Please try to run “./seahub.sh start” again

The strange part is that I don’t get any logs in the seahub.log file

Thanks in advance.

2

You can also modify conf/gunicorn.conf , change daemon = True to daemon = False , then run ./seahub.sh again.

If there are missing Python dependencies, the error will be reported in the terminal.

If you have an syntax error in seahub_settings.py, it will also print the error.

3

Thanks for your answer! The problem with my setup is that both elasticsearch and seasearch are running together; therefore, Seahub failed to start.

By the way, I suggest adding a prompt, if the user failed to start seahub normally, then it will prompt the user to change the daemon to False for more information.

Thanks!