[已解决]ubuntu 安装专业版服务器到最后 启动的时候报错,求助

已解决,因为自己的粗心大意加熬夜修仙,公示自己犯的无脑错误如下:

  1. ubuntu 18.04.3 本身没问题,安装好干净系统后,没有把源设置为国内的(如 清华大学 https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/)导致更新速度慢的要死,冤枉熬夜(活该)。
  2. 下载seafile PRO server 服务器文件时,没有仔细看目录,明明是 [seafile-pro-server_7.0.9_x86-64.tar.gz]结果眼花看到下面的 [seafile-pro-server_7.0.9_x86-64_Ubuntu.tar.gz] 还怪人家写文档的没更新(安装的时候安装程序提示要前面那个文件,还自作聪明的把后面那个改名)(无语:joy:
  3. 改正以上两个错误,现在在本地虚拟机顺利安装完成。
    总结: 别人安装都没问题,就不要怀疑官方文档没更新,多怀疑自己!:laughing::laughing::laughing:
    最后,感谢帮助我的 hulk 朋友,谢谢!

===============已解决!=================

root@seafile_pro_servers:~# service seafile-server start
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.
root@seafile_pro_servers:~# systemctl status seafile-server.service
● seafile-server.service - LSB: Seafile server
Loaded: loaded (/etc/init.d/seafile-server; generated)
Active: failed (Result: exit-code) since Thu 2019-10-10 18:16:32 UTC; 2min 16s ago
Docs: man:systemd-sysv-generator(8)
Process: 17473 ExecStart=/etc/init.d/seafile-server start (code=exited, status=1/FAILURE)
Tasks: 65 (limit: 4660)
CGroup: /system.slice/seafile-server.service
├─17287 /opt/seafile/seafile-pro-server-7.0.9/seafile/bin/seafile-controller -c /opt/seafile/ccnet -d /opt/seafile/seafile-data -F /opt/seafile/conf
├─17290 ccnet-server -F /opt/seafile/conf -c /opt/seafile/ccnet -f /opt/seafile/logs/ccnet.log -d -L /opt/seafile -P /opt/seafile/pids/ccnet.pid
├─17291 seaf-server -F /opt/seafile/conf -c /opt/seafile/ccnet -d /opt/seafile/seafile-data -l /opt/seafile/logs/seafile.log -P /opt/seafile/pids/seaf-server.pid -f -L
├─17292 /usr/bin/python2.7 -m seafevents.main --config-file /opt/seafile/conf/seafevents.conf --logfile /opt/seafile/logs/seafevents.log -P /opt/seafile/pids/seafevents
├─17294 /usr/bin/python2.7 -m wsgidav.server.run_server runfcgi --log-file /opt/seafile/logs/seafdav.log --pid /opt/seafile/pids/seafdav.pid --port 8080 --host localhos
└─17295 /usr/bin/java -Xms512m -Xmx1g -XX:-AssumeMP -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch

Oct 10 18:16:31 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:16:31 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17294 (python2.7) in control group while starting unit. Ignoring.
Oct 10 18:16:31 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:16:31 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17295 (java) in control group while starting unit. Ignoring.
Oct 10 18:16:31 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:16:31 seafile_pro_servers systemd[1]: Starting LSB: Seafile server…
Oct 10 18:16:32 seafile_pro_servers sudo[17482]: pam_unix(sudo:session): session closed for user seafile
Oct 10 18:16:32 seafile_pro_servers systemd[1]: seafile-server.service: Control process exited, code=exited status=1
Oct 10 18:16:32 seafile_pro_servers systemd[1]: seafile-server.service: Failed with result ‘exit-code’.
Oct 10 18:16:32 seafile_pro_servers systemd[1]: Failed to start LSB: Seafile server.
lines 1-24/24 (END)

Oct 10 18:17:01 seafile_pro_servers CRON[17492]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 10 18:17:01 seafile_pro_servers CRON[17493]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 10 18:17:01 seafile_pro_servers CRON[17492]: pam_unix(cron:session): session closed for user root
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17287 (seafile-control) in control group while starting unit. Ignoring.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:26:24 seafile_pro_servers sudo[17528]: root : TTY=unknown ; PWD=/ ; USER=seafile ; COMMAND=/opt/seafile/seafile-server-latest/seafile.sh start
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17290 (ccnet-server) in control group while starting unit. Ignoring.
Oct 10 18:26:24 seafile_pro_servers sudo[17528]: pam_unix(sudo:session): session opened for user seafile by (uid=0)
Oct 10 18:26:24 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:26:24 seafile_pro_servers sudo[17528]: pam_unix(sudo:session): session closed for user seafile
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17291 (seaf-server) in control group while starting unit. Ignoring.
Oct 10 18:26:24 seafile_pro_servers sudo[17536]: root : TTY=unknown ; PWD=/ ; USER=seafile ; COMMAND=/opt/seafile/seafile-server-latest/seahub.sh start
Oct 10 18:26:24 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:26:24 seafile_pro_servers sudo[17536]: pam_unix(sudo:session): session opened for user seafile by (uid=0)
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17292 (python2.7) in control group while starting unit. Ignoring.
Oct 10 18:26:24 seafile_pro_servers sudo[17536]: pam_unix(sudo:session): session closed for user seafile
Oct 10 18:26:24 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17294 (python2.7) in control group while starting unit. Ignoring.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Found left-over process 17295 (java) in control group while starting unit. Ignoring.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: Starting LSB: Seafile server…
– Subject: Unit seafile-server.service has begun start-up
– Defined-By: systemd
– Support: http://www.ubuntu.com/support

– Unit seafile-server.service has begun starting up.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Control process exited, code=exited status=1
Oct 10 18:26:24 seafile_pro_servers systemd[1]: seafile-server.service: Failed with result ‘exit-code’.
Oct 10 18:26:24 seafile_pro_servers systemd[1]: Failed to start LSB: Seafile server.
– Subject: Unit seafile-server.service has failed
– Defined-By: systemd
– Support: http://www.ubuntu.com/support

– Unit seafile-server.service has failed.

– The result is RESULT.
lines 2170-2232/2232 (END)

ubuntu-18.04.3-live-server-amd64

好奇怪啊。。。。

好像是有个lib64目录不存在导致的:
Oct 11 02:37:32 seafile_pro_servers python2.7[1810]: looking for plugins in ‘/usr/lib64/sasl2’, failed to open directory, error: No such file or directory

=============更新=============
以下文章来源:ubuntu - Looking for plugins in '/usr/lib64/sasl2' - failed to open directory - Unix & Linux Stack Exchange

The same situation happens at all the different environments where our services run on:

  • Ubuntu 19.04 (XFCE4)
  • Ubuntu 18.04 (GNOME)
  • Ubuntu 16.04 (GNOME)
  • Raspbian buster
  • Raspbian stretch

What does the log mean? What does it relate to? How to fix it?

That error indicates that the script was looking for a library directory in your library folder, but it doesn’t exist. In particular, it is looking for the sasl2 folder, located in /usr/lib64. SASL, the Simple Authentication and Security Library, is a library that is used for authentication for certain protocols such as POP, IMAP, etc.

Read more about SASL here.

Without knowing what the python scripts are, and what they’re intended to do, it’s hard to guess as to what exact use of SASL in the case of this script is, although a good guess is for email notifications of some sort of event - maybe a motion notification, based on how the scripts appear to be handling video processing. Did a component of your scripts stop working, or is it just the log message that is new?

Since it is simply a debug log message, if none of your software is broken, it can (likely) be ignored. On the other hand, if your software isn’t working as expected, you might need to install the required library. Before installing SASL, however, check to see if it is simply hidden somewhere the python script can’t find it.

find / -name "libsasl*" 

On my Ubuntu 16.04 box, it was located in /usr/lib/x86_64-linux-gnu/sasl2. If this is the case for you, I’d try simply creating a symbolic link for the directory that the script is looking for:

ln -sfn /usr/lib/x86_64-linux-gnu/sasl2/ /usr/lib64/sasl2 

To install the library if necessary, use apt (you might still need to create a symbolic link or change the script, depending on the installation directory).

sudo apt-get install libsasl2-2

As an addendum, it’s interesting to me that the script is looking in /usr/lib64/sasl2, since it seems that Ubuntu killed off lib<32/64> directories in favor of a single lib directory for multiarch. This means that even when the correct libraries are installed, you might still be required to point the script toward the correct libsasl2 installation directory.

现在解决了报错文件目录找不到的问题:looking for plugins in ‘/usr/lib64/sasl2’, failed to open directory, error: No such file or directory
但还是无法启动,继续查原因。

================更新============
似乎和加密有关?

journalctl -xe

感觉都和那个SASL有关,网上查说是加密冲突了?

python2.7的环境有点问题吧,你用./seahub.sh start命令启动seahub服务,看有啥报错没

您好,感谢您的回复,似乎是可以启动:
LC_ALL is not set in ENV, set to en_US.UTF-8
Starting seahub at port 8000 …

Seahub is started

Done.

我是按手册里,脚本安装方式 安装的,很奇怪遇到这种问题,是不是需要重新安装?还是有其它办法解决?

建议你使用一个Ubuntu16的环境重新安装下吧,可以使用这里的全自动安装脚本:https://github.com/haiwen/seafile-server-installer-cn

您好,我就是按这里的脚本和帮助安装的,发现有些出入,但都能顺利装完,装完后就提示服务器启动失败,整个过程都没有任何错误。。。
我按您说的,重新弄个新干净的再试试,:rofl::rofl::rofl:
感谢:grin:

会不会是我下载的服务器版本太新了?

你下载安装包在哪下载的,可能是你下载的安装包不是ubuntu下的包,是centos下的包吧

是Ubuntu的,文件名有区别,而且这个脚本安装的时候,只认不带ubuntu的包,我得先改名字,再安装, 是英文网站上的

那安装包应该没错了,你换个ubuntu16.04的操作系统来部署吧
ubuntu18的环境默认带的是python3的环境

如果要安装专业版, 需要先将下载好的专业版的包 seafile-pro-server_6.0.13_x86-64.tar.gz 放到 /opt/ 目录下
脚本只认这个seafile-pro-server_6.0.13_x86-64.tar.gz 而不认seafile-pro-server_6.0.13_ubuntu_x86-64.tar.gz

对,但我用Python来看版本,是2.7.15+

python --version
Python 2.7.15+

实在不行也可以用docker来部署,这样系统环境的问题就不存在了
https://cloud.seafile.com/published/seafile-manual-cn/docker/pro-edition/用Docker部署Seafile.md

好的,实在不行只能Docker

新系统,更新完补丁升级啥的,再按那个一键脚本,还是一样的问题,看来是服务器和ubuntu 18.04.3 不兼容。


Your seafile server configuration has been finished successfully.

run seafile server: ./seafile.sh { start | stop | restart }
run seahub server: ./seahub.sh { start | stop | restart }


If you are behind a firewall, remember to allow input/output of these tcp ports:

port of seafile fileserver: 8082
port of seahub: 8000

When problems occur, Refer to

    https://github.com/haiwen/seafile/wiki

for information.

** Message: seafile-controller.c(1157): loading seafdav config from /opt/seafile/conf/seafdav.conf

[10/11/19 10:32:05] …/common/session.c(139): using config file /opt/seafile/conf/ccnet.conf
[10/11/19 10:32:05] …/common/license.c(406): Loading license file /opt/seafile/seafile-license.txt …
[10/11/19 10:32:05] …/common/license.c(409): License file /opt/seafile/seafile-license.txt does not exist, allow at most 3 trial users
License file /opt/seafile/seafile-license.txt does not exist, allow at most 3 trial users
Starting seafile server, please wait …
** Message: seafile-controller.c(1157): loading seafdav config from /opt/seafile/conf/seafdav.conf

Seafile server started

Done.

LC_ALL is not set in ENV, set to en_US.UTF-8
Starting seahub at port 8000 …


Successfully created seafile admin

Seahub is started

Done.

Seahub is not running
Done.

Stopping seafile server …
Done.
Starting productive 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.
root@seafile_pro:~#

一样的问题, 首先就是
seafile_pro python2.7[16490]: looking for plugins in ‘/usr/lib64/sasl2’, failed to open directory, error: No such file or directory
这个上面就有解决办法,但后面那个类似加密冲突就不知道怎么搞了