| 
91porn邀请码1 综合本文主要先容 JumpServer 组件有关的常见问题处理【MXSPS-485】顔面騎乗でおマ●コべろべろ！絶頂クンニ4時間。 2 Core 启动很是2.1 问题神气在启动 JumpServer 处事时间，Core 组件启动很是，导致其他组件启动失败（举例：KoKo、Lion 等组件） # 启动 JumpServer 处事./jmsctl.sh start# 输出如下：Creating network "jms_net" with driver "bridge"Creating jms_mysql ... doneCreating jms_redis ... doneCreating jms_core ... doneERROR: for celery Container "76b2e315f69d" is unhealthy.ERROR: for lion Container "76b2e315f69d" is unhealthy.ERROR: for koko Container "76b2e315f69d" is unhealthy.ERROR: for web Container "76b2e315f69d" is unhealthy.ERROR: Encountered errors while bringing up the project.2.2 操作才智淌若出现上头组件报错 unhealthy 的诞妄，实行底下的号召，直到出现 Check service status 为止。 docker logs -f jms_core --tail 200# 淌若莫得报错就等表结构归拢完毕后，然后从头实行 start 即可2.2.1 启动化超时# 日记信息2023-03-16 18:15:08 [db_port INFO] Check oracle ports2023-03-16 18:15:08 Collect static files2023-03-16 18:15:08 Collect static files done2023-03-16 18:15:08 Check database structure change ...2023-03-16 18:15:08 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, xpackRunning migrations: Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK ··· 不详 Applying terminal.0021_auto_20200213_1316... OK Applying terminal.0022_session_is_success... OK Applying terminal.0023_command_risk_level... OK Applying terminal.0024_auto_20200715_1713... OK Applying terminal.0025_auto_20200810_1735... OK Applying terminal.0026_auto_20201027_1905... OK Applying terminal.0027_auto_20201102_1651... OK # 笃定这上头皆是深入 ok，不可有 error2023-03-16 18:18:26 [signal_handlers INFO] Create SystemMsgSubscription: package=ops type=ServerPerformanceMessage2023-03-16 18:18:26 Create SystemMsgSubscription: package=ops type=ServerPerformanceMessage2023-03-16 18:18:27 [signal_handlers INFO] Create SystemMsgSubscription: package=terminal type=CommandAlertMessage OKAfter migration, update builtin role permissions - Update builtin rolescomplete# 笃定上头皆是 ok 的莫得报错, 领导 Check service status 后就不错从头启动其他组件./jmsctl.sh start2.2.2 启动超时# 日记信息2023-03-16 18:20:16 [db_port INFO] Check oracle ports2023-03-16 18:20:16 Check database connection: 0System check identified no issues (0 silenced).2023-03-16 18:20:18 Database connect success2023-03-16 18:20:18 Collect static files2023-03-16 18:20:19 Collect static files done2023-03-16 18:20:19 Check database structure change ...2023-03-16 18:20:19 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, xpackRunning migrations: No migrations to apply.After migration, update builtin role permissions - Update builtin roles2023-03-16 18:20:22 Install builtin applets2023-03-16 18:20:22 Thu Mar 16 18:20:22 20232023-03-16 18:20:22 JumpServer version v3.0.3, more see https://www.jumpserver.org- Start Flower as Task Monitor- Start Gunicorn WSGI HTTP Server- Start heartbeat thread => ([Core]-ab-jms1-174)2023-03-16 18:20:23 Check service status: flower -> running at 262023-03-16 18:20:24 Check service status: gunicorn -> running at 272023-03-16 18:20:55 Check service status: flower -> running at 26# 笃定上头皆是 ok 的莫得报错, 领导 Check service status 后就不错从头启动其他组件./jmsctl.sh start3 Web 页面很是3.1 问题神气在用户探询 JumpServer 页面时，报错 "Server error occur, contact administrator" 3.2 问题处理# 检验是否有报错，淌若莫得粗略不齐备请干与容器检验日记docker logs -f jms_core --tail 200docker exec -it jms_core /bin/bashtail -f logs/jumpserver.log# 凭证内容报错处理4 Web 登陆失败4.1健忘密码，密码逾期淌若健忘密码粗略密码逾期，不错点击找回密码通过邮件找回，淌若无法通过邮件找回，不错通过适度台重置，操作才智如下： docker exec -it jms_core /bin/bashcd /opt/jumpserver/appspython manage.py shellfrom users.models import Useru = User.objects.get(username='admin')u.reset_password('password')u.save# admin 为你要修改的账户称号，password 为你要修改的密码4.2登录往往账号被锁定不错找解决员重置，解决员不错在对专揽户的个东谈主页面重置账号，粗略通过适度台重置，操作才智如下： docker exec -it jms_core /bin/bashcd /opt/jumpserver/appspython manage.py shellfrom django.core.cache import cachecache.delete_pattern('_LOGIN_BLOCK_*')cache.delete_pattern('_LOGIN_LIMIT_*')粗略也不错新建一个超等解决员来对其他用户进行开拓，操作才智如下： docker exec -it jms_core /bin/bashcd /opt/jumpserver/appspython manage.py shellfrom users.models import Useru = User.objects.get(username='admin')u.mfa_level='0'u.otp_secret_key=''u.save4.4 开拓了 LDAP 后无法登录淌若是开拓了 LDAP 后无法登录，请登录数据库禁用 ldap 登录，然后从头开拓 LDAP，操作才智如下： mysql -uroot -puse jumpserver;update settings_setting set value='false' where name='AUTH_LDAP';update settings_setting set enabled='0' where name='AUTH_LDAP';redis-cli -a $REDIS_PASSWORDselect 4keys *LDAP*del :1:_SETTING_AUTH_LDAP淌若是开拓 其他身份认证 后无法登录，不错使用腹地用户登录 Web 后在开拓内部从头竖立。 5 对于特权用户5.1财富测试可荟萃性、更新硬件信息 报 Permission denied 粗略 Authentication failure一般皆是特权用户账户密码不正确。 5.2财富测试可荟萃性、更新硬件信息 报 /usr/bin/python: not found一般出咫尺 Ubuntu 财富上，财富 Python 未装配粗略 Python 很是。 5.3 领导 timeout# 手动 ssh 登录领导 timeout 的那台处事器vi /etc/ssh/sshd_config# 修改 UseDNS 参数为 noUseDNS no# 重启 JumpServer 处事器的 docker 和 koko 组件处事systemctl restart dockerdocker restart jms_koko5.4Connect Websocket server error一般情况下是 Nginx 未竖立 Websocket 导致【MXSPS-485】顔面騎乗でおマ●コべろべろ！絶頂クンニ4時間，凭证反向代理 - JumpServer 文档进行修改后重启 Nginx 即可。
|
