k8s部署seafile报错

mserver [~]$ kubectl logs seafile-srv-0 -n production
*** Running /etc/my_init.d/01_create_data_links.sh…
*** Running /etc/my_init.d/10_syslog-ng.init…
Jul 5 01:24:59 seafile-srv-0 syslog-ng[28]: syslog-ng starting up; version=‘3.13.2’
*** Running /etc/my_init.d/99_mysql_setup.sh…
*** Booting runit daemon…
*** Runit started as PID 38
*** Running /scripts/start.py…
Jul 5 01:25:00 seafile-srv-0 cron[47]: (CRON) INFO (pidfile fd = 3)
Jul 5 01:25:00 seafile-srv-0 cron[47]: (CRON) INFO (Running @reboot jobs)
[2022-07-05 01:25:02] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.
[07/05/2022 01:25:02][upgrade]: The container was recreated, running minor-upgrade.sh to fix the media symlinks
[07/05/2022 01:25:02][upgrade]: Running script /opt/seafile/seafile-server-6.3.4/upgrade/minor-upgrade.sh


This script would do the minor upgrade for you.
Press [ENTER] to contiune


migrating avatars …

DONE

updating seafile-server-latest symbolic link to /opt/seafile/seafile-server-6.3.4 …

DONE

[07/05/22 01:25:02] …/common/session.c(132): using config file /opt/seafile/conf/ccnet.conf
Starting seafile server, please wait …
Seafile server started

Done.

Starting seahub at port 8000 …

Error: ‘/opt/seafile/conf/gunicorn.conf’ doesn’t exist
Error:Seahub failed to start.
Please try to run “./seahub.sh start” again
Traceback (most recent call last):
File “/scripts/start.py”, line 86, in
main()
File “/scripts/start.py”, line 72, in main
call(‘{} start’.format(get_script(‘seahub.sh’)))
File “/scripts/utils/init.py”, line 68, in call
return subprocess.check_call(*a, **kw)
File “/usr/lib/python2.7/subprocess.py”, line 190, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘/opt/seafile/seafile-server-6.3.4/seahub.sh start’ returned non-zero exit status 1
*** /scripts/start.py exited with status 1.
*** Shutting down runit daemon (PID 38)…
*** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown…
Jul 5 01:25:13 seafile-srv-0 syslog-ng[28]: syslog-ng shutting down; version=‘3.13.2’
*** Killing all processes…

无法连接数据库报错,seafile在k8s集群中部署时,在DB_HOST这个value需要写mariadb的svc的地址,如果写name的话,会导致无法连接数据库,报上面的错误

1 个赞

请问更改后可以正常运行吗?我更改后pod正常运行,当是前端仍然报502,seafile日志打印的最后一句为This is an idle script (infinite loop) to keep contailer running