Operations to perform:
Apply all migrations: accounts, acls, admin, applications, assets, audits, auth, authentication, captcha, common, contenttypes, django_cas_ng, django_celery_beat, jms_oidc_rp, notifications, ops, orgs, perms, rbac, sessions, settings, terminal, tickets, users
Running migrations:
No migrations to apply.
After migration, update builtin role permissions
- Update builtin roles
2023-06-08 09:27:54 Install builtin applets
Install or update applet: /opt/jumpserver/apps/terminal/applets/chrome
Install or update applet: /opt/jumpserver/apps/terminal/applets/dbeaver
2023-06-08 09:27:54 Thu Jun 8 09:27:54 2023
2023-06-08 09:27:54 JumpServer version v3.3.1, more see https://www.jumpserver.org
2023-06-08 09:28:27 Service start failed, exit: flower
我把容器里/data/flower.db删除但是过段时间又重新生成
时间不对吧,你这是6月8号的日志
重启时查看 docker logs jms_core
或者tail -f /data/jumpserver/logs/jumpserver.log
2023-07-19 14:21:50 Collect static files
2023-07-19 14:21:54 Collect static files done
2023-07-19 14:21:54 Check database structure change …
2023-07-19 14:21:54 Migrate model change to database …
Operations to perform:
Apply all migrations: accounts, acls, admin, applications, assets, audits, auth, authentication, captcha, common, contenttypes, django_cas_ng, django_celery_beat, jms_oidc_rp, notifications, ops, orgs, perms, rbac, sessions, settings, terminal, tickets, users
Running migrations:
No migrations to apply.
After migration, update builtin role permissions
- Update builtin roles
2023-07-19 14:21:56 Install builtin applets
Install or update applet: /opt/jumpserver/apps/terminal/applets/chrome
Install or update applet: /opt/jumpserver/apps/terminal/applets/dbeaver
2023-07-19 14:21:57 Wed Jul 19 14:21:57 2023
2023-07-19 14:21:57 JumpServer version v3.4.3, more see https://www.jumpserver.org
2023-07-19 14:22:31 Service start failed, exit: flower
只有下面的这些kubect logs 看到的这些日志
k8s 部署的吗?
可以找一下你的storeageclass 的持久化在哪看一下jumpserver.log
k8s 部署的
我看flower的日志有错误信息
File “/usr/local/lib/python3.9/shelve.py”, line 243, in open
return DbfilenameShelf(filename, flag, protocol, writeback)
File “/usr/local/lib/python3.9/shelve.py”, line 227, in init
Shelf.init(self, dbm.open(filename, flag), protocol, writeback)
File “/usr/local/lib/python3.9/dbm/init.py”, line 95, in open
return mod.open(file, flag, mode)
_gdbm.error: Malformed database file header
Traceback (most recent call last):
File “/usr/local/bin/celery”, line 8, in
sys.exit(main())
File “/usr/local/lib/python3.9/site-packages/celery/main.py”, line 15, in main
sys.exit(_main())
File “/usr/local/lib/python3.9/site-packages/celery/bin/celery.py”, line 217, in main
return celery(auto_envvar_prefix=“CELERY”)
File “/usr/local/lib/python3.9/site-packages/click/core.py”, line 1130, in call
return self.main(*args, **kwargs)
File “/usr/local/lib/python3.9/site-packages/click/core.py”, line 1055, in main
rv = self.invoke(ctx)
kubectl describe pod -n ns core_pod_name
看一下事件中有打印什么信息没
Normal Scheduled 8m13s default-scheduler Successfully assigned jms-k8s/jms-k8s-jumpserver-jms-core-6d5d944b68-r5nq2 to slave-01
Normal Pulled 7m25s (x2 over 8m12s) kubelet Container image “docker.io/jumpserver/core:v3.4.3” already present on machine
Normal Created 7m25s (x2 over 8m12s) kubelet Created container jms-core
Normal Started 7m25s (x2 over 8m12s) kubelet Started container jms-core
Warning Unhealthy 7m17s (x3 over 8m7s) kubelet Readiness probe failed: Get “http://172.31.145.197:8080/api/health/”: dial tcp 172.31.145.197:8080: connect: connection refused
Warning Unhealthy 7m14s (x2 over 8m4s) kubelet Liveness probe failed: Get “http://172.31.145.197:8080/api/health/”: dial tcp 172.31.145.197:8080: connect: connection refused
Warning Unhealthy 7m6s (x3 over 7m56s) kubelet Readiness probe failed: Get “http://172.31.145.197:8080/api/health/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 7m3s (x2 over 7m53s) kubelet Liveness probe failed: Get “http://172.31.145.197:8080/api/health/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
每次把容器里的data/flower.db删了就可以启动起来了,但是过一段时间又重启了,
我之前部署3.1版本,后来换了好几次版本现在换到3.4还是这个问题
这个有影响吗,我看我flower.db删除后现在服务就正常了,健康检测也是一直没过去,但是过段时间就会重启
健康检测重试几次才会判断失败,失败后就把pod重启了
把pod删除掉,让它重建试下?
你的日志持久化文件找到了吗?把jumpserver.log的日志打印拿全一些
找到了jumpserver.log但是里面没有日志哎
哦?你k8s是什么版本?修改了helm的什么东西了吗?
或者那你可以加入jumpserver的社区支持群,请求远程帮助,更实时些