Hello,
I just upgrade my SeaFile using admin web page. Since then I can’t access to my files. Client says « Internal error » and so does the web access.
Seafile is installed on /opt/yunohost/seafile and claims being working.
Thanks for your help.
Hello,
You could see the log in /opt/yunohost/seafile/logs/ to have more information about why it’s broken. The most interesting files might be “seahub.log”, “seahub.init.log”. You can also see maybe “controller.log”, “seafile.init.log” and “seafile.log”.
Thanks for your answer.
Here are the logs.
tail -n 20 /opt/yunohost/seafile/logs/seahub.init.log
LC_ALL is not set in ENV, set to C
Starting seahub at port 8000 ...
Seahub is started
Done.
Stopping seahub ...
Done.
LC_ALL is not set in ENV, set to C
Starting seahub at port 8000 ...
Seahub is started
Done.
tail -n 20 /opt/yunohost/seafile/logs/controller.log
[03/27/18 16:21:33] seafile-controller.c(73): spawn_process: ccnet-server -F /opt/yunohost/seafile/conf -c /opt/yunohost/seafile/ccnet -f /opt/yunohost/seafile/logs/ccnet.log -d -P /opt/yunohost/seafile/pids/ccnet.pid
[03/27/18 16:21:33] seafile-controller.c(88): spawned ccnet-server, pid 1680
[03/27/18 16:21:34] seafile-controller.c(555): ccnet daemon connected.
[03/27/18 16:21:34] seafile-controller.c(186): starting seaf-server ...
[03/27/18 16:21:34] seafile-controller.c(73): spawn_process: seaf-server -F /opt/yunohost/seafile/conf -c /opt/yunohost/seafile/ccnet -d /home/yunohost.app/seafile-data -l /opt/yunohost/seafile/logs/seafile.log -P /opt/yunohost/seafile/pids/seaf-server.pid
[03/27/18 16:21:34] seafile-controller.c(88): spawned seaf-server, pid 1685
[03/27/18 16:21:34] seafile-controller.c(396): pid file /opt/yunohost/seafile/pids/seafdav.pid does not exist
[03/27/18 16:21:34] seafile-controller.c(73): spawn_process: /usr/bin/python2.7 -m wsgidav.server.run_server runfcgi --log-file /opt/yunohost/seafile/logs/seafdav.log --pid /opt/yunohost/seafile/pids/seafdav.pid --port 8080 --host localhost
[03/27/18 16:21:34] seafile-controller.c(88): spawned /usr/bin/python2.7, pid 1686
[06/27/18 18:03:26] seafile-controller.c(566): shutting down ccnet-server ...
[06/27/18 18:04:06] seafile-controller.c(154): starting ccnet-server ...
[06/27/18 18:04:06] seafile-controller.c(73): spawn_process: ccnet-server -F /opt/yunohost/seafile/conf -c /opt/yunohost/seafile/ccnet -f /opt/yunohost/seafile/logs/ccnet.log -d -P /opt/yunohost/seafile/pids/ccnet.pid
[06/27/18 18:04:06] seafile-controller.c(88): spawned ccnet-server, pid 1358
[06/27/18 18:04:07] seafile-controller.c(555): ccnet daemon connected.
[06/27/18 18:04:07] seafile-controller.c(186): starting seaf-server ...
[06/27/18 18:04:07] seafile-controller.c(73): spawn_process: seaf-server -F /opt/yunohost/seafile/conf -c /opt/yunohost/seafile/ccnet -d /home/yunohost.app/seafile-data -l /opt/yunohost/seafile/logs/seafile.log -P /opt/yunohost/seafile/pids/seaf-server.pid
[06/27/18 18:04:07] seafile-controller.c(88): spawned seaf-server, pid 1363
[06/27/18 18:04:07] seafile-controller.c(396): pid file /opt/yunohost/seafile/pids/seafdav.pid does not exist
[06/27/18 18:04:07] seafile-controller.c(73): spawn_process: /usr/bin/python2.7 -m wsgidav.server.run_server runfcgi --log-file /opt/yunohost/seafile/logs/seafdav.log --pid /opt/yunohost/seafile/pids/seafdav.pid --port 8080 --host localhost
[06/27/18 18:04:07] seafile-controller.c(88): spawned /usr/bin/python2.7, pid 13
tail -n 20 /opt/yunohost/seafile/logs/seafile.init.log
Done.
Stopping seafile server ...
Done.
[03/27/18 16:21:33] ../common/session.c(132): using config file /opt/yunohost/seafile/conf/ccnet.conf
Starting seafile server, please wait ...
Seafile server started
Done.
Stopping seafile server ...
Done.
[06/27/18 18:04:06] ../common/session.c(132): using config file /opt/yunohost/seafile/conf/ccnet.conf
Starting seafile server, please wait ...
Seafile server started
Done.
tail -n 20 /opt/yunohost/seafile/logs/seafile.log
[06/27/18 21:34:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 21:39:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 21:44:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 21:49:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 21:54:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 21:59:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:04:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:09:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:14:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:19:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:24:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:29:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:34:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:39:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:44:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:49:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:54:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 22:59:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 23:04:08] size-sched.c(96): Repo size compute queue size is 0
[06/27/18 23:09:08] size-sched.c(96): Repo size compute queue size is 0Ok,
Could you try to type :
sudo systemctl restart seafile-server
and after
sudo systemctl status seafile-server and sudo journalctl --lines=20 -u seafile-server
systemctl restart seafile-server
Job for seafile-server.service failed because the control process exited with error code.
See “systemctl status seafile-server.service” and “journalctl -xe” for details.
systemctl status seafile-server
- seafile-server.service - LSB: Starts Seafile Server
Loaded: loaded (/etc/init.d/seafile-server; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-06-28 07:06:17 CEST; 26s ago
Docs: man:systemd-sysv-generator(8)
Process: 14517 ExecStart=/etc/init.d/seafile-server start (code=exited, status=1/FAILURE)
Tasks: 26 (limit: 4915)
CGroup: /system.slice/seafile-server.service
|-1359 /opt/yunohost/seafile/seafile-server-6.2.3/seafile/bin/seafile-controller -c /opt/yunohost/seafile/ccnet -d /home/yunohost.
|-1361 ccnet-server -F /opt/yunohost/seafile/conf -c /opt/yunohost/seafile/ccnet -f /opt/yunohost/seafile/logs/ccnet.log -d -P /op
|-1364 /usr/bin/python2.7 -m wsgidav.server.run_server runfcgi --log-file /opt/yunohost/seafile/logs/seafdav.log --pid /opt/yunoho
|-1365 seaf-server -F /opt/yunohost/seafile/conf -c /opt/yunohost/seafile/ccnet -d /home/yunohost.app/seafile-data -l /opt/yunohos
|-1420 python2.7 /opt/yunohost/seafile/seafile-server-6.2.3/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/yunohost/sea
|-1427 python2.7 /opt/yunohost/seafile/seafile-server-6.2.3/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/yunohost/sea
|-1428 python2.7 /opt/yunohost/seafile/seafile-server-6.2.3/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/yunohost/sea
|-1429 python2.7 /opt/yunohost/seafile/seafile-server-6.2.3/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/yunohost/sea
|-1430 python2.7 /opt/yunohost/seafile/seafile-server-6.2.3/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/yunohost/sea
`-1431 python2.7 /opt/yunohost/seafile/seafile-server-6.2.3/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/yunohost/sea
Jun 28 07:06:17 pi-et-ro.net sudo[14518]: root : TTY=unknown ; PWD=/ ; USER=seafile ; COMMAND=/opt/yunohost/seafile/seafile-server-latest/sea
Jun 28 07:06:17 pi-et-ro.net sudo[14518]: pam_unix(sudo:session): session opened for user seafile by (uid=0)
Jun 28 07:06:17 pi-et-ro.net sudo[14518]: pam_unix(sudo:session): session closed for user seafile
Jun 28 07:06:17 pi-et-ro.net sudo[14525]: root : TTY=unknown ; PWD=/ ; USER=seafile ; COMMAND=/opt/yunohost/seafile/seafile-server-latest/sea
Jun 28 07:06:17 pi-et-ro.net sudo[14525]: pam_unix(sudo:session): session opened for user seafile by (uid=0)
Jun 28 07:06:17 pi-et-ro.net sudo[14525]: pam_unix(sudo:session): session closed for user seafile
Jun 28 07:06:17 pi-et-ro.net systemd[1]: seafile-server.service: Control process exited, code=exited status=1
Jun 28 07:06:17 pi-et-ro.net systemd[1]: Failed to start LSB: Starts Seafile Server.
Jun 28 07:06:17 pi-et-ro.net systemd[1]: seafile-server.service: Unit entered failed state.
Jun 28 07:06:17 pi-et-ro.net systemd[1]: seafile-server.service: Failed with result ‘exit-code’.
journalctl --lines=20 -u seafile-server
– Logs begin at Wed 2018-06-27 18:00:37 CEST, end at Thu 2018-06-28 07:06:17 CEST. –
Jun 27 20:51:59 pi-et-ro.net systemd[1]: seafile-server.service: Unit entered failed state.
Jun 27 20:51:59 pi-et-ro.net systemd[1]: seafile-server.service: Failed with result ‘exit-code’.
Jun 28 07:01:33 pi-et-ro.net systemd[1]: Starting LSB: Starts Seafile Server…
Jun 28 07:01:33 pi-et-ro.net seafile-server[14426]: sudo: /opt/yunohost/seafile/seafile-server-latest/seafile.sh: command not found
Jun 28 07:01:33 pi-et-ro.net seafile-server[14426]: sudo: /opt/yunohost/seafile/seafile-server-latest/seahub.sh: command not found
Jun 28 07:01:33 pi-et-ro.net systemd[1]: seafile-server.service: Control process exited, code=exited status=1
Jun 28 07:01:33 pi-et-ro.net systemd[1]: Failed to start LSB: Starts Seafile Server.
Jun 28 07:01:33 pi-et-ro.net systemd[1]: seafile-server.service: Unit entered failed state.
Jun 28 07:01:33 pi-et-ro.net systemd[1]: seafile-server.service: Failed with result ‘exit-code’.
Jun 28 07:06:17 pi-et-ro.net systemd[1]: Starting LSB: Starts Seafile Server…
Jun 28 07:06:17 pi-et-ro.net sudo[14518]: root : TTY=unknown ; PWD=/ ; USER=seafile ; COMMAND=/opt/yunohost/seafile/seafile-server-latest/sea
Jun 28 07:06:17 pi-et-ro.net sudo[14518]: pam_unix(sudo:session): session opened for user seafile by (uid=0)
Jun 28 07:06:17 pi-et-ro.net sudo[14518]: pam_unix(sudo:session): session closed for user seafile
Jun 28 07:06:17 pi-et-ro.net sudo[14525]: root : TTY=unknown ; PWD=/ ; USER=seafile ; COMMAND=/opt/yunohost/seafile/seafile-server-latest/sea
Jun 28 07:06:17 pi-et-ro.net sudo[14525]: pam_unix(sudo:session): session opened for user seafile by (uid=0)
Jun 28 07:06:17 pi-et-ro.net sudo[14525]: pam_unix(sudo:session): session closed for user seafile
Jun 28 07:06:17 pi-et-ro.net systemd[1]: seafile-server.service: Control process exited, code=exited status=1
Jun 28 07:06:17 pi-et-ro.net systemd[1]: Failed to start LSB: Starts Seafile Server.
Jun 28 07:06:17 pi-et-ro.net systemd[1]: seafile-server.service: Unit entered failed state.
Jun 28 07:06:17 pi-et-ro.net systemd[1]: seafile-server.service: Failed with result ‘exit-code’.
I noticed /opt/yunohost/seafile/seafile-server-latest was pointing to /opt/yunohost/seafile/seafile-server-6.2.3 so recreated the symlink to point to /opt/yunohost/seafile/seafile-server-6.2.5. But I still have the same errors.
ls /opt/yunohost/seafile/seafile-server-latest
check_init_admin.py runtime seaf-fuse.sh seafile seahub setup-seafile-mysql.py setup-seafile.sh
reset-admin.sh seaf-fsck.sh seaf-gc.sh seafile.sh seahub.sh setup-seafile-mysql.sh upgrade
I don’t really know why but it look like that some file are not found when I see that :
sudo: /opt/yunohost/seafile/seafile-server-latest/seahub.sh: command not found
I purpose to try to do a upgrade of the apps and mybe after it should be ok.
So you could do this (don’t enable the restore if the upgrade fail because it could be worse than to keep the actuall install). So
Do eventually a manual backup :
yunohost backup create --apps seafile --verbose
And after do an upgrade
NO_BACKUP_UPGRADE=1 sudo yunohost app upgrade -u https://github.com/YunoHost-Apps/seafile_ynh --verbose seafile
First it was empty because seafile-server-latest was pointing to seafile-server-6.2.3.
I created again the symlink, and as you can see, it is not empty now.
I noticed to strange errors.
CGroup: /system.slice/seafile-server.service
|-1359 /opt/yunohost/seafile/seafile-server-6.2.3/seafile/bin/seafile-controller -c /opt/yunohost/seafile/ccnet -d /home/yunohost.
Why there is still a reference to seafile-server-6.2.3 directory ?
Why is it pointing to /home/yunohost ? Seafile data is in /home/yunohost.apps/
I can not acces my server for the moment. So I’ll try what you say later.
First it was empty because seafile-server-latest was pointing to seafile-server-6.2.3.
I created again the symlink, and as you can see, it is not empty now.
Yes I understand.
Why there is still a reference to seafile-server-6.2.3 directory ?
I don’t really know. Mybe it’s an old log while your link pointed to the 6.2.3 version.
Why is it pointing to /home/yunohost ? Seafile data is in /home/yunohost.apps/
It’s because your seafile data are stored in /home/yunohost.
Why there is still a reference to seafile-server-6.2.3 directory ?I don’t really know. Mybe it’s an old log while your link pointed to the 6.2.3 version.
It was not an old log. It’s the log after systemctl status seafile-server and after I created the good symlink
Why is it pointing to /home/yunohost ? Seafile data is in /home/yunohost.apps/It’s because your seafile data are stored in /home/yunohost.
I have no /home/yunohost directory.
seafile data is in /home/yunohost.app/seafile-data/
Ok.
So I just rebooted the server and everything works fine. 
The problem was directory seafile-server-latest not properly linked.
Thanks for your help.