Summary: | Logrotate include directive not working | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Karl O. Pinc <kop> |
Component: | logrotate | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7.3 | CC: | srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-07-15 12:19:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
Karl O. Pinc
2003-03-04 17:42:42 UTC
Does it start working if you include the syslog.local file manually in /etc/logrotate.d/syslog? I'll have to wait until the end of the month to find out if including the file locally works. I have more information. It doesn't look as if logrotate is running at all, yet it's in /etc/cron.daily as usual. There's no mention of logrotate in the cron logs, in /var/log/messages or in mail sent to root. (The configuration remains as above, except now the /var/log/maillog section has a "compress" on the line after "rotate 12". For the future, I've commented out the 'include' line and included the contents manually.) Could the problem be that syslog.local is being included twice? Once in /etc/logrotate.conf (as /etc/logrotate.d/syslog.local) and once in /etc/logrotate.d/syslog? If this is the problem why am I not getting an error message _somewhere_? try running logrotate manually if you want to know whether it gives any errors. Duh, should'a thought of that. [root@jcp root]# /etc/cron.daily/logrotate error: syslog.local:3 duplicate log entry for /var/log/jcp For other reasons I'm not getting root's mail. So, go ahead and close this bug. Unless you want to use this opportunity to fix the error message so it starts with the name of the program generating the error as is (sorta) standard. (IIRC as in the GNU coding standards. See 'info standards', node 'Errors'.) That'd make it easier to grep for and to tell where the message is coming from when it's buried in with other errors. I'm not making any claims, but it's possible I wouldn't have had to file this bug if my grepping had found the error message. Sorry for the false alarm. |