[已解决] 腾讯企业邮箱配置seafile pro邮件配置，seahub重启失败

服务器问题
1

如图：
%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87_20190722173844

然后无法启动seahub

但是将邮件配置全部注释掉，seahub重启就成功。通过查看日志：

Jul 22 17:28:03 VM_0_8_centos systemd: Stopping Seafile Seahub…
Jul 22 17:28:03 VM_0_8_centos seahub.sh: Stopping seahub …
Jul 22 17:28:04 VM_0_8_centos seahub.sh: Done.
Jul 22 17:28:04 VM_0_8_centos systemd: Stopped Seafile Seahub.
Jul 22 17:28:04 VM_0_8_centos systemd: Starting Seafile Seahub…
Jul 22 17:28:04 VM_0_8_centos seahub.sh: LC_ALL is not set in ENV, set to en_US.UTF-8
Jul 22 17:28:04 VM_0_8_centos seahub.sh: Starting seahub at port 8000 …
Jul 22 17:28:05 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/thirdpart/gunicorn’
Jul 22 17:28:06 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:28:10 VM_0_8_centos seahub.sh: #033[33mError:Seahub failed to start.#033[m
Jul 22 17:28:10 VM_0_8_centos seahub.sh: Please try to run “./seahub.sh start” again
Jul 22 17:28:10 VM_0_8_centos systemd: seahub.service: main process exited, code=exited, status=1/FAILURE
Jul 22 17:28:10 VM_0_8_centos systemd: Failed to start Seafile Seahub.
Jul 22 17:28:10 VM_0_8_centos systemd: Unit seahub.service entered failed state.
Jul 22 17:28:10 VM_0_8_centos systemd: seahub.service failed.
Jul 22 17:28:14 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:28:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:29:01 VM_0_8_centos systemd: Started Session 439 of user root.
Jul 22 17:29:14 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:29:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:30:01 VM_0_8_centos systemd: Started Session 440 of user root.
Jul 22 17:30:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:30:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:31:01 VM_0_8_centos systemd: Started Session 441 of user root.
Jul 22 17:31:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:31:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:32:01 VM_0_8_centos systemd: Started Session 442 of user root.
Jul 22 17:32:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:32:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:33:01 VM_0_8_centos systemd: Started Session 443 of user root.
Jul 22 17:33:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:33:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:34:01 VM_0_8_centos systemd: Started Session 444 of user root.
Jul 22 17:34:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:34:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:34:32 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:34:33 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:34:33 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:34:33 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:35:01 VM_0_8_centos systemd: Started Session 445 of user root.
Jul 22 17:35:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:35:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:36:01 VM_0_8_centos systemd: Started Session 446 of user root.
Jul 22 17:36:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:36:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:37:01 VM_0_8_centos systemd: Started Session 447 of user root.
Jul 22 17:37:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:37:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:38:01 VM_0_8_centos systemd: Started Session 448 of user root.
Jul 22 17:38:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:38:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:38:32 VM_0_8_centos systemd-logind: Removed session 436.
Jul 22 17:38:32 VM_0_8_centos systemd: Removed slice User Slice of root.
Jul 22 17:39:01 VM_0_8_centos systemd: Created slice User Slice of root.
Jul 22 17:39:01 VM_0_8_centos systemd: Started Session 449 of user root.
Jul 22 17:39:01 VM_0_8_centos systemd: Removed slice User Slice of root.
Jul 22 17:39:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:39:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:40:01 VM_0_8_centos systemd: Created slice User Slice of root.
Jul 22 17:40:01 VM_0_8_centos systemd: Started Session 450 of user root.
Jul 22 17:40:01 VM_0_8_centos systemd: Removed slice User Slice of root.
Jul 22 17:40:15 VM_0_8_centos python2.7: detected unhandled Python exception in ‘/opt/seafile/seafile-pro-server-7.0.5/seahub/manage.py’
Jul 22 17:40:15 VM_0_8_centos python2.7: can’t communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
Jul 22 17:40:22 VM_0_8_centos systemd: Created slice User Slice of root.
Jul 22 17:40:22 VM_0_8_centos systemd: Started Session 451 of user root.

我发现是某个.py文件引起的。有人可以帮帮我吗:disappointed_relieved:

2

image
image797×245 39.6 KB

检查下这块配置的开头是不是多了个空格

4

@Hulk 我把空格删了还是不行
TLS改成SSL以及端口改为465也是不行

5

把 conf/gunicorn.conf 配置文件中的 daemon设置为False ，然后启动seahub，会打印报错信息到终端

6

@Hulk 目前是停留在systemctl restart seahub 上，但是web端，PC端,APP都能连接

7

那就是启动没问题，你把那个配置改回去，再重新启动。另外，我刚才让你重启seahub没说明，你不应该用systemctl的方式重启，你要切换到seafile用户，然后用 ./seahub.sh restart 这个命令重启

9

@Hulk

%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_20190723165108
%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_20190723165108977×263 6.71 KB

然后一直停在这里

10

这就是正常启动了，没有任何报错，刚才让你改的配置就是让程序运行在前端，你把那个配置改回去，重启就可以了。

11

@Hulk十分感谢。其实应该是我的单词拼错了。True→Ture:sweat_smile:

12

哈哈哈哈，和我一样，官方文档的坑:joy_cat: