Jump to content

logrotate error on 2009.1


RVDowning
 Share

Recommended Posts

I'm getting the following email:

 

/etc/cron.daily/logrotate:

error: sa-update:3 unknown option 'notifyempty' -- ignoring line

 

By the way, I don't have a file named "sa-update"

 

I understand the problem is a typo, namely 'notifyempty' should be 'notifempty' but I don't know where to make the change. I don't really want to have to scan every file in the system looking for the 'nofityempty' string.

Link to comment
Share on other sites

Nothing in /etc/logrotate.conf and I did a scan of all the files under /etc/logrotate.d/ and everything is spelled correctly as "notifempty". I can find no occurrance of "notifyempty" but I keep getting this email every day. Puzzled.....

Link to comment
Share on other sites

Still puzzled:

 

# logrotate -v /etc/logrotate.conf

reading config file /etc/logrotate.conf

including /etc/logrotate.d

reading config file .directory

error: .directory:1 lines must begin with a keyword or a filename (possibly in double quotes)

error: .directory:2 unknown option 'AdditionalInfo' -- ignoring line

error: .directory:2 unexpected text

error: .directory:3 unknown option 'Timestamp' -- ignoring line

error: .directory:3 unexpected text

error: .directory:4 unknown option 'ViewMode' -- ignoring line

error: .directory:4 unexpected text

reading config file kdm

reading config info for /var/log/kdm.log

reading config file msec

reading config info for /var/log/security.log

reading config file ppp

reading config info for /var/log/ppp/connect-errors

reading config file preload

reading config info for /var/log/preload.log

reading config file rpm

reading config info for /var/log/rpmpkgs

reading config file sudo

reading config info for /var/log/sudo.log

reading config file syslog

