Debuging options seahub

Hi

After an upgrade of a seafile server 5.1.4 to 6.0.8 seahub was not starting anymore. I tried to
find out way with no success.

I tried with debug and log file options but there was no hint pointing me to where the
problem is.

any hints ?

thanks Manuel

If you start seahub via ‘seahub.sh start-fastcgi’, the error will be printed.

I quite often have the same problem - seahub not starting anymore after an upgrade / restart (in a docker container) - i really think that always having the exact error printed and explaining why the process is not starting would be really nice (and is really needed) (that means, to have this behavior by default without the need to change anything in configuration or startup scripts).

Did you tried docker logs -f seafile ?

Hey !
Yes i did, sadly i just have logs like :

2017-11-21 11:56:57,367 INFO success: seahub entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-11-21 11:57:01,007 INFO exited: seahub (exit status 1; not expected) 2017-11-21 11:57:02,010 INFO spawned: 'seahub' with pid 566 2017-11-21 11:57:02,318 CRIT reaped unknown pid 580) 2017-11-21 11:57:02,659 CRIT reaped unknown pid 581) 2017-11-21 11:57:03,660 INFO success: seahub entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-11-21 11:57:07,322 INFO exited: seahub (exit status 1; not expected) 2017-11-21 11:57:08,325 INFO spawned: 'seahub' with pid 590 2017-11-21 11:57:08,621 CRIT reaped unknown pid 604) 2017-11-21 11:57:08,971 CRIT reaped unknown pid 605) 2017-11-21 11:57:09,972 INFO success: seahub entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-11-21 11:57:13,625 INFO exited: seahub (exit status 1; not expected)

I would just be able to easily read (by default) somewhere why the process is crashing over and over.