Hi everyone,
after executing #bench update the frappe-bench-frappe-web is unable to start, the error showing as below:
Please advise how to fix it.
Thank you.
2016-10-28 05:03:45,463 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
2016-10-28 05:03:45,463 INFO supervisord started with pid 9326
2016-10-28 05:03:46,465 INFO spawned: ‘syncthing’ with pid 9351
2016-10-28 05:03:46,467 INFO spawned: ‘frappe-bench-frappe-default-worker-0’ with pid 9352
2016-10-28 05:03:46,468 INFO spawned: ‘frappe-bench-frappe-schedule’ with pid 9353
2016-10-28 05:03:46,470 INFO spawned: ‘frappe-bench-frappe-long-worker-0’ with pid 9354
2016-10-28 05:03:46,472 INFO spawned: ‘frappe-bench-frappe-short-worker-0’ with pid 9355
2016-10-28 05:03:46,474 INFO spawned: ‘frappe-bench-frappe-web’ with pid 9360
2016-10-28 05:03:46,476 INFO spawned: ‘frappe-bench-node-socketio’ with pid 9361
2016-10-28 05:03:46,478 INFO spawned: ‘frappe-bench-redis-queue’ with pid 9362
2016-10-28 05:03:46,480 INFO spawned: ‘frappe-bench-redis-cache’ with pid 9364
2016-10-28 05:03:46,482 INFO spawned: ‘frappe-bench-redis-socketio’ with pid 9365
2016-10-28 05:03:47,226 INFO exited: frappe-bench-frappe-web (exit status 1; not expected)
2016-10-28 05:03:47,511 INFO success: syncthing entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-frappe-default-worker-0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-frappe-schedule entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-frappe-long-worker-0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-frappe-short-worker-0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-node-socketio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-redis-queue entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-redis-cache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:47,511 INFO success: frappe-bench-redis-socketio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-10-28 05:03:48,755 INFO spawned: ‘frappe-bench-frappe-web’ with pid 9448
2016-10-28 05:03:49,076 INFO exited: frappe-bench-frappe-web (exit status 1; not expected)
2016-10-28 05:03:51,079 INFO spawned: ‘frappe-bench-frappe-web’ with pid 9471
2016-10-28 05:03:51,395 INFO exited: frappe-bench-frappe-web (exit status 1; not expected)
2016-10-28 05:03:54,645 INFO spawned: ‘frappe-bench-frappe-web’ with pid 9505
2016-10-28 05:03:54,960 INFO exited: frappe-bench-frappe-web (exit status 1; not expected)
2016-10-28 05:03:55,962 INFO gave up: frappe-bench-frappe-web entered FATAL state, too many start retries too quickly