1 回答

TA貢獻1853條經驗 獲得超9個贊
在過去的幾天里,我遇到了類似的問題。在進入盒子并運行后,我得到了這個日志:journalctl -u php7.0-fpm
Feb 14 09:53:47 vagrant systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Feb 14 09:53:47 vagrant update-alternatives[10343]: update-alternatives: error: alternative path /run/php/php7.0-fpm.sock doesn't exist
Feb 14 09:53:47 vagrant systemd[1]: php7.0-fpm.service: PID file /run/php/php7.0-fpm.pid not readable (yet?) after start-post: No such file or directory
Feb 14 09:55:17 vagrant systemd[1]: php7.0-fpm.service: Start-post operation timed out. Stopping.
Feb 14 09:55:17 vagrant systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Feb 14 09:55:17 vagrant systemd[1]: php7.0-fpm.service: Unit entered failed state.
Feb 14 09:55:17 vagrant systemd[1]: php7.0-fpm.service: Failed with result 'timeout'.
Feb 14 09:55:22 vagrant systemd[1]: Stopped The PHP 7.0 FastCGI Process Manager.
事實證明,PID文件路徑是錯誤的。
您可以在參數.pp 中更新 PID 文件變量。文件路徑:$pid_filepuphpet/puppet/modules/puphpet/manifests/php/params.pp
更新此值以銷毀并運行為我修復了此問題。run/php/php7.0-fpm.pidvagrant up
puphpet 存儲庫中還有一個包含此更改的拉取請求:https://github.com/AOEpeople/puppet-puphpet/commit/e3b50ce72b922c2649ac82979b02edfd4e3b8c0a
- 1 回答
- 0 關注
- 121 瀏覽
添加回答
舉報