• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue seafile error

piticu iulian

piticu iulian

Basic Pleskian
Server operating system version
centos7
Plesk version and microupdate number
18.0.51 Update #1
i have installed seafiles but i het this error when i try to install on client domain
Seafile installation failed. Please examine the logs for details.
  • error
 
That is not possible, because something is always logged when trying to install an extension. Maybe it was the wrong log. Do you see anything in /var/log/plesk/panel.log, e.g.
grep "extension/seafile" /var/log/plesk/panel.log
?
 
[2023-04-18 10:55:56.754] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14cc0303e] Finished in 0.74166s, Error code: 0, stdout: /files/var/www/vhosts/1uk.host/seafile/conf/ccnet.conf
[2023-04-18 10:55:56.795] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14ccc21ce] Starting: '/usr/local/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' ''\''chown'\'' '\''-Rv'\'' '\''sysuser_9:psaserv'\'' '\''/var/www/vhosts/1uk.host/seafile'\''' '--allow-root', stdin:
[2023-04-18 10:55:57.753] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14ccc21ce] Finished in 0.94497s, Error code: 0, stdout: changed ownership of ‘/var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/setup-seafile.sh’ from root:root to sysuser_9:psaserv
[2023-04-18 10:55:58.035] 20630:643e14cdd8dbb DEBUG [extension/seafile] Found an existing install task with status'running'
[2023-04-18 10:55:58.036] 20630:643e14cdd8dbb INFO [extension/seafile] Found an existing running task
[2023-04-18 10:55:58.194] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14ce2f67a] Starting: '/usr/local/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' ''\''systemctl'\'' '\''daemon-reload'\''' '--allow-root', stdin:
[2023-04-18 10:55:58.980] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14ce2f67a] Finished in 0.78566s, Error code: 0, stdout: , stderr:
[2023-04-18 10:55:58.981] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14ceef89e] Starting: '/usr/local/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' ''\''chown'\'' '\''-Rv'\'' '\''sysuser_9:psaserv'\'' '\''/var/www/vhosts/1uk.host/seafile'\''' '--allow-root', stdin:
[2023-04-18 10:56:00.151] 20637:643e14cff2eb1 DEBUG [extension/seafile] Found an existing install task with status'running'
[2023-04-18 10:56:00.152] 20637:643e14cff2eb1 INFO [extension/seafile] Found an existing running task
[2023-04-18 10:56:00.389] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14ceef89e] Finished in 1.39434s, Error code: 0, stdout: ownership of ‘/var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/setup-seafile.sh’ retained as sysuser_9:psaserv
[2023-04-18 10:56:00.567] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14d08a6b4] Starting: '/usr/local/psa/admin/bin/modules/seafile/generate-password' , stdin:
[2023-04-18 10:56:00.600] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14d08a6b4] Finished in 0.03245s, Error code: 0, stdout: a5oqq2o7rv2k1y8pk8z2y8odv, stderr:
[2023-04-18 10:56:00.659] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14d0a0e0a] Starting: '/usr/local/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' ''\''systemctl'\'' '\''enable'\'' '\''seafile@8235'\''' '--allow-root', stdin:
[2023-04-18 10:56:00.903] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14d0a0e0a] Finished in 0.24339s, Error code: 0, stdout: , stderr: Created symlink from /etc/systemd/system/multi-user.target.wants/[email protected] to /etc/systemd/system/[email protected].
[2023-04-18 10:56:00.903] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14d0dca23] Starting: '/usr/local/psa/admin/bin/filemng' 'root' 'exec' '/' 'bash' '-c' ''\''systemctl'\'' '\''start'\'' '\''seafile@8235'\''' '--allow-root', stdin:
[2023-04-18 10:56:01.114] 20692:643e14bc6b44a DEBUG [extension/seafile] [643e14d0dca23] Finished in 0.21051s, Error code: 1, stdout: , stderr: Job for [email protected] failed because the control process exited with error code. See "systemctl status [email protected]" and "journalctl -xe" for details.
[2023-04-18 10:56:01.115] 20692:643e14bc6b44a ERR [extension/seafile] Error executing: ;'systemctl' 'start' 'seafile@8235''
[2023-04-18 10:56:01.115] 20692:643e14bc6b44a ERR [extension/seafile] stderr: Job for [email protected] failed because the control process exited with error code. See "systemctl status [email protected]" and "journalctl -xe" for details.
[2023-04-18 10:56:01.115] 20692:643e14bc6b44a ERR [extension/seafile] Failed to start the service
[2023-04-18 10:56:01.115] 20692:643e14bc6b44a ERR [extension/seafile] Service initialisation failed1uk.host
[2023-04-18 10:56:02.146] 20635:643e14d1f25b4 DEBUG [extension/seafile] Found an existing install task with status'running'
[2023-04-18 10:56:02.146] 20635:643e14d1f25b4 INFO [extension/seafile] Found an existing running task
[2023-04-18 10:56:04.158] 20584:643e14d404764 DEBUG [extension/seafile] Found an existing install task with status'error'
 
