执行 ./jms start时候报错

来源：5-1 JumpServer介绍

慕桂英1419664

2018-12-20

(py3) [root@kvmserver jumpserver]# ./jms start
Thu Dec 20 14:52:14 2018
Jumpserver version 1.4.6, more see https://www.jumpserver.org
Check database connection …
2018-12-20 14:52:47 [signals_handler DEBUG] Receive django ready signal
2018-12-20 14:52:47 [signals_handler DEBUG] - fresh all settings
users
[X] 0001_initial
[X] 0002_auto_20171225_1157
[X] 0003_auto_20180101_0046
[X] 0004_auto_20180125_1218
[X] 0005_auto_20180306_1804
[X] 0006_auto_20180411_1135
[X] 0007_auto_20180419_1036
[X] 0008_auto_20180425_1516
[X] 0009_auto_20180517_1537
[X] 0010_auto_20180606_1505
[X] 0011_user_source
[X] 0012_auto_20180710_1641
[X] 0013_auto_20180807_1116
[X] 0014_auto_20180816_1652
[X] 0015_auto_20181105_1112
[X] 0016_auto_20181109_1505
[X] 0017_auto_20181123_1113
Database connect success
Check database structure change …
Migrate model change to database …
2018-12-20 14:53:20 [signals_handler DEBUG] Receive django ready signal
2018-12-20 14:53:20 [signals_handler DEBUG] - fresh all settings
System check identified some issues:

WARNINGS:
?: (mysql.W002) MySQL Strict Mode is not set for database connection 'default’
HINT: MySQL’s Strict Mode fixes many data integrity problems in MySQL, such as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/2.1/ref/databases/#mysql-sql-mode
Operations to perform:
Apply all migrations: admin, assets, audits, auth, captcha, common, contenttypes, django_celery_beat, ops, orgs, perms, sessions, terminal, users
Running migrations:
No migrations to apply.
Collect static files
2018-12-20 14:53:53 [signals_handler DEBUG] Receive django ready signal
2018-12-20 14:53:53 [signals_handler DEBUG] - fresh all settings

0 static files copied to ‘/opt/jumpserver/data/static’, 550 unmodified.

Start Gunicorn WSGI HTTP Server
Start Celery as Distributed Task Queue
Start Beat as Periodic Task Scheduler
[2018-12-20 14:53:54 +0800] [13822] [INFO] Starting gunicorn 19.9.0
[2018-12-20 14:53:54 +0800] [13822] [INFO] Listening at: http://0.0.0.0:8080 (13822)
[2018-12-20 14:53:54 +0800] [13822] [INFO] Using worker: gthread
[2018-12-20 14:53:54 +0800] [13833] [INFO] Booting worker with pid: 13833
[2018-12-20 14:53:54 +0800] [13834] [INFO] Booting worker with pid: 13834
[2018-12-20 14:53:54 +0800] [13835] [INFO] Booting worker with pid: 13835
[2018-12-20 14:53:54 +0800] [13836] [INFO] Booting worker with pid: 13836
[2018-12-20 14:54:24 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13833)
[2018-12-20 14:54:24 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13834)
[2018-12-20 14:54:24 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13835)
[2018-12-20 14:54:24 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13836)
[2018-12-20 14:54:25 +0800] [13833] [INFO] Worker exiting (pid: 13833)
[2018-12-20 14:54:25 +0800] [13834] [INFO] Worker exiting (pid: 13834)
[2018-12-20 14:54:25 +0800] [13836] [INFO] Worker exiting (pid: 13836)
[2018-12-20 14:54:25 +0800] [13835] [INFO] Worker exiting (pid: 13835)
[2018-12-20 14:54:25 +0800] [13854] [INFO] Booting worker with pid: 13854
[2018-12-20 14:54:25 +0800] [13855] [INFO] Booting worker with pid: 13855
[2018-12-20 14:54:25 +0800] [13856] [INFO] Booting worker with pid: 13856
[2018-12-20 14:54:25 +0800] [13857] [INFO] Booting worker with pid: 13857
celery beat v4.1.0 (latentcall) is starting.
2018-12-20 14:54:27 [signals_handler DEBUG] Receive django ready signal
2018-12-20 14:54:27 [signals_handler DEBUG] - fresh all settings
2018-12-20 14:54:27 [signals_handler DEBUG] Receive django ready signal
2018-12-20 14:54:27 [signals_handler DEBUG] - fresh all settings
/opt/py3/lib/python3.6/site-packages/celery/platforms.py:795: RuntimeWarning: You’re running the worker with superuser privileges: this is
absolutely not recommended!

Please specify a different user using the -u option.

User information: uid=0 euid=0 gid=0 egid=0

uid=uid, euid=euid, gid=gid, egid=egid,
__ - … __ - _
LocalTime -> 2018-12-20 14:54:29
Configuration ->
. broker -> redis://:**@192.168.4.1:6379/3
. loader -> celery.loaders.app.AppLoader
. scheduler -> django_celery_beat.schedulers.DatabaseScheduler

. logfile -> [stderr]@%INFO
. maxinterval -> 1.00 minute (60.0s)

beat: Starting…
Writing entries…

-------------- celery@kvmserver.example.com v4.1.0 (latentcall)
---- **** -----
— * *** * – Linux-3.10.0-514.el7.x86_64-x86_64-with-centos-7.3.1611-Core 2018-12-20 14:54:29
– * - **** —

** ---------- [config]
** ---------- .> app: jumpserver:0x7f7917a09710
** ---------- .> transport: redis://:**@192.168.4.1:6379/3
** ---------- .> results: redis://:**@192.168.4.1:6379/3
*** — * — .> concurrency: {min=4, max=20} (prefork)
– ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
— ***** -----
-------------- [queues]
.> celery exchange=celery(direct) key=celery

[tasks]
. assets.tasks.push_system_user_a_asset_manual
. assets.tasks.push_system_user_to_assets
. assets.tasks.push_system_user_to_assets_manual
. assets.tasks.push_system_user_util
. assets.tasks.set_assets_hardware_info
. assets.tasks.set_system_user_connectivity_info
. assets.tasks.test_admin_user_connectability_period
. assets.tasks.test_admin_user_connectivity_manual
. assets.tasks.test_admin_user_connectivity_period
. assets.tasks.test_admin_user_connectivity_util
. assets.tasks.test_asset_connectivity_manual
. assets.tasks.test_asset_connectivity_util
. assets.tasks.test_system_user_connectability_period
. assets.tasks.test_system_user_connectivity_a_asset
. assets.tasks.test_system_user_connectivity_manual
. assets.tasks.test_system_user_connectivity_period
. assets.tasks.test_system_user_connectivity_util
. assets.tasks.update_asset_hardware_info_manual
. assets.tasks.update_assets_hardware_info_period
. assets.tasks.update_assets_hardware_info_util
. common.tasks.send_mail_async
. ops.tasks.hello
. ops.tasks.hello_callback
. ops.tasks.run_ansible_task
. ops.tasks.run_command_execution
. terminal.tasks.clean_expired_session_period
. terminal.tasks.clean_orphan_session
. terminal.tasks.delete_terminal_status_period
. users.tasks.check_password_expired
. users.tasks.check_password_expired_periodic
. users.tasks.write_login_log_async

Connected to redis://:**@192.168.4.1:6379/3
mingle: searching for neighbors
mingle: all alone
2018-12-20 14:54:30 [signal_handler DEBUG] Start need start task: [users.tasks.check_password_expired_periodic, terminal.tasks.delete_terminal_status_period, terminal.tasks.clean_orphan_session, terminal.tasks.clean_expired_session_period]
Start need start task: [users.tasks.check_password_expired_periodic, terminal.tasks.delete_terminal_status_period, terminal.tasks.clean_orphan_session, terminal.tasks.clean_expired_session_period]
/opt/py3/lib/python3.6/site-packages/celery/fixups/django.py:202: UserWarning: Using settings.DEBUG leads to a memory leak, never use this setting in production environments!
warnings.warn('Using settings.DEBUG leads to a memory leak, never '
celery@kvmserver.example.com ready.
Received task: users.tasks.check_password_expired_periodic[9da8fd7b-a288-4762-8ba1-8cf766a140f4]
Received task: terminal.tasks.delete_terminal_status_period[b48621d2-5bcd-4da5-83fb-3d1b0ce884e2]
Received task: terminal.tasks.clean_orphan_session[713dcc5d-2c15-4101-8114-03f8f26cf27a]
Received task: terminal.tasks.clean_expired_session_period[870c17f4-dc36-4618-99c2-2bbdd720041c]
Signal handler <function pre_run_task_signal_handler at 0x7f790d934f28> raised: FileExistsError(17, ‘File exists’)
Traceback (most recent call last):
File “/opt/py3/lib/python3.6/site-packages/celery/utils/dispatch/signal.py”, line 227, in send
response = receiver(signal=self, sender=sender, **named)
File “/opt/jumpserver/apps/ops/celery/signal_handler.py”, line 78, in pre_run_task_signal_handler
os.makedirs(os.path.dirname(full_path))
File “/usr/local/python/lib/python3.6/os.py”, line 220, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/opt/jumpserver/data/celery/2018-12-20’
Task terminal.tasks.delete_terminal_status_period[b48621d2-5bcd-4da5-83fb-3d1b0ce884e2] succeeded in 0.12817315299980692s: None
Start clean expired session record, commands and replay
Task terminal.tasks.clean_expired_session_period[870c17f4-dc36-4618-99c2-2bbdd720041c] succeeded in 0.1363370400013082s: None
Task terminal.tasks.clean_orphan_session[713dcc5d-2c15-4101-8114-03f8f26cf27a] succeeded in 0.13628715300001204s: None
Task users.tasks.check_password_expired_periodic[9da8fd7b-a288-4762-8ba1-8cf766a140f4] succeeded in 0.1576876409999386s: None
**Signal handler <function post_run_task_signal_handler at 0x7f790d93c0d0> raised: AttributeError("‘check_password_expired_periodic’ object has no attribute ‘log_f’",)
Traceback (most recent call last):
File “/opt/py3/lib/python3.6/site-packages/celery/utils/dispatch/signal.py”, line 227, in send
response = receiver(signal=self, sender=sender, named)
File “/opt/jumpserver/apps/ops/celery/signal_handler.py”, line 100, in post_run_task_signal_handler
task.log_f.flush()
AttributeError: ‘check_password_expired_periodic’ object has no attribute 'log_f’
[2018-12-20 14:54:55 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13854)
[2018-12-20 14:54:55 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13855)
[2018-12-20 14:54:55 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13856)
[2018-12-20 14:54:55 +0800] [13822] [CRITICAL] WORKER TIMEOUT (pid:13857)