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 关注
- 102 浏览
添加回答
举报