We'll need to find out why the service does not start. My current guess is that there is an unfinished, hanging installation and it is being attempted to do another installation which fails, because the first one did not complete. I am pretty sure that some important information is missing from the initial description of the issue, e.g. that there must have been something preceding the "error" situation. Could you please give this a thought? Is this the first domain where you try to use it? Or are there other domains on the server where it already works?

Also, please try to run
Code: 
# systemctl status [email protected]
# journalctl -xe
and
Code: 
# grep seafile /var/log/messages
to try to collect more details on what the situation is.

I'd also try to see if "seafile" shows up in the process list, e.g.
Code: 
# ps aux | grep seafile
and try to see what it is currently doing using strace.
 
Apr 17 13:56:46 mail systemd: Unit [email protected] entered failed state.
Apr 17 13:56:46 mail systemd: [email protected] failed.
Apr 17 14:11:32 mail seafile.sh: Stopping seafile server ...
Apr 17 14:11:32 mail seafile.sh: seafile server not running yet
Apr 17 14:11:32 mail seafile.sh: Done.
Apr 17 14:11:32 mail seafile.sh: Done.
Apr 17 14:20:57 mail systemd: Started Plesk task: ext-seafile-domain_install (task=682 process=682 trace=29318:643cf358f2563).
Apr 17 14:21:16 mail seafile.sh: Starting seafile server, please wait ...
Apr 17 14:21:16 mail journal: seafile-controller.c(536): No seafevents.
Apr 17 14:21:19 mail seafile.sh: Seafile server started
Apr 17 14:21:19 mail seafile.sh: Done.
Apr 17 14:21:20 mail seahub.sh: Successfully created seafile admin
Apr 17 14:29:15 mail systemd: Started Plesk task: ext-seafile-domain_install (task=684 process=684 trace=30975:643cf54b5ceb0).
Apr 17 14:29:15 mail systemd: Started Plesk task: ext-seafile-domain_install_monitor (task=683 process=683 trace=30975:643cf54b5ceb0).
Apr 17 14:29:35 mail seafile.sh: Seafile controller is already running, pid 29531
Apr 17 14:29:35 mail systemd: [email protected]: control process exited, code=exited status=1
Apr 17 14:29:35 mail systemd: Unit [email protected] entered failed state.
Apr 17 14:29:35 mail systemd: [email protected] failed.
Apr 17 14:33:04 mail systemd: Started Plesk task: ext-seafile-domain_install (task=686 process=686 trace=31891:643cf6306170b).
Apr 17 14:33:04 mail systemd: Started Plesk task: ext-seafile-domain_install_monitor (task=685 process=685 trace=31891:643cf6306170b).
Apr 17 14:33:24 mail seafile.sh: Seafile controller is already running, pid 29531
Apr 17 14:33:24 mail systemd: [email protected]: control process exited, code=exited status=1
Apr 17 14:33:24 mail systemd: Unit [email protected] entered failed state.
Apr 17 14:33:24 mail systemd: [email protected] failed.
Apr 17 14:36:09 mail systemd: Started Plesk task: ext-seafile-domain_install_monitor (task=687 process=687 trace=32764:643cf6e81c17a).
Apr 17 14:36:09 mail systemd: Started Plesk task: ext-seafile-domain_install (task=688 process=688 trace=32764:643cf6e81c17a).
Apr 17 14:36:27 mail seafile.sh: Seafile controller is already running, pid 29531
Apr 17 14:36:27 mail systemd: [email protected]: control process exited, code=exited status=1
Apr 17 14:36:27 mail systemd: Unit [email protected] entered failed state.
Apr 17 14:36:27 mail systemd: [email protected] failed.
Apr 17 14:39:14 mail seafile.sh: Seafile controller is already running, pid 29531
Apr 17 14:39:14 mail systemd: [email protected]: control process exited, code=exited status=1
Apr 17 14:39:14 mail systemd: Unit [email protected] entered failed state.
Apr 17 14:39:14 mail systemd: [email protected] failed.
Apr 17 14:50:55 mail systemd: Started Plesk task: ext-seafile-domain_install_monitor (task=689 process=689 trace=3597:643cfa5ee9a36).
Apr 17 14:50:55 mail systemd: Started Plesk task: ext-seafile-domain_install (task=690 process=690 trace=3597:643cfa5ee9a36).
Apr 17 14:51:14 mail seafile.sh: Seafile controller is already running, pid 29531
Apr 17 14:51:14 mail systemd: [email protected]: control process exited, code=exited status=1
Apr 17 14:51:14 mail systemd: Unit [email protected] entered failed state.
Apr 17 14:51:14 mail systemd: [email protected] failed.
Apr 17 14:53:50 mail seafile.sh: Seafile controller is already running, pid 29531
Apr 17 14:53:50 mail systemd: [email protected]: control process exited, code=exited status=1
Apr 17 14:53:50 mail systemd: Unit [email protected] entered failed state.
Apr 17 14:53:50 mail systemd: [email protected] failed.
Apr 18 10:55:39 mail systemd: Started Plesk task: ext-seafile-domain_install_monitor (task=703 process=703 trace=20635:643e14bac50bb).
Apr 18 10:55:39 mail systemd: Started Plesk task: ext-seafile-domain_install (task=704 process=704 trace=20635:643e14bac50bb).
Apr 18 10:56:01 mail seafile.sh: Seafile controller is already running, pid 29531
Apr 18 10:56:01 mail systemd: [email protected]: control process exited, code=exited status=1
Apr 18 10:56:01 mail systemd: Unit [email protected] entered failed state.
Apr 18 10:56:01 mail systemd: [email protected] failed.
 
