こちらを参考にPHPの起動を試みたのですが、失敗してしまいました。
「sudo systemctl restart php-fpm」を実行した際のエラーは下記の内容です
Job for php-fpm.service failed because the control process exited with error code. See "systemctl status php-fpm.service" and "journalctl -xe" for details.
「sudo systemctl status php-fpm.service」を実行した際の結果は下記の通りです。
php-fpm.service - The PHP FastCGI Process Manager Loaded: loaded (/usr/lib/systemd/system/php-fpm.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2020-06-06 09:57:18 UTC; 7min ago Process: 9787 ExecStart=/usr/sbin/php-fpm --nodaemonize (code=exited, status=78) Main PID: 9787 (code=exited, status=78) Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: Starting The PHP FastCGI Process Manager... Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal php-fpm[9787]: [06-Jun-2020 09:57:18] ALERT: [pool www] user has not been defined Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal php-fpm[9787]: [06-Jun-2020 09:57:18] ERROR: failed to post process the configuration Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal php-fpm[9787]: [06-Jun-2020 09:57:18] ERROR: FPM initialization failed Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: php-fpm.service: main process exited, code=exited, status=78/n/a Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: Failed to start The PHP FastCGI Process Manager. Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: Unit php-fpm.service entered failed state. Jun 06 09:57:18 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: php-fpm.service failed.
PHPの起動方法に関するアドバイスを頂けましたら幸いです。
追記
「sudo journalctl -xe」の実行結果は以下になります。
h-4.2$ sudo journalctl -xe
Jun 06 09:57:37 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: Created slice User Slice of root.
-- Subject: Unit user-0.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit user-0.slice has finished starting up.
-- The start-up result is done.
Jun 06 09:57:37 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: Starting User Slice of root.
-- Subject: Unit user-0.slice has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit user-0.slice has begun starting up.
Jun 06 09:57:37 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: Started Session c17 of user root.
-- Subject: Unit session-c17.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c17.scope has finished starting up.
-- The start-up result is done.
Jun 06 09:57:37 ip-172-31-10-96.ap-northeast-1.compute.internal systemd-logind[2687]: New session c17 of user root.
-- Subject: A new session c17 has been created for user root
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
-- A new session with the ID c17 has been created for the user root.
-- The leading process of the session is 9800.
Jun 06 09:57:37 ip-172-31-10-96.ap-northeast-1.compute.internal systemd[1]: Starting Session c17 of user root.
-- Subject: Unit session-c17.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c17.scope has begun starting up.
Jun 06 09:57:37 ip-172-31-10-96.ap-northeast-1.compute.internal sudo[9800]: pam_unix(sudo:session): session opened for user root by (uid=0)
回答1件
あなたの回答
tips
プレビュー