I have documented the workaround in the bug description. This bug
presumably does not affect releases = Vivid since it is related to
upstart and Ubuntu runs systemd since Vivid. So marking Fix Released and
creating a Trusty task in case someone can come up with a good fix for
Trusty that can be
Any updates on this? This is causing us huge troubles because every
configuration update via puppet triggers a service reload which kills
the php5-fpm parent process and detaches it's clients, leading to stale
code running in production after deployments.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
** Changed in: php5 (Ubuntu)
Status: Triaged = New
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) = Pratiksha (deekshammhs10)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
What I just noticed (on an Ubuntu 14.04.4 LTS, using ondrej's PPA) is
that /etc/init.d/php5-fpm still exists.
When I issue service php5-fpm reload - my FPM engines disappear, even
though I have /etc/init/php5-fpm.conf and /etc/init/php5-fpm.override
set to enable the reload parameter.
Looks like
It should be fixed upstream, simply adopting Ondrejs PPA *and* removing
`/etc/init.d/php5-fpm` breaks BC and doesn't make much sense.
@deekshammhs10: Any ETA?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
@Ondrej, I can confirm that with your latest PPA the reload is fine.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To manage
Shall I try fetching upstream and applying your patch or that's the one
the ppa is built with?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
There's nothing wrong with master process NOT CHANGING the PID. I told
you to look at the logs and not at the PID, so please do so before
jumping to wrong conclusions, thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in
Hi Ondrej, sorry if I seemed pushy, not my intention.
The logs I pasted above refer to the exact test procedure you requested,
here are some fresh ones;
root@sandbox01:/home/pmoust# php -v
PHP 5.5.14-2+deb.sury.org~trusty+1 (cli) (built: Jul 2 2014 12:14:44)
Copyright (c) 1997-2014 The PHP
Did you modify the standard logging?
# grep -E 'log' /etc/php5/fpm/php-fpm.conf /etc/php5/fpm/pool.d/* | grep
-v :;
?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
Not really,
pmoust@sandbox01:~⟫ grep -E 'log' /etc/php5/fpm/php-fpm.conf
/etc/php5/fpm/pool.d/* | grep -v :;
/etc/php5/fpm/php-fpm.conf:error_log = /var/log/php5-fpm.log
/etc/php5/fpm/pool.d/main.conf:access.log = /var/log/fpm/main.access.log
/etc/php5/fpm/pool.d/main.conf:slowlog =
I have no idea why there's nothing in the logs, but I can say for sure
that the PID of the master process *DOES NOT* change between reloads
(the execve() call exchange the running code, but not the PID of the
process).
The easy thing how to check if the pool.d/* processes do reload is to
change
I am aware what execve() call does.
So there must be an inconsistency between 5.3.x php fpm and the one under your
ppa?
Centos 6.4;
[root@cygnus ~]# php -v
PHP 5.3.3 (cli) (built: Dec 11 2013 03:29:57)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend
PHP 5.3 was first version to have php-fpm integrated, so I guess there
might have been a room for improvement.
I haven't packaged FPM in Debian squeeze, so I cannot confirm the PHP
5.3 behaviour.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
On 12.04
pmoust@webserver01:~$ ps aux | grep fpm | grep master
root 5002 13.0 0.0 609140 10236 ?Ss 07:21 0:00 php-fpm:
master process (/etc/php5/fpm/php-fpm.conf)
pmoust@webserver01:~$ sudo kill -USR2 5002
pmoust@webserver01:~$ ps aux | grep fpm | grep master
root 10771
@ondrej , I've used your ppa that provides PHP 5.5.14-2+deb.sury.org~trusty+1
(cli) (built: Jul 2 2014 12:14:44) , doing service php5-fpm reload or manually
sending kill -1 to master fpm process does not seem to alter the master PID.
Shouldn't the master process respawn itself as well?
I was
What does the log says?
# apt-cache policy php5-fpm
php5-fpm:
Installed: 5.6.0~rc2+dfsg-1
Candidate: 5.6.0~rc2+dfsg-1
Version table:
*** 5.6.0~rc2+dfsg-1 0
700 http://ftp.cz.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
5.6.0~rc1+dfsg-1 0
Rather strange,
root@sandbox01:/home/pmoust# sudo service php5-fpm restart
php5-fpm stop/waiting
php5-fpm start/running, process 2193
root@sandbox01:/home/pmoust# tailf /var/log/php5-fpm.log
[1] 2703
root@sandbox01:/home/pmoust# [07-Jul-2014 07:28:47] NOTICE: configuration file
Did not paste the important part, here it goes
root@sandbox01:/home/pmoust# kill -HUP 2193; echo $?
0
root@sandbox01:/home/pmoust# kill -USR2 2193; echo $?
0
root@sandbox01:/home/pmoust# ps aux | grep fpm | grep master
root 2193 0.3 0.1 389924 23812 ?Ss 08:13 0:00 php-fpm:
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To manage notifications about this bug go to:
I think it's not exactly clear here, why this cannot be fixed right away
in Ubuntu 14.04 LTS.
The main problem is that 'upstart' is not following Postel's principle
(be benevolent in what you receive, and strict in what you send) and
barfs and breaks whole release upgrade process if it encounters
@Robie: Try pulling fbdc116d6023141060d515949f38fcaa61ef2ed7 from
master-5.5 branch.
I have implemented:
Hmm, or we can just patch php5-fpm to reload on SIGHUP
That would just make everyone happy without fixing upstart.
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: bugs.php.net/ #67553
http://bugs.php.net/bug.php?id=67553
** Also affects: php via
http://bugs.php.net/bug.php?id=67553
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
JFTR the ppa:ondrej/php5-oldstable, ppa:ondrej/php5 and ppa:php5-5.6 has
been updated (or will be updated shortly) with patched PHP 5.4, 5.5 and
5.6 that accept SIGHUP as reload signal and thus it doesn't break with
upstart.
--
You received this bug notification because you are a member of
This should be treated ASAP, atm Ubuntu 14.04 LTS php5-fpm package cannot
gracefully reload workers with new configuration.
Restart is not an option in a production environment.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5
Some possible workarounds (off the top of my head):
1) Restart instead.
2) Send a USR2 signal to the correct PID manually (get it with status
php5-fpm).
3) Create /etc/init/php5-fpm.override file with the single line reload signal
USR2 in it.
Please report which of these workarounds works for
+1
We have this issue too. Seems the reload signal USR2 being in the
official php5-fpm.conf is still commented out. Not sure why, as it
should be able to be pinned just to recent versions of Upstart /
releases.
I have used Robie's suggestion #3 above in an .override file, and that
seems to work
We ran into this bug while upgrading our servers from 12.04 LTS to 14.04
LTS. It is serious for us. When we deploy our app, we need to do
`service php5-fpm reload` so that the php opcode cache is flushed,
otherwise old files will still be served. Doing a `php5-fpm restart`
isn't a option as it
I agreed totally with Renan... PHP5-FPM reload is broken meaning that
restart is mandatory ATM (which is not a way to go for shared hosting
environment where configuration should be reloaded without having to do
a full restart)...
--
You received this bug notification because you are a member of
The package 5.5.9+dfsg-1ubuntu3 have the correct upstart script with
reload signal USR2, which works great on Ubuntu Trusty since it uses
upstart = 1.10.0
For fixing the https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1272788 bug
a new package was released, called 5.5.9+dfsg-1ubuntu4, which
I'm on precise64 with ondrej's PPA for php 5.5 and experiencing the same
issues. Using service results in the bug report's error. Using init.d
gives me:
stop: Rejected send message, 1 matched rules; type=method_call,
sender=:1.15 (uid=1001 pid=21912 comm=stop php5-fpm )
Did an upgrade on my Ubuntu 14.04 server on the 7th of March. php5-fpm
died immediately. Adding lines of code such as reload signal
SIGUSR2 or taking them away makes no difference. Running php5-fpm -v
produces this print out Segmentation fault Result of php5 -v
is
PHP
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To manage notifications about this bug go to:
Hi,
We are using Precise LTS too here.
The init script from the php-fpm package in Ondřej's php5-oldstable PPA (PHP
5.4) works on Precise.
That's using start-stop-daemon instead of upstart.
So a fix for Precise, and possibly other older distributions, is to use that
init script also on PHP
Hi,
Giacomo Orlandi: sorry that I didn't make it clear, by
/etc/init.d/php5-fpm I meant what you just mentioned (The init script
from the php-fpm package in Ondřej's php5-oldstable PPA), not the
symlink provided by the php5-fpm package.
--
You received this bug notification because you are a
Hi,
Great to see that the bug was fixed. However, what could be the solution
for old version ( 1.10.0) of upstart? For instance, in ubuntu precise,
the version of upstart is 1.5-0ubuntu7.2, is there any suggested
workaround for such case? Thanks!
--
You received this bug notification because
I have found that I can still use /etc/init.d/php5-fpm to do reload,
however, this script doesn't work well with php5-fpm processes that are
started by service php5-fpm start, for instance,
/etc/init.d/php5-fpm stop sometimes can't stop all the processes, I
have not looked into the cause of
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To manage notifications about this bug go to:
@Ondřej
I just tested upstart 1.5-0ubuntu7.2 from Precise. This fails with
signal USR2 with the error Unknown stanza, and refuses to process
the job. So this will only work with upstart = 1.10.0. It looks like
this first became available in Debian unstable only a few days ago.
Does this block
Oh, I've just seen your fix uploaded in 5.5.6+dfsg-1, sorry.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To manage notifications about this
As far as I remember I have discussed this on the debian-devel and the
reload signal was added to upstart just recently.
Robie, could you please confirm that the older versions of upstart won't
cry too much if they encounter unknown directive?
--
You received this bug notification because you
Note that the move to upstart for php5-fpm happened with Ubuntu 13.10
Its not relevant for older releases.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Confirmed: php5-fpm(8) documents USR2 as the reload signal, and the
upstart script defaults to HUP.
Workaround (untested): add the line reload signal USR2 to
/etc/init/php5-fpm.conf.
This also exists in Debian
44 matches
Mail list logo