● [email protected] - Seafile
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sel 2023-04-18 10:56:01 WIB; 9h ago

Apr 18 10:56:00 mail.marketindonesia.co.id systemd[1]: Starting Seafile...
Apr 18 10:56:01 mail.marketindonesia.co.id systemd[1]: [email protected]: control process exited, code=exited status=1
Apr 18 10:56:01 mail.marketindonesia.co.id systemd[1]: Failed to start Seafile.
Apr 18 10:56:01 mail.marketindonesia.co.id systemd[1]: Unit [email protected] entered failed state.
Apr 18 10:56:01 mail.marketindonesia.co.id systemd[1]: [email protected] failed.
 
This situation can be caused when the permissions of the /seafile subdirectory of the subscription are not correct. Could you please verify with ps -aux |grep wsgi that Seafile is truly running as the output from above logs suggest? It should output something like
Code: 
root 1832 0.0 0.1 111140 44996 ? S Oct08 0:07 python2.7 /var/www/vhosts/example.com/seafile/seafile-server-6.2.5/seahub/thirdpart/gunicorn seahub.wsgi:application -c /var/www/vhosts/example.com/seafile/seafile-server-6.2.5/runtime/seahub.conf -b 0.0.0.0:8000 --preload

The I suppose that owner and group of the seafile directory are root, are they?
ls -lahR /var/www/vhosts/example.com/seafile/ | grep root
Will probably look similar to this:
Code: 
-rw------- 1 root root 34 Oct 9 13:30 3169014891a3aa95b486b0e29e74fa1e.djcache
-rw------- 1 root root 24 Oct 9 12:52 43b472d9735b24b59fc61e61d5a98257.djcache
-rw------- 1 root root 994 Oct 9 14:54 ceec40422771f78d283f254429d1d993.djcache
-rw-r--r-- 1 root root 0 Dec 12 2019 access.log
-rw-r--r-- 1 root root 0 Dec 12 2019 error.log
-rw-r--r-- 1 root root 6 Oct 9 13:30 seahub.pid
lrwxrwxrwx 1 root root 27 May 13 14:45 custom -> ../../../seahub-data/custom
-rw-rw-r-- 1 jdoe psaserv 1.8K Jan 23 2018 rooturl.py
-rw-r--r-- 1 jdoe psaserv 649 Dec 12 2019 rooturl.pyc
-rw-r--r-- 1 root root 222 Oct 9 14:54 __init__.pyc
-rw-r--r-- 1 root root 1.2K Oct 9 14:54 formats.pyc
-rw-r--r-- 1 root root 2.2K Oct 8 20:07 runfcgi.pyc
-rw-r--r-- 1 root root 6.4K Oct 8 20:07 fastcgi.pyc
-rw-r--r-- 1 root root 2.7K Oct 8 20:07 daemonize.pyc
-rw-r--r-- 1 jdoe psaserv 26K Nov 30 2015 old_root.pem

