[SOLVED] Service seahub is failed :(

Hardware: VPS bought online ( Contabo )
YunoHost version: 11.1.6 (stable)
I have access to my server : Through SSH and browser
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

just started getting the message in the subject every time i run a diagnosis.

if i navigate to my seafile domain, im presented with a blank page with this message:

502 Bad Gateway

If you see this page, your connection with the server is working but the internal service providing this path is not responding.

Administrator, make sure that the service is running, and check its logs if it is not. The Services page is in your webadmin, under `Tools > Services`.

*Thank you for using YunoHost.*

and if i do follow the diagnosis instructions and run the suggested command in ssh i get:

~$ sudo yunohost service restart seahub
Job for seahub.service failed because the control process exited with error code.
See "systemctl status seahub.service" and "journalctl -xe" for details.
Warning: Could not execute the command 'systemctl restart seahub'
Error: Could not restart the service 'seahub'

Recent service logs:-- Journal begins at Fri 2023-01-27 18:18:01 CET, ends at Thu 2023-02-09 22:20:56 CET. --
Jan 28 00:26:08 systemd[1]: Starting Seafile hub...
Jan 28 00:26:08 seahub.sh[30636]: LC_ALL is not set in ENV, set to en_US.UTF-8
Jan 28 00:26:08 seahub.sh[30636]: Starting seahub at port 8000 ...
Jan 28 00:26:09 seahub.sh[30645]: ----------------------------------------
Jan 28 00:26:09 seahub.sh[30645]: Successfully created seafile admin
Jan 28 00:26:09 seahub.sh[30645]: ----------------------------------------
Jan 28 00:26:14 seahub.sh[30636]: Seahub is started
Jan 28 00:26:14 seahub.sh[30636]: Done.
Jan 28 00:26:14 systemd[1]: Started Seafile hub.
Jan 28 00:27:29 python3[30656]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory
Jan 28 00:27:35 python3[30654]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory
Jan 28 01:05:53 python3[30652]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory
Jan 28 02:36:39 python3[30653]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory
Jan 28 02:37:18 python3[30651]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory
-- Boot 641f49fd63fc4fe39ed1aecbad18f757 --
Feb 05 12:04:21 systemd[1]: Starting Seafile hub...
Feb 05 12:04:22 seahub.sh[1788]: LC_ALL is not set in ENV, set to en_US.UTF-8
Feb 05 12:04:22 seahub.sh[1788]: Starting seahub at port 8000 ...
Feb 05 12:04:30 seahub.sh[1788]: Seahub is started
Feb 05 12:04:30 seahub.sh[1788]: Done.
Feb 05 12:04:30 systemd[1]: Started Seafile hub.
Feb 06 21:06:39 python3[1944]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory
Feb 07 14:25:42 python3[1947]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory
-- Boot d0ab8babc7f94afaa7ab1e7a693a87b3 --
Feb 08 02:02:38 systemd[1]: Starting Seafile hub...
Feb 08 02:02:38 seahub.sh[1798]: LC_ALL is not set in ENV, set to en_US.UTF-8
Feb 08 02:02:38 seahub.sh[1798]: Starting seahub at port 8000 ...
Feb 08 02:02:46 seahub.sh[1798]: Error:Seahub failed to start.
Feb 08 02:02:46 seahub.sh[1798]: Please try to run "./seahub.sh start" again
Feb 08 02:02:46 systemd[1]: seahub.service: Control process exited, code=exited, status=1/FAILURE
Feb 08 02:02:46 systemd[1]: seahub.service: Failed with result 'exit-code'.
Feb 08 02:02:46 systemd[1]: Failed to start Seafile hub.
Feb 08 02:02:46 systemd[1]: seahub.service: Consumed 1.922s CPU time.
Feb 09 00:08:50 systemd[1]: Starting Seafile hub...
Feb 09 00:08:51 seahub.sh[42776]: LC_ALL is not set in ENV, set to en_US.UTF-8
Feb 09 00:08:51 seahub.sh[42776]: Starting seahub at port 8000 ...
Feb 09 00:09:01 seahub.sh[42776]: Seahub is started
Feb 09 00:09:01 seahub.sh[42776]: Done.
Feb 09 00:09:01 systemd[1]: Started Seafile hub.
Feb 09 00:09:13 systemd[1]: seahub.service: Main process exited, code=exited, status=1/FAILURE
Feb 09 00:09:13 systemd[1]: seahub.service: Failed with result 'exit-code'.
Feb 09 00:09:13 systemd[1]: seahub.service: Consumed 4.771s CPU time.
Feb 09 22:18:55 systemd[1]: Starting Seafile hub...
Feb 09 22:18:55 seahub.sh[88041]: LC_ALL is not set in ENV, set to en_US.UTF-8
Feb 09 22:18:57 seahub.sh[88041]: Starting seahub at port 8000 ...
Feb 09 22:19:07 seahub.sh[88041]: Seahub is started
Feb 09 22:19:07 seahub.sh[88041]: Done.
Feb 09 22:19:07 systemd[1]: Started Seafile hub.
Feb 09 22:19:14 systemd[1]: seahub.service: Main process exited, code=exited, status=1/FAILURE
Feb 09 22:19:14 systemd[1]: seahub.service: Failed with result 'exit-code'.
Feb 09 22:19:14 systemd[1]: seahub.service: Consumed 13.677s CPU time.
Feb 09 22:20:50 systemd[1]: Starting Seafile hub...
Feb 09 22:20:50 seahub.sh[88377]: LC_ALL is not set in ENV, set to en_US.UTF-8
Feb 09 22:20:50 seahub.sh[88377]: Starting seahub at port 8000 ...
Feb 09 22:20:56 seahub.sh[88377]: Error:Seahub failed to start.
Feb 09 22:20:56 seahub.sh[88377]: Please try to run "./seahub.sh start" again
Feb 09 22:20:56 systemd[1]: seahub.service: Control process exited, code=exited, status=1/FAILURE
Feb 09 22:20:56 systemd[1]: seahub.service: Failed with result 'exit-code'.
Feb 09 22:20:56 systemd[1]: Failed to start Seafile hub.
Feb 09 22:20:56 systemd[1]: seahub.service: Consumed 5.672s CPU time.

~$ sudo systemctl status seahub.service
● seahub.service - Seafile hub
     Loaded: loaded (/etc/systemd/system/seahub.service; enabled; vendor preset>
     Active: failed (Result: exit-code) since Thu 2023-02-09 22:20:56 CET; 52s >
    Process: 88377 ExecStart=/opt/yunohost/seafile/seafile-server-latest/seahub>
        CPU: 5.672s

Feb 09 22:20:50 charming.monster systemd[1]: Starting Seafile hub...
Feb 09 22:20:50 charming.monster seahub.sh[88377]: LC_ALL is not set in ENV, se>
Feb 09 22:20:50 charming.monster seahub.sh[88377]: Starting seahub at port 8000>
Feb 09 22:20:56 charming.monster seahub.sh[88377]: Error:Seahub failed to start.
Feb 09 22:20:56 charming.monster seahub.sh[88377]: Please try to run "./seahub.>
Feb 09 22:20:56 charming.monster systemd[1]: seahub.service: Control process ex>
Feb 09 22:20:56 charming.monster systemd[1]: seahub.service: Failed with result>
Feb 09 22:20:56 charming.monster systemd[1]: Failed to start Seafile hub.
Feb 09 22:20:56 charming.monster systemd[1]: seahub.service: Consumed 5.672s CP>

anyone able to help?

i really want to use this app instead of nextcloud so i hope it’s a solvable issue. :frowning_face:

What happens if you try to restart i manually from “services”?

Do you have test to run this command ?

if you mean this:

~$ sudo systemctl restart seahub.service
Job for seahub.service failed because the control process exited with error code.
See "systemctl status seahub.service" and "journalctl -xe" for details.

it fails as well.

the full line says:

Please try to run "./seahub.sh start" again

but when i try:

~$ ./seahub.sh start
-bash: ./seahub.sh: No such file or directory

it also doesn’t work. :frowning_face:

solved issue by installing and reinstalling seafile as other people seemed to have done even though it seems like an odd issue.

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.