On the problem of self-booting of Seafile

I follow:
RHEL/CentOS (run as service) in the document ( https://manual-cn.seafile.com...)-- at RHEL/CentOS we use the / etc/init.d/ script to enable the seafile/seahub service to boot itself.
sets it up, but when I run the last step: "
and run:
service seafile start
service seahub start"
, the following prompt appears:
Starting seafile (via systemctl): Job for seafile.service failed because the control process exited with error code. See "systemctl status seafile.service" and "journalctl-xe" for details.
[FAILED]

run the command "systemctl status seafile.service" to get
seafile.service-SYSV: seafile
Loaded: loaded (/ etc/rc.d/init.d/seafile; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2019-01-11 14:29:43 CST; 1h 21min ago
Docs: man:systemd-sysv-generator (8)
< strong Process: 28084 ExecStart=/etc/rc.d/init.d/seafile start (code=exited, status=1/FAILURE)

Jan 11 14:29:43 VM_189_195_centos systemd [1]: Starting SYSV: seafile...
Jan 11 14:29:43 VM_189_195_centos su [28088]: (to root) root on none
Jan 11 14:29:43 VM_189_195_centos systemd [1]: seafile.service: control process exited Code=exited status=1
Jan 11 14:29:43 VM_189_195_centos seafile [28084]: Starting seafile:
Jan 11 14:29:43 VM_189_195_centos systemd [1]: Failed to start SYSV: seafile.
Jan 11 14:29:43 VM_189_195_centos systemd [1]: Unit seafile.service entered failed state.
Jan 11 14:29:43 VM_189_195_centos systemd [1]: seafile.service failed.

I think all my previous steps are correct. How should I solve this problem? * *

Apr.17,2022
Menu