If this is the case, then the issue can be fixed running
chown -R jdoe:psaserv /var/www/vhosts/example.com/seafile/

Instead of example.com in the above examples, your real domain needs to be entered.

If the above does not apply to your case, no reasonable further investigation can be done here on the forum. Instead, please then open a support ticket, because then a support engineer needs to look into your server to find the root cause.
 
root 9190 0.0 0.0 114884 980 pts/0 S+ 20:56 0:00 grep --color=auto wsgi
sysuser+ 29706 0.0 0.1 369636 10368 ? S Apr17 0:38 python3 /var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /var/www/vhosts/1uk.host/seafile/conf/gunicorn.conf.py -b 0.0.0.0:8211 --preload
sysuser+ 29721 0.0 0.1 369636 11788 ? S Apr17 0:00 python3 /var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /var/www/vhosts/1uk.host/seafile/conf/gunicorn.conf.py -b 0.0.0.0:8211 --preload
sysuser+ 29722 0.0 0.1 369636 12036 ? S Apr17 0:00 python3 /var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /var/www/vhosts/1uk.host/seafile/conf/gunicorn.conf.py -b 0.0.0.0:8211 --preload
sysuser+ 29723 0.0 0.1 369636 12052 ? S Apr17 0:00 python3 /var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /var/www/vhosts/1uk.host/seafile/conf/gunicorn.conf.py -b 0.0.0.0:8211 --preload
sysuser+ 29724 0.0 0.1 369636 12064 ? S Apr17 0:00 python3 /var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /var/www/vhosts/1uk.host/seafile/conf/gunicorn.conf.py -b 0.0.0.0:8211 --preload
sysuser+ 29725 0.0 0.1 369636 12048 ? S Apr17 0:00 python3 /var/www/vhosts/1uk.host/seafile/seafile-server-8.0.8/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /var/www/vhosts/1uk.host/seafile/conf/gunicorn.conf.py -b 0.0.0.0:8211 --preload
 
I have a similar problem!
I installed Seafile from the extensions and the installation crashed!
grep "extension/seafile" /var/log/plesk/panel.log
Click to expand...
[2023-12-20 19:57:48.455] 86797:658338653f173 ERR [extension/seafile] Error executing: ;'systemctl' 'start' 'seahub@8001''
[2023-12-20 19:57:48.455] 86797:658338653f173 ERR [extension/seafile] stderr: Job for [email protected] failed because the control process exited with error code.
[2023-12-20 19:57:48.455] 86797:658338653f173 ERR [extension/seafile] Failed to start the service
[2023-12-20 19:57:48.455] 86797:658338653f173 ERR [extension/seafile] Service initialisation faileddjdimpel.de
[2023-12-20 20:00:56.533] 87285:6583396c6630a ERR [extension/seafile] Error executing: ;'systemctl' 'start' 'seafile@8005''
[2023-12-20 20:00:56.533] 87285:6583396c6630a ERR [extension/seafile] stderr: Job for [email protected] failed because the control process exited with error code.
[2023-12-20 20:00:56.533] 87285:6583396c6630a ERR [extension/seafile] Failed to start the service
[2023-12-20 20:00:56.533] 87285:6583396c6630a ERR [extension/seafile] Service initialisation faileddjdimpel.de
[2023-12-20 20:12:37.815] 109407:65833bfc73644 ERR [extension/seafile] Error executing: ;'systemctl' 'start' 'seafile@8010''
[2023-12-20 20:12:37.815] 109407:65833bfc73644 ERR [extension/seafile] stderr: Job for [email protected] failed because the control process exited with error code.
[2023-12-20 20:12:37.815] 109407:65833bfc73644 ERR [extension/seafile] Failed to start the service
[2023-12-20 20:12:37.815] 109407:65833bfc73644 ERR [extension/seafile] Service initialisation faileddjdimpel.de
[2023-12-20 20:19:34.066] 153555:65833dcd96ef0 ERR [extension/seafile] Error executing: ;'systemctl' 'start' 'seafile@8015''
[2023-12-20 20:19:34.066] 153555:65833dcd96ef0 ERR [extension/seafile] stderr: Job for [email protected] failed because the control process exited with error code.
[2023-12-20 20:19:34.066] 153555:65833dcd96ef0 ERR [extension/seafile] Failed to start the service
[2023-12-20 20:19:34.066] 153555:65833dcd96ef0 ERR [extension/seafile] Service initialisation faileddjdimpel.de

