Bug 193159
| Summary: | logrotate kills privoxy | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | DaveG <daveg> |
| Component: | privoxy | Assignee: | Karsten Hopp <karsten> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | bzcl34nup | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-06 15:56:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: The privoxy deamon is killed after rotating log files. Version-Release number of selected component (if applicable): privoxy-3.0.3-9.2.1 (kernel-smp-2.6.16-1.2111_FC5, logrotate-3.7.3-2.2.1, vixie-cron-4.1-54.FC5, crontabs-1.10-7.1, bash-3.1-6.2, util-linux-2.13-0.20.1) How reproducible: Allow privoxy log file or cookie jar to reach maximum size (default 1M) and allow logrotate to run from cron. Steps to Reproduce: 0. Reduce the limit file size in /etc/logrotate.d/privoxy and modify /etc/crontab times for debugging. 1. Run privoxy. 2. Generate some log information from privoxy. 3. Run the daily cron jobs. 4. Check the state of the privoxy daemon. Actual results: privoxy daemon no longer running. /var/log/privoxy/logfile: May 25 07:35:57 Privoxy(-1209034080) Info: Privoxy version 3.0.3 May 25 07:35:57 Privoxy(-1209034080) Info: Program name: /usr/sbin/privoxy May 25 07:35:57 Privoxy(-1240507488) Info: exiting by signal 6 .. bye This is the problem -----------------------------------------^ That siganl was supposed to be SIGHUP (1)! Expected results: The logrotate script should signal privoxy to reload. Should be seeing SIGHUP (1) and not SIGABRT (6). Additional info: It appears that the various shells - cron, logrotate, logrotate-postrotate etc. end up using /bin/kill rather than the bash built-in at some point. Changing the privoxy init script to use generic syntax appears to fix the problem on FC5 i686-smp at least. # diff -u /etc/init.d/privoxy.orig /etc/init.d/privoxy --- /etc/init.d/privoxy.orig 2006-05-25 11:47:31.000000000 +0100 +++ /etc/init.d/privoxy 2006-05-25 12:05:29.000000000 +0100 @@ -234,7 +234,7 @@ ;; reload) if [ -f $PRIVOXY_PID ] ; then - kill -HUP `cat $PRIVOXY_PID` + kill -s HUP `cat $PRIVOXY_PID` RETVAL=$? fi ;;