Bug 238850 - logrotate script points to wrong log location
logrotate script points to wrong log location
Status: CLOSED DUPLICATE of bug 233760
Product: Fedora
Classification: Fedora
Component: setroubleshoot (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Dennis
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-03 09:06 EDT by Derek Atkins
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-03 10:49:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Derek Atkins 2007-05-03 09:06:55 EDT
Description of problem:

The settroubleshoot logrotate configuration is broken.  I see this in my daily
emails:

/etc/cron.daily/logrotate:

error: error accessing /usr/local/var/log/setroubleshoot: No such file or direct
ory
error: setroubleshoot:1 glob failed for /usr/local/var/log/setroubleshoot/*.log
error: found error in /usr/local/var/log/setroubleshoot/*.log , skipping


Version-Release number of selected component (if applicable):

setroubleshoot-server-1.9.4-1.fc7

How reproducible:

Every night this happens.

Steps to Reproduce:
1. Install settroubleshoot-server
2. Wait for cron.daily to run at 4am
3. Look in root's email
  
Actual results:

See the email above.

Expected results:

It should rotate the proper log

Additional info:

/etc/logrotate.d/settroubleshoot contains a broken pointer:

[root@pgpdev ~]# more /etc/logrotate.d/setroubleshoot 
/usr/local/var/log/setroubleshoot/*.log {
...

This should probably be /var/log/settroubleshoot/*.log and not
/usr/local/var/log/...
Comment 1 Derek Atkins 2007-05-03 09:10:56 EDT
oops, this should be against devel, not test3.  Sorry.  This is against F7t4.
Comment 2 John Dennis 2007-05-03 10:49:21 EDT

*** This bug has been marked as a duplicate of 233760 ***

Note You need to log in before you can comment on or make changes to this bug.