grep seafile /var/log/messages
Click to expand...

Dec 20 19:57:39 charming-noyce [87093]: seafile-controller.c(536): No seafevents.

ps aux | grep seafile
Click to expand...

djdimpe+ 87095 0.0 0.0 60412 3332 ? Ss 19:57 0:00 /var/www/vhosts/djdimpel.de/seafile/seafile-server-8.0.8/seafile/bin/seafile-controller -c /var/www/vhosts/djdimpel.de/seafile/ccnet -d /var/www/vhosts/djdimpel.de/seafile/seafile-data -F /var/www/vhosts/djdimpel.de/seafile/conf
djdimpe+ 87097 0.0 0.0 1178104 11452 ? Ssl 19:57 0:00 seaf-server -F /var/www/vhosts/djdimpel.de/seafile/conf -c /var/www/vhosts/djdimpel.de/seafile/ccnet -d /var/www/vhosts/djdimpel.de/seafile/seafile-data -l /var/www/vhosts/djdimpel.de/seafile/logs/seafile.log -P /var/www/vhosts/djdimpel.de/seafile/pids/seaf-server.pid -p /var/www/vhosts/djdimpel.de/seafile/seafile-server-8.0.8/runtime
djdimpe+ 87559 0.0 0.0 1178104 11144 ? Ssl 20:00 0:00 seaf-server -F /var/www/vhosts/djdimpel.de/seafile/conf -c /var/www/vhosts/djdimpel.de/seafile/ccnet -d /var/www/vhosts/djdimpel.de/seafile/seafile-data -l /var/www/vhosts/djdimpel.de/seafile/logs/seafile.log -P /var/www/vhosts/djdimpel.de/seafile/pids/seaf-server.pid -p /var/www/vhosts/djdimpel.de/seafile/seafile-server-8.0.8/runtime
djdimpe+ 121665 0.0 0.0 1178104 11100 ? Ssl 20:12 0:00 seaf-server -F /var/www/vhosts/djdimpel.de/seafile/conf -c /var/www/vhosts/djdimpel.de/seafile/ccnet -d /var/www/vhosts/djdimpel.de/seafile/seafile-data -l /var/www/vhosts/djdimpel.de/seafile/logs/seafile.log -P /var/www/vhosts/djdimpel.de/seafile/pids/seaf-server.pid -p /var/www/vhosts/djdimpel.de/seafile/seafile-server-8.0.8/runtime
djdimpe+ 153922 0.0 0.0 1178104 11184 ? Ssl 20:19 0:00 seaf-server -F /var/www/vhosts/djdimpel.de/seafile/conf -c /var/www/vhosts/djdimpel.de/seafile/ccnet -d /var/www/vhosts/djdimpel.de/seafile/seafile-data -l /var/www/vhosts/djdimpel.de/seafile/logs/seafile.log -P /var/www/vhosts/djdimpel.de/seafile/pids/seaf-server.pid -p /var/www/vhosts/djdimpel.de/seafile/seafile-server-8.0.8/runtime
root 156814 0.0 0.0 6316 708 pts/0 S+ 20:50 0:00 grep seafile


I need help
 
You do not have to, but I cannot solve the issue from the information provided and as noone else has responded in this thread probably others cannot either. As Plesk has real engineers in their support, normally they are able to find out what the problem is when they can look into the server.
 
My server is from a hoster and not from Plesk.
I have installed plesk automatic from my hoster

Now i have installed my server new und try agin install Seafile from extension.
Inall is crashed once mor with error!
 
You must log in or register to reply here.

Similar threads

C
Issue Seafile: Extension Installation Error
Replies
13
Views
778
Kaspar
K
D
Resolved Seafile running- but "Failed to login: Internal server error" when trying to log in
Replies
7
Views
1K
DenizGelion
D
K
Issue not starting the following service:maldet.service,php-fpm.service,[email protected]
Replies
0
Views
286
kalombo
K
Dennis Rahmen
Issue Kolab (Apheleia IT AG) extensions
Replies
8
Views
3K
drdna
D
S
Issue Sitejet Builder
Replies
0
Views
198
Sopherl
S
Back
Top