我從here復制了以作為守護進程運行Python代碼。

為了延長正常運行時間。我想最好使用supervisor來保持這個守護進程的運行。

我做到了。

python_deamon.conf[program:python_deamon]

directory=/usr/local/python_deamon/

command=/usr/local/python_venv/bin/python daemon_runnner.py start

stderr_logfile=/var/log/gunicorn.log

stdout_logfile=/var/log/gunicorn.log

autostart=true

autorestart=true

問題是，盡管supervisor成功地啟動了python_守護進程，但它仍在重試。2015-09-23 16:10:45,592 CRIT Supervisor running as root (no user in config file)

2015-09-23 16:10:45,592 WARN Included extra file "/etc/supervisor/conf.d/python_daemon.conf" during parsing

2015-09-23 16:10:45,592 INFO RPC interface 'supervisor' initialized

2015-09-23 16:10:45,592 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2015-09-23 16:10:45,592 INFO supervisord started with pid 13880

2015-09-23 16:10:46,595 INFO spawned: 'python_deamon' with pid 17884

2015-09-23 16:10:46,611 INFO exited: python_deamon (exit status 1; not expected)

2015-09-23 16:10:47,614 INFO spawned: 'python_deamon' with pid 17885

2015-09-23 16:10:47,630 INFO exited: python_deamon (exit status 1; not expected)

2015-09-23 16:10:49,635 INFO spawned: 'python_deamon' with pid 17888

2015-09-23 16:10:49,656 INFO exited: python_deamon (exit status 1; not expected)

2015-09-23 16:10:52,662 INFO spawned: 'python_deamon' with pid 17891

2015-09-23 16:10:52,680 INFO exited: python_deamon (exit status 1; not expected)

2015-09-23 16:10:53,681 INFO gave up: python_deamon entered FATAL state, too many start retries too quickly

為了記錄重寫后的run()方法，我從不返回任何內容。

有沒有可能做我想做的事，或者我是在裝傻？

p.S：我知道整個問題的根本原因是，由于run()從不返回任何主管一直試圖啟動它，因此認為進程失敗，并將狀態設為FATAL Exited too quickly (process log may have details)。

我真正的問題是我做得對嗎？或者可以這樣做？

p.p.S：獨立(不帶主管)daemon_runnner.py在有和沒有sudo權限的情況下運行良好。

總結

以上是生活随笔為你收集整理的supervisor python_使用supervisor运行python脚本的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。