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.
I’m getting the same error after switching from CE to Professional docker image.
Starting seafile server, please wait ...
Failed to start seafile server
Traceback (most recent call last):
File "/scripts/start.py", line 91, in <module>
main()
File "/scripts/start.py", line 76, in main
call('{} start'.format(get_script('seafile.sh')))
File "/scripts/utils.py", line 71, in call
return subprocess.check_call(*a, **kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/seafile/seafile-pro-server-13.0.12/seafile.sh start' returned non-zero exit status 1.
both elasticsearch and seasearch are running together; therefore, Seahub failed to start.