2019-02-06 13:30:36,825 CRIT Supervisor running as root (no user in config file)
2019-02-06 13:30:36,825 INFO Included extra file “/etc/supervisor/conf.d/bluelog.conf” during parsing
2019-02-06 13:30:36,892 INFO RPC interface ‘supervisor’ initialized
2019-02-06 13:30:36,892 INFO RPC interface ‘supervisor’ initialized
2019-02-06 13:30:36,892 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
2019-02-06 13:30:36,894 INFO daemonizing the supervisord process
2019-02-06 13:30:36,894 INFO supervisord started with pid 1613
2019-02-06 13:30:37,897 INFO spawned: ‘bluelog’ with pid 1614
2019-02-06 13:30:38,785 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:30:39,788 INFO spawned: ‘bluelog’ with pid 1627
2019-02-06 13:30:40,752 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:30:42,756 INFO spawned: ‘bluelog’ with pid 1640
2019-02-06 13:30:43,715 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:30:46,722 INFO spawned: ‘bluelog’ with pid 1653
2019-02-06 13:30:47,668 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:30:48,670 INFO gave up: bluelog entered FATAL state, too many start retries too quickly
2019-02-06 13:30:55,302 INFO spawned: ‘bluelog’ with pid 1666
2019-02-06 13:30:56,246 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:30:57,249 INFO spawned: ‘bluelog’ with pid 1679
2019-02-06 13:30:58,217 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:30:59,253 ERRO 192.168.1.114:61618 - - [06/Feb/2019:05:30:59 +0800] “GET /?message=ERROR%3A%20Process%20bluelog%3A%20spawn%20error HTTP/1.1” 200 2603
2019-02-06 13:31:00,386 INFO spawned: ‘bluelog’ with pid 1692
2019-02-06 13:31:01,462 INFO success: bluelog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-02-06 13:31:01,462 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:31:02,467 INFO spawned: ‘bluelog’ with pid 1705
2019-02-06 13:31:03,387 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:31:04,391 INFO spawned: ‘bluelog’ with pid 1718
2019-02-06 13:31:05,297 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:31:07,304 INFO spawned: ‘bluelog’ with pid 1731
2019-02-06 13:31:08,246 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:31:11,252 INFO spawned: ‘bluelog’ with pid 1744
2019-02-06 13:31:12,171 INFO exited: bluelog (exit status 1; not expected)
2019-02-06 13:31:13,173 INFO gave up: bluelog entered FATAL state, too many start retries too quickl
一直报错