This bug was fixed in the package exim4 - 4.69-2ubuntu0.1
---
exim4 (4.69-2ubuntu0.1) hardy-proposed; urgency=low
* debian/exim4-base.exim4.init: Fix 'reload' action so that it
doesn't just stop the daemon (LP: #252686)
-- Paul Elliott omahns.h...@gmail.com Wed, 31 Mar 2010
Accepted exim4 into hardy-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: exim4 (Ubuntu Hardy)
** Branch linked: lp:ubuntu/hardy-proposed/exim4
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in ubuntu.
--
Ubuntu-server-bugs mailing
The 4.69-2ubuntu0.1 package from hardy-proposed fixes the issue on my
test machines. Can anyone else also provide verification?
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team,
@Paul: The patch looks incorrect to me. You use $PROGRAM while the
original script uses $DAEMON ?
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
@Thierry: Well spotted, strange that it still worked without the command
at the end of the parameters to start-stop-daemon. Anyway, please find
attached a corrected debdiff.
** Attachment added: exim4_4.69-2ubuntu0.1.debdiff
http://launchpadlibrarian.net/42785694/exim4_4.69-2ubuntu0.1.debdiff
Uploaded, pending acceptation in hardy-proposed.
** Changed in: exim4 (Ubuntu Hardy)
Status: In Progress = Confirmed
** Changed in: exim4 (Ubuntu Hardy)
Assignee: Paul Elliott (omahns-home) = (unassigned)
--
Reload action on init script kills daemon
** Changed in: exim4 (Ubuntu Hardy)
Assignee: (unassigned) = Paul Elliott (omahns-home)
** Changed in: exim4 (Ubuntu Hardy)
Status: Triaged = In Progress
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because
SRU: Minimal patch to fix 'reload' action in exim4 init script
I would like to nominate this for SRU in Hardy. Newer releases do not
have this issue as the underlying problem in init-functions is fixed:
https://bugs.launchpad.net/ubuntu/hardy/+source/exim4/+bug/252686/comments/2
Currently it's
Hi Paul,
(1) Please target hardy-proposed, not hardy
(2) Version number should be 4.69-2ubuntu0.1
Other than that, the patch looks good. Once this is fixed, consider the
patch ACKed by the SRU team.
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You
Hi John,
Thanks for your pointers, I've updated the target to hardy-proposed and
corrected the version number. Please find the updated debdiff attached.
Please can somebody provide sponsorship and upload to hardy-proposed for
further testing?
Thanks, Paul.
** Attachment added: Corrected
This bug was fixed in the package freeradius - 1.1.7-1ubuntu0.1
---
freeradius (1.1.7-1ubuntu0.1) hardy-proposed; urgency=low
* debian/freeradius.init: Fix 'reload' action so that it doesn't just
stop the daemon (LP: #252686)
-- Thierry Carrez thierry.car...@ubuntu.com Mon,
This is 8.04.3 LTS, looking at apt-cache policy I see I've pulled
nagios3 as backport from rogerw's ppa (mentioned in bug 240764).
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server
This bug affects nagios3 as well, the patch from comment #4 fixes the
issue.
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in ubuntu.
--
I confirm that the version in hardy-proposed fixes the reload issue.
** Tags removed: verification-needed
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Accepted freeradius into hardy-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: freeradius (Ubuntu
** Branch linked: lp:ubuntu/hardy-proposed/freeradius
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in ubuntu.
--
Ubuntu-server-bugs
(In the future, please just upload simple patches like that; it's easy
to reject them in the few cases where there aren't appropriate, and in
general having it in the queue already speeds things up)
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received
** Changed in: freeradius (Ubuntu Hardy)
Status: Confirmed = In Progress
** Changed in: freeradius (Ubuntu Hardy)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification
Uploaded.
** Changed in: freeradius (Ubuntu Hardy)
Status: In Progress = Fix Committed
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius
** Changed in: freeradius (Ubuntu Hardy)
Importance: Undecided = Medium
** Changed in: freeradius (Ubuntu Hardy)
Status: New = In Progress
** Changed in: freeradius (Ubuntu Hardy)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
Reload action on init script kills daemon
SRU Report for freeradius
Bug Impact: calling the reload init script action for freeradius
results in killing the daemon.
Affected supported releases: hardy. The bug in LSB has been introduced
between gutsy and hardy.
Development branch fix: LSB has been fixed in intrepid so that killproc
Subscribing ubuntu-sru for decision on hardy SRU for freeradius
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in ubuntu.
--
Tim: it's not a severe bug, but it's a risky move in an LTS, since you
can't really determine all what may be affected by this change. The
choice made was to selectively fix the affected packages, which is safer
but more work and less comprehensive. Adding a task for
freeradius/hardy.
** Also
Is the fix discussed in #228460 going to make it into hardy? Specifically this
change to /lib/lsb/init-functions:
-if [ -n $sig -o $sig = 15 -o $sig = TERM ]; then
+if [ -z $sig -o $sig = 15 -o $sig = TERM ]; then
I'm encountering this bug when /etc/init.d/freeradius reload ends
** Changed in: exim4 (Ubuntu Hardy)
Status: In Progress = Triaged
** Changed in: exim4 (Ubuntu Hardy)
Assignee: Thierry Carrez (ttx) = (unassigned)
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are
** Changed in: exim4 (Ubuntu Hardy)
Status: Triaged = In Progress
** Changed in: exim4 (Ubuntu Hardy)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are
Confirming on hardy. Fixed in intrepid by the LSB bugfix.
** Also affects: exim4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: exim4 (Ubuntu)
Status: New = Invalid
** Changed in: exim4 (Ubuntu Hardy)
Status: New = Confirmed
--
Reload action on init script
This bug also affects Exim4:
After a
/etc/init.d/exim4 reload
exim is sent a TERM signal, and disappears without warning.
Relevant bash trace:
+ reload_exim
+ case ${QUEUERUNNER} in
+ killproc -p /var/run/exim4/exim.pid /usr/sbin/exim4 -HUP
+ local pidfile sig status base i name_param
Copied to hardy-updates.
** Changed in: nagios2 (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Verification done (x86):
- nagios2 2.11-1ubuntu1.2 (hardy): reload does not work;
- nagios2 2.11-1ubuntu1.3 (hardy-proposed): reload works fine.
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of
lsb in Intrepid fixed this problem. Following Dustin's advice, it is
preferable to address this in nagios2 to reduce regression potential.
Intrepid is not affected: nagios2 has been superseded by nagios3.
** Changed in: lsb (Ubuntu)
Status: New = Fix Released
** Changed in: lsb (Ubuntu
Debdiff for bug 231004 + bug 252686 SRU
Bug Impact: calling the reload init script action for nagios2 results
in killing the daemon.
Affected supported releases: hardy. The bug in LSB has been introduced
between gutsy and hardy.
Development branch fix: nagios3 is shipped with Intrepid. LSB has
Uploaded to hardy-proposed as 2.11-1ubuntu1.3.
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios2 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: lsb (Debian)
Status: Unknown = Fix Released
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios2 in ubuntu.
--
** Also affects: lsb (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478871
Importance: Unknown
Status: Unknown
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Confirmed in hardy.
This is in fact a bug in /lib/lsb/init-functions where killproc does handle all
signals as SIGTERM :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478871
The fix is already merged in intrepid.
** Changed in: nagios2 (Ubuntu)
Importance: Undecided = Medium
This can be worked-around in nagios2, or fixed in lsb. The LSB change
might have too much regression potential for a SRU, though.
If we want to fix it in nagios2 we can use the attached initscript
patch.
** Attachment added: killproc.patch
http://launchpadlibrarian.net/16377987/killproc.patch
This would be the patch if we choose to fix it in lsb directly.
This will change behavior of all scripts calling killproc with a signal
number. This is theorically a good change, but it might generate
unexpected behavior changes.
I can make a debdiff for the chosen solution.
** Also affects:
nagios2 initscript patch if we prefer to fix it in nagios2
** Attachment added: initscript.patch
http://launchpadlibrarian.net/16378233/initscript.patch
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a
Whoops. nagios2 not nagios
** Changed in: nagios2 (Ubuntu)
Sourcepackagename: nagios = nagios2
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios2 in
41 matches
Mail list logo