reading config info for /var/log/auth.log /var/log/messages /var/log/syslog /var/log/user.log /var/log/explanations /var/log/boot.log /var/log/mail/*.log /var/log/cron/*.log /var/log/kernel/*.log /var/log/daemons/*.log

reading config file xdm

reading config info for /var/log/xdm-error.log

reading config info for /var/log/wtmp

reading config info for /var/log/btmp

 

Handling 10 logs

 

rotating pattern: /var/log/kdm.log weekly (4 rotations)

empty log files are not rotated, old logs are removed

considering log /var/log/kdm.log

log does not need rotating

 

rotating pattern: /var/log/security.log monthly (4 rotations)

empty log files are rotated, old logs are removed

considering log /var/log/security.log

log does not need rotating

 

rotating pattern: /var/log/ppp/connect-errors after 1 days (5 rotations)

empty log files are not rotated, old logs are removed

considering log /var/log/ppp/connect-errors

log does not need rotating

not running postrotate script, since no logs were rotated

 

rotating pattern: /var/log/preload.log 65536 bytes (4 rotations)

empty log files are not rotated, old logs are removed

considering log /var/log/preload.log

log does not need rotating

not running postrotate script, since no logs were rotated

 

rotating pattern: /var/log/rpmpkgs weekly (4 rotations)

empty log files are not rotated, old logs are removed

considering log /var/log/rpmpkgs

log does not need rotating

not running postrotate script, since no logs were rotated

 

rotating pattern: /var/log/sudo.log monthly (4 rotations)

empty log files are rotated, old logs are removed

considering log /var/log/sudo.log

log does not need rotating

not running postrotate script, since no logs were rotated

 

rotating pattern: /var/log/auth.log /var/log/messages /var/log/syslog /var/log/user.log /var/log/explanations /var/log/boot.log /var/log/mail/*.log /var/log/cron/*.log /var/log/kernel/*.log /var/log/daemons/*.log weekly (4 rotations)

empty log files are rotated, old logs are removed

considering log /var/log/auth.log

log does not need rotating

considering log /var/log/messages

log does not need rotating

considering log /var/log/syslog

log does not need rotating

considering log /var/log/user.log

log does not need rotating

considering log /var/log/explanations

log does not need rotating

considering log /var/log/boot.log

log does not need rotating

considering log /var/log/mail/errors.log

log does not need rotating

considering log /var/log/mail/info.log

log does not need rotating

considering log /var/log/mail/warnings.log

log does not need rotating

considering log /var/log/cron/errors.log

log does not need rotating

considering log /var/log/cron/info.log

log does not need rotating

considering log /var/log/cron/warnings.log

log does not need rotating

considering log /var/log/kernel/errors.log

log does not need rotating

considering log /var/log/kernel/info.log

log does not need rotating

considering log /var/log/kernel/warnings.log

log does not need rotating

considering log /var/log/daemons/errors.log

log does not need rotating

considering log /var/log/daemons/info.log

log does not need rotating

considering log /var/log/daemons/warnings.log

log does not need rotating

not running postrotate script, since no logs were rotated

 

rotating pattern: /var/log/xdm-error.log weekly (4 rotations)

empty log files are not rotated, old logs are removed

considering log /var/log/xdm-error.log

log /var/log/xdm-error.log does not exist -- skipping

not running postrotate script, since no logs were rotated

 

rotating pattern: /var/log/wtmp monthly (1 rotations)

empty log files are rotated, old logs are removed

considering log /var/log/wtmp

log does not need rotating

not running postrotate script, since no logs were rotated

 

rotating pattern: /var/log/btmp monthly (1 rotations)

empty log files are rotated, old logs are removed

considering log /var/log/btmp

log does not need rotating

not running postrotate script, since no logs were rotated

Link to comment
Share on other sites

When I read your log carefully I note the following:

# logrotate -v /etc/logrotate.conf
reading config file /etc/logrotate.conf
including /etc/logrotate.d
reading config file .directory
error: .directory:1 lines must begin with a keyword or a filename (possibly in double quotes)
...

To me this means that you have a file /etc/logrotate.d/.directory which probably doesn't belong there (not containing directives for logrotate). Can you check the contents of /etc/logrotate with ls -la?

Link to comment
Share on other sites

# ls -la (in /etc/lograte.d)

total 43

drwxr-xr-x 2 root root 272 2009-07-03 16:46 ./

drwxr-xr-x 104 root root 6800 2009-07-03 09:54 ../

-rw------- 1 root root 96 2009-07-03 16:46 .directory

-rw-r--r-- 1 root root 60 2009-06-15 11:33 kdm

-rw-r--r-- 1 root root 448 2009-04-23 09:05 msec

-rw-r--r-- 1 root root 136 2008-12-17 12:34 ppp

-rw-r--r-- 1 root root 180 2009-02-06 06:23 preload

-rw-r--r-- 1 root root 61 2009-06-18 04:55 rpm

-rw-r--r-- 1 root root 61 2009-05-31 13:02 sudo

-rw-r--r-- 1 root root 438 2009-02-05 12:34 syslog

-rw-r--r-- 1 root root 71 2009-03-07 00:34 xdm

 

 

There was a hidden file in /etc/logrotate.d called ".directory" with the following content:

 

[Dolphin]

AdditionalInfo=3

Timestamp=2009,7,3,16,46,26

ViewMode=1

 

[settings]

ShowDotFiles=true

 

Ha, wouldn't you know that Dolphin has its dirty fingers in there somehow.

Link to comment
Share on other sites

I guess Greg asked about spamassasin as 'sa-update' is a spamassasin binary.

 

A quick google search for the error you get returns loads of hits, here is a good explanation:

https://bugzilla.redhat.com/show_bug.cgi?id=223753

 

The weird thing is that you don't seem to have a /etc/logrotate.d/sa-update file (at least not in the ls -la output you posted), are you sure the email is not from another machine?

Edited by tux99
Link to comment
Share on other sites

Hmmmm. Ya know...... My web site is actually on a linux machine...... It is a web hosting service, but I actually have a virtual machine. I'll have to check that. It had never crossed my mind. May not get to it tonight. I have a road race in the morning (worlds largest 10k) and it about time for me to start preparing stuff and then get to bed. I'll post back after I get a chance to check it.

 

Thanks for the insight.

 

Rich

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...