[Bug 984806] Re: squid-deb-proxy's logrotate file calls "squid" instead of "squid3" on Precise
Bryce Harrington
984806 at bugs.launchpad.net
Thu Apr 19 21:11:58 UTC 2012
** Description changed:
- The logrotate configuration is trying to call "squid" instead of
- "squid3" to notify the proxy of the log rotation. Here is the error mail
- from cron :
+ [Problem]
+ <1-2 sentence summary of the issue>
+
+ [Impact]
+ <fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release>
+
+ [Development Fix]
+ <fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. >
+
+ [Stable Fix]
+ <fill me in by pointing out a minimal patch applicable to the stable version of the package.>
+
+ [Text Case]
+ <fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem.>
+ 1.
+ 2.
+ 3.
+ Broken Behavior:
+ Fixed Behavior:
+
+ [Regression Potential]
+ <fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected.>
+
+ [Original Report]
+
+
+ The logrotate configuration is trying to call "squid" instead of "squid3" to notify the proxy of the log rotation. Here is the error mail from cron :
/etc/cron.daily/logrotate:
logrotate_script: 2: logrotate_script: /usr/sbin/squid: not found
error: error running shared postrotate script for '/var/log/squid-deb-proxy/*.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1
Here is the faulty logrotate config extract from /etc/logrotate.d/squid-
deb-proxy :
- postrotate
- test ! -e /var/run/squid-deb-proxy.pid || /usr/sbin/squid -f /etc/squid-deb-proxy/squid-deb-proxy.conf -k rotate
- endscript
-
+ postrotate
+ test ! -e /var/run/squid-deb-proxy.pid || /usr/sbin/squid -f /etc/squid-deb-proxy/squid-deb-proxy.conf -k rotate
+ endscript
# lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
# apt-cache policy squid-deb-proxy
squid-deb-proxy:
- Installed: 0.6.2
- Candidate: 0.6.2
- Version table:
- *** 0.6.2 0
- 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 0.6.2
+ Candidate: 0.6.2
+ Version table:
+ *** 0.6.2 0
+ 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
+ 100 /var/lib/dpkg/status
# apt-cache policy squid3
squid3:
- Installed: 3.1.19-1ubuntu2
- Candidate: 3.1.19-1ubuntu2
- Version table:
- *** 3.1.19-1ubuntu2 0
- 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 3.1.19-1ubuntu2
+ Candidate: 3.1.19-1ubuntu2
+ Version table:
+ *** 3.1.19-1ubuntu2 0
+ 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
+ 100 /var/lib/dpkg/status
** Summary changed:
- squid-deb-proxy's logrotate file calls "squid" instead of "squid3" on Precise
+ squid-deb-proxy's logrotate file calls "squid" instead of "squid3" on Precise [SRU]
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/984806
Title:
squid-deb-proxy's logrotate file calls "squid" instead of "squid3" on
Precise [SRU]
Status in “squid-deb-proxy” package in Ubuntu:
Fix Committed
Bug description:
[Problem]
<1-2 sentence summary of the issue>
[Impact]
<fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release>
[Development Fix]
<fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. >
[Stable Fix]
<fill me in by pointing out a minimal patch applicable to the stable version of the package.>
[Text Case]
<fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem.>
1.
2.
3.
Broken Behavior:
Fixed Behavior:
[Regression Potential]
<fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected.>
[Original Report]
The logrotate configuration is trying to call "squid" instead of "squid3" to notify the proxy of the log rotation. Here is the error mail from cron :
/etc/cron.daily/logrotate:
logrotate_script: 2: logrotate_script: /usr/sbin/squid: not found
error: error running shared postrotate script for '/var/log/squid-deb-proxy/*.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1
Here is the faulty logrotate config extract from /etc/logrotate.d
/squid-deb-proxy :
postrotate
test ! -e /var/run/squid-deb-proxy.pid || /usr/sbin/squid -f /etc/squid-deb-proxy/squid-deb-proxy.conf -k rotate
endscript
# lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
# apt-cache policy squid-deb-proxy
squid-deb-proxy:
Installed: 0.6.2
Candidate: 0.6.2
Version table:
*** 0.6.2 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy squid3
squid3:
Installed: 3.1.19-1ubuntu2
Candidate: 3.1.19-1ubuntu2
Version table:
*** 3.1.19-1ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/984806/+subscriptions
More information about the Ubuntu-sponsors
mailing list