Find whats preventing php7.0-fpm from starting
1
how can I figure out whats preventing me from starting php7.0-fpm. Nothing seems to show whats preventing it from starting.
$ sudo service php7.0-fpm status
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-08-11 16:52:04 EDT; 20h ago
Main PID: 4171 (code=exited, status=78)
Aug 11 16:52:04 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: FPM initialization failed
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 11 16:52:04 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
trying to find if any process is tied to socket gets no results
$ ps aux | grep fpm
me 19222 0.0 0.0 12944 984 pts/0 S+ 13:56 0:00 grep --color=auto fpm
$ ps aux | grep php
me 19230 0.0 0.0 12944 976 pts/0 S+ 13:56 0:00 grep --color=auto php
I can't start the service
$ sudo service php7.0-fpm start
Job for php7.0-fpm.service failed because the control process exited with error code. See "systemctl status php7.0-fpm.service" and "journalctl -xe" for details.
journalctl details
$ journalctl -xe -n 20
Aug 12 14:26:48 foo.com sudo[27777]: me : TTY=pts/0 ; PWD=/etc/apache2/sites-available ; USER=root ; COMMAND=/usr/sbin/service php7.0-fpm start
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session opened for user root by me(uid=0)
Aug 12 14:26:48 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
-- Subject: Unit php7.0-fpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has begun starting up.
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: FPM initialization failed
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session closed for user root
Aug 12 14:26:48 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
-- Subject: Unit php7.0-fpm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has failed.
--
-- The result is failed.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
systemctl status results
$ systemctl status php7.0-fpm.service
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2017-08-12 14:29:46 EDT; 4s ago
Process: 28363 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)
Process: 28354 ExecStartPre=/usr/lib/php/php7.0-fpm-checkconf (code=exited, status=0/SUCCESS)
Main PID: 28363 (code=exited, status=78)
Aug 12 14:29:46 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: FPM initialization failed
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:29:46 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
debug commands
$ sudo /usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf
[12-Aug-2017 15:00:23] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
[12-Aug-2017 15:00:23] ERROR: FPM initialization failed
linux ubuntu apache-http-server php ubuntu-16.04
asked Aug 12 '17 at 18:06
veiligveilig
5261618
|
show 3 more comments
1
how can I figure out whats preventing me from starting php7.0-fpm. Nothing seems to show whats preventing it from starting.
$ sudo service php7.0-fpm status
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-08-11 16:52:04 EDT; 20h ago
Main PID: 4171 (code=exited, status=78)
Aug 11 16:52:04 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: FPM initialization failed
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 11 16:52:04 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
trying to find if any process is tied to socket gets no results
$ ps aux | grep fpm
me 19222 0.0 0.0 12944 984 pts/0 S+ 13:56 0:00 grep --color=auto fpm
$ ps aux | grep php
me 19230 0.0 0.0 12944 976 pts/0 S+ 13:56 0:00 grep --color=auto php
I can't start the service
$ sudo service php7.0-fpm start
Job for php7.0-fpm.service failed because the control process exited with error code. See "systemctl status php7.0-fpm.service" and "journalctl -xe" for details.
journalctl details
$ journalctl -xe -n 20
Aug 12 14:26:48 foo.com sudo[27777]: me : TTY=pts/0 ; PWD=/etc/apache2/sites-available ; USER=root ; COMMAND=/usr/sbin/service php7.0-fpm start
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session opened for user root by me(uid=0)
Aug 12 14:26:48 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
-- Subject: Unit php7.0-fpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has begun starting up.
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: FPM initialization failed
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session closed for user root
Aug 12 14:26:48 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
-- Subject: Unit php7.0-fpm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has failed.
--
-- The result is failed.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
systemctl status results
$ systemctl status php7.0-fpm.service
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2017-08-12 14:29:46 EDT; 4s ago
Process: 28363 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)
Process: 28354 ExecStartPre=/usr/lib/php/php7.0-fpm-checkconf (code=exited, status=0/SUCCESS)
Main PID: 28363 (code=exited, status=78)
Aug 12 14:29:46 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: FPM initialization failed
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:29:46 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
debug commands
$ sudo /usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf
[12-Aug-2017 15:00:23] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
[12-Aug-2017 15:00:23] ERROR: FPM initialization failed
linux ubuntu apache-http-server php ubuntu-16.04
asked Aug 12 '17 at 18:06
veiligveilig
5261618
So provide the details from php7.0-fpm.service and journalctl . But "An another FPM instance seems to already listen on " is the reason it's failing
– Ramhound
Aug 12 '17 at 18:25
@Ramhound I updated the question with the details, both just seem to say another process is already process is already listening. I can't figure out what is?
– veilig
Aug 12 '17 at 18:32
If you're completely sure it's not running, you can delete the/run/php/php7.0-fpm.sockfile and try again. Possibly another instance hang or was not shut down cleanly and did not remove the sock file.
– nKn
Aug 12 '17 at 18:33
@nKn, I don't think its running. I tried restarting the server and got the same result. its a staging server, so it doesn't matter if I have to kill something or reboot. downtime isn't critical
– veilig
Aug 12 '17 at 18:37
2
Did you try to remove the sock file before trying to restart?
– nKn
Aug 12 '17 at 18:38
|
show 3 more comments
1
1
1
1
how can I figure out whats preventing me from starting php7.0-fpm. Nothing seems to show whats preventing it from starting.
$ sudo service php7.0-fpm status
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-08-11 16:52:04 EDT; 20h ago
Main PID: 4171 (code=exited, status=78)
Aug 11 16:52:04 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: FPM initialization failed
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 11 16:52:04 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
trying to find if any process is tied to socket gets no results
$ ps aux | grep fpm
me 19222 0.0 0.0 12944 984 pts/0 S+ 13:56 0:00 grep --color=auto fpm
$ ps aux | grep php
me 19230 0.0 0.0 12944 976 pts/0 S+ 13:56 0:00 grep --color=auto php
I can't start the service
$ sudo service php7.0-fpm start
Job for php7.0-fpm.service failed because the control process exited with error code. See "systemctl status php7.0-fpm.service" and "journalctl -xe" for details.
journalctl details
$ journalctl -xe -n 20
Aug 12 14:26:48 foo.com sudo[27777]: me : TTY=pts/0 ; PWD=/etc/apache2/sites-available ; USER=root ; COMMAND=/usr/sbin/service php7.0-fpm start
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session opened for user root by me(uid=0)
Aug 12 14:26:48 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
-- Subject: Unit php7.0-fpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has begun starting up.
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: FPM initialization failed
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session closed for user root
Aug 12 14:26:48 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
-- Subject: Unit php7.0-fpm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has failed.
--
-- The result is failed.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
systemctl status results
$ systemctl status php7.0-fpm.service
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2017-08-12 14:29:46 EDT; 4s ago
Process: 28363 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)
Process: 28354 ExecStartPre=/usr/lib/php/php7.0-fpm-checkconf (code=exited, status=0/SUCCESS)
Main PID: 28363 (code=exited, status=78)
Aug 12 14:29:46 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: FPM initialization failed
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:29:46 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
debug commands
$ sudo /usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf
[12-Aug-2017 15:00:23] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
[12-Aug-2017 15:00:23] ERROR: FPM initialization failed
linux ubuntu apache-http-server php ubuntu-16.04
asked Aug 12 '17 at 18:06
veiligveilig
5261618
how can I figure out whats preventing me from starting php7.0-fpm. Nothing seems to show whats preventing it from starting.
$ sudo service php7.0-fpm status
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-08-11 16:52:04 EDT; 20h ago
Main PID: 4171 (code=exited, status=78)
Aug 11 16:52:04 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 11 16:52:04 foo.com php-fpm7.0[4171]: [11-Aug-2017 16:52:04] ERROR: FPM initialization failed
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 11 16:52:04 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 11 16:52:04 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
trying to find if any process is tied to socket gets no results
$ ps aux | grep fpm
me 19222 0.0 0.0 12944 984 pts/0 S+ 13:56 0:00 grep --color=auto fpm
$ ps aux | grep php
me 19230 0.0 0.0 12944 976 pts/0 S+ 13:56 0:00 grep --color=auto php
I can't start the service
$ sudo service php7.0-fpm start
Job for php7.0-fpm.service failed because the control process exited with error code. See "systemctl status php7.0-fpm.service" and "journalctl -xe" for details.
journalctl details
$ journalctl -xe -n 20
Aug 12 14:26:48 foo.com sudo[27777]: me : TTY=pts/0 ; PWD=/etc/apache2/sites-available ; USER=root ; COMMAND=/usr/sbin/service php7.0-fpm start
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session opened for user root by me(uid=0)
Aug 12 14:26:48 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
-- Subject: Unit php7.0-fpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has begun starting up.
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:26:48 foo.com php-fpm7.0[27818]: [12-Aug-2017 14:26:48] ERROR: FPM initialization failed
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:26:48 foo.com sudo[27777]: pam_unix(sudo:session): session closed for user root
Aug 12 14:26:48 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
-- Subject: Unit php7.0-fpm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit php7.0-fpm.service has failed.
--
-- The result is failed.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:26:48 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
systemctl status results
$ systemctl status php7.0-fpm.service
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2017-08-12 14:29:46 EDT; 4s ago
Process: 28363 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)
Process: 28354 ExecStartPre=/usr/lib/php/php7.0-fpm-checkconf (code=exited, status=0/SUCCESS)
Main PID: 28363 (code=exited, status=78)
Aug 12 14:29:46 foo.com systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
Aug 12 14:29:46 foo.com php-fpm7.0[28363]: [12-Aug-2017 14:29:46] ERROR: FPM initialization failed
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Aug 12 14:29:46 foo.com systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Unit entered failed state.
Aug 12 14:29:46 foo.com systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
debug commands
$ sudo /usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf
[12-Aug-2017 15:00:23] ERROR: An another FPM instance seems to already listen on /run/php/php7.0-fpm.sock
[12-Aug-2017 15:00:23] ERROR: FPM initialization failed
linux ubuntu apache-http-server php ubuntu-16.04
linux ubuntu apache-http-server php ubuntu-16.04
asked Aug 12 '17 at 18:06
veiligveilig
5261618
asked Aug 12 '17 at 18:06
veiligveilig
5261618
edited Aug 12 '17 at 19:01
veilig
asked Aug 12 '17 at 18:06
veiligveilig
5261618
asked Aug 12 '17 at 18:06
veiligveilig
5261618
asked Aug 12 '17 at 18:06
veiligveilig
5261618
5261618
So provide the details from php7.0-fpm.service and journalctl . But "An another FPM instance seems to already listen on " is the reason it's failing
– Ramhound
Aug 12 '17 at 18:25
@Ramhound I updated the question with the details, both just seem to say another process is already process is already listening. I can't figure out what is?
– veilig
Aug 12 '17 at 18:32
If you're completely sure it's not running, you can delete the/run/php/php7.0-fpm.sockfile and try again. Possibly another instance hang or was not shut down cleanly and did not remove the sock file.
– nKn
Aug 12 '17 at 18:33
@nKn, I don't think its running. I tried restarting the server and got the same result. its a staging server, so it doesn't matter if I have to kill something or reboot. downtime isn't critical
– veilig
Aug 12 '17 at 18:37
2
Did you try to remove the sock file before trying to restart?
– nKn
Aug 12 '17 at 18:38
|
show 3 more comments
So provide the details from php7.0-fpm.service and journalctl . But "An another FPM instance seems to already listen on " is the reason it's failing
– Ramhound
Aug 12 '17 at 18:25
@Ramhound I updated the question with the details, both just seem to say another process is already process is already listening. I can't figure out what is?
– veilig
Aug 12 '17 at 18:32
If you're completely sure it's not running, you can delete the/run/php/php7.0-fpm.sockfile and try again. Possibly another instance hang or was not shut down cleanly and did not remove the sock file.
– nKn
Aug 12 '17 at 18:33
@nKn, I don't think its running. I tried restarting the server and got the same result. its a staging server, so it doesn't matter if I have to kill something or reboot. downtime isn't critical
– veilig
Aug 12 '17 at 18:37
2
Did you try to remove the sock file before trying to restart?
– nKn
Aug 12 '17 at 18:38
So provide the details from php7.0-fpm.service and journalctl . But "An another FPM instance seems to already listen on " is the reason it's failing
– Ramhound
Aug 12 '17 at 18:25
So provide the details from php7.0-fpm.service and journalctl . But "An another FPM instance seems to already listen on " is the reason it's failing
– Ramhound
Aug 12 '17 at 18:25
@Ramhound I updated the question with the details, both just seem to say another process is already process is already listening. I can't figure out what is?
– veilig
Aug 12 '17 at 18:32
@Ramhound I updated the question with the details, both just seem to say another process is already process is already listening. I can't figure out what is?
– veilig
Aug 12 '17 at 18:32
If you're completely sure it's not running, you can delete the
/run/php/php7.0-fpm.sock file and try again. Possibly another instance hang or was not shut down cleanly and did not remove the sock file.– nKn
Aug 12 '17 at 18:33
If you're completely sure it's not running, you can delete the
/run/php/php7.0-fpm.sock file and try again. Possibly another instance hang or was not shut down cleanly and did not remove the sock file.– nKn
Aug 12 '17 at 18:33
@nKn, I don't think its running. I tried restarting the server and got the same result. its a staging server, so it doesn't matter if I have to kill something or reboot. downtime isn't critical
– veilig
Aug 12 '17 at 18:37
@nKn, I don't think its running. I tried restarting the server and got the same result. its a staging server, so it doesn't matter if I have to kill something or reboot. downtime isn't critical
– veilig
Aug 12 '17 at 18:37
2
2
Did you try to remove the sock file before trying to restart?
– nKn
Aug 12 '17 at 18:38
Did you try to remove the sock file before trying to restart?
– nKn
Aug 12 '17 at 18:38
|
show 3 more comments
1 Answer
1
active
oldest
votes
0
For me I just needed to delete the sock file, and then php-fpm would start again.
$ rm /run/php/php7.0-fpm.sock
or on my configuration it was:
$ rm /var/run/php/php7.0-fpm.sock
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1240301%2ffind-whats-preventing-php7-0-fpm-from-starting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
For me I just needed to delete the sock file, and then php-fpm would start again.
$ rm /run/php/php7.0-fpm.sock
or on my configuration it was:
$ rm /var/run/php/php7.0-fpm.sock
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
add a comment |
0
For me I just needed to delete the sock file, and then php-fpm would start again.
$ rm /run/php/php7.0-fpm.sock
or on my configuration it was:
$ rm /var/run/php/php7.0-fpm.sock
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
add a comment |
0
0
0
For me I just needed to delete the sock file, and then php-fpm would start again.
$ rm /run/php/php7.0-fpm.sock
or on my configuration it was:
$ rm /var/run/php/php7.0-fpm.sock
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
For me I just needed to delete the sock file, and then php-fpm would start again.
$ rm /run/php/php7.0-fpm.sock
or on my configuration it was:
$ rm /var/run/php/php7.0-fpm.sock
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
answered Feb 26 at 19:45
Justin FortierJustin Fortier
101
101
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1240301%2ffind-whats-preventing-php7-0-fpm-from-starting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
So provide the details from php7.0-fpm.service and journalctl . But "An another FPM instance seems to already listen on " is the reason it's failing
– Ramhound
Aug 12 '17 at 18:25
@Ramhound I updated the question with the details, both just seem to say another process is already process is already listening. I can't figure out what is?
– veilig
Aug 12 '17 at 18:32
If you're completely sure it's not running, you can delete the
/run/php/php7.0-fpm.sockfile and try again. Possibly another instance hang or was not shut down cleanly and did not remove the sock file.– nKn
Aug 12 '17 at 18:33
@nKn, I don't think its running. I tried restarting the server and got the same result. its a staging server, so it doesn't matter if I have to kill something or reboot. downtime isn't critical
– veilig
Aug 12 '17 at 18:37
2
Did you try to remove the sock file before trying to restart?
– nKn
Aug 12 '17 at 18:38