Seahub wont start and it not gives any useful input about why

[seafile@calvatia seafile-server-latest]$ ./ start

Starting seahub at port 8000 …
Error:Seahub failed to start.
Please try to run “./ start” again
[seafile@calvatia seafile-server-latest]$ ./ start-fastcgi

Usage: { start | stop | restart }

is optional, and defaults to 8000

I have also tried to upgrade it, ran the upgrade script successfuly but no dice. Seahub really could use some debug options or verbose startup option.

I have ran out of ideas. System is Fedora Server. It has Python 3.11 currently, and I see that in in e.g gunicorn it is set for python3.8. I created a symlink but it didn’t work either.

In act of desperation I started browsing through file tree looking for something unusual. I removed from pids and it started.

I am perplexed.

Thanks for posting this solution. When I read your post I had a feeling that I saw this issue before - many years ago. Can I ask what version of Seafile server you are running?

In any case, a similar post dated November 2021 can be found HERE:

hi there!

today i had some serious issues to start seahub.

worst of all there was literally no hint in error message, only

Error:Seahub failed to start.
Please try to run “./ start” again

Nothing in my *.logs, systemd/journal or anything else i could think of. Maybe i missed something …
BUT after 1,5h and almost losing my mind i just stumble upon some PID files. was still there, and of course after removing everything was fine again.

PLS can seafile team implement some check to delete remaining PID files? (prbl happend after sys crash)
or at least a message that there are remaining pid files.

I agree, that errors upon starting of seahub can be hard to track. One thing we did recently was setting logging from gunicorn (in shell-script) to ‘debug’ and specify a logfile destination. This way we found the error was usally caused by wrong versions of (or missing) python-packages.