system log service stops logging on the third day after reboot.

[muungwana]

I have noticed this behavior for a while now and i though i should report it. When i restart a computer and keep it running for a couple of days, the log file will be cleared on what i think on a third day when log files are backed up and logging stops and i have to restart syslog service for logging to restart.

Will try to keep the computer running for the next three days  to see if it happens only after a computer (re)start or after every three days if a computer isnt restarted.

[muungwana]

The system reports uptime of 12 days and the log file was empty this morning, the system logger stopped logging. There is a problem to be looked at here.

The interval maybe intermittent but the system log service stops logging after couple of days of continuous run.

[YouCanToo]

The system reports uptime of 12 days and the log file was empty this morning, the system logger stopped logging. There is a problem to be looked at here.

The interval maybe intermittent but the system log service stops logging after couple of days of continuous run.

For whats it worth, it is working just fine on all of my machines.

[Old-Polack]

The system reports uptime of 12 days and the log file was empty this morning, the system logger stopped logging. There is a problem to be looked at here.

The interval maybe intermittent but the system log service stops logging after couple of days of continuous run.

For whats it worth, it is working just fine on all of my machines.

Same here. My logs just rotated with the last seven days now archived.

[Rudge]

I just checked and seems all is working here as well.  



oops, forgot to show that the syslog rotated on Apr 3 04:02

[muungwana]

I always get the following lines on the log file everyday when they logs are rotated, are you guys getting them too?

Mar 22 04:01:01 mtz anacron[9171]: Normal exit (0 jobs run)
Mar 22 04:02:01 mtz CROND[9185]: (root) CMD (nice -n 19 run-parts --report /etc/cron.daily)
Mar 22 04:02:02 mtz logrotate: ALERT exited abnormally with [1]
Mar 22 04:02:02 mtz logrotate: error: error accessing /var/log/samba: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: samba:1 glob failed for /var/log/samba/*.log
Mar 22 04:02:02 mtz logrotate: error: found error in /var/log/samba/*.log , skipping
Mar 22 04:02:02 mtz logrotate: error: error accessing /var/log/mail: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: syslog:2 glob failed for /var/log/mail/*.log
Mar 22 04:02:02 mtz logrotate: error: found error in /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 , skipping
Mar 22 04:02:02 mtz logrotate: error: stat of /var/log/mpd/mpd.log failed: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: stat of /var/log/mpd/mpd.error failed: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: stat of /var/log/security.log failed: No such file or directory
Mar 22 05:01:01 mtz CROND[9587]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)
Mar 22 06:01:01 mtz CROND[9800]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)



my system backup only 4 logs named "syslog.1.gz", "syslog.2.gz","syslog.3.gz","syslog.4.gz". Do you also only have 4 or more? I was working under an assumption that rotation program gets confused when it reached the last one.

[muungwana]

The system reports uptime of 12 days and the log file was empty this morning, the system logger stopped logging. There is a problem to be looked at here.

The interval maybe intermittent but the system log service stops logging after couple of days of continuous run.

For whats it worth, it is working just fine on all of my machines.

Same here. My logs just rotated with the last seven days now archived.

How many days is your system running? a response on a system running for more than 7 days will be best

[Old-Polack]

The system reports uptime of 12 days and the log file was empty this morning, the system logger stopped logging. There is a problem to be looked at here.

The interval maybe intermittent but the system log service stops logging after couple of days of continuous run.

For whats it worth, it is working just fine on all of my machines.

Same here. My logs just rotated with the last seven days now archived.

How many days is your system running? a response on a system running for more than 7 days will be best

Normally I'm up 24/7 for weeks or months, but I just rebooted three installations for the 2.6.38.2-pclos1.pae.bfs kernel upgrades. Previous 2 uptimes were 17 days and 21 days on this one.

[YouCanToo]

my shortest running machine is at 22 days and my longest one is at 221 days

[Rudge]

I always get the following lines on the log file everyday when they logs are rotated, are you guys getting them too?

Mar 22 04:01:01 mtz anacron[9171]: Normal exit (0 jobs run)
Mar 22 04:02:01 mtz CROND[9185]: (root) CMD (nice -n 19 run-parts --report /etc/cron.daily)
Mar 22 04:02:02 mtz logrotate: ALERT exited abnormally with [1]
Mar 22 04:02:02 mtz logrotate: error: error accessing /var/log/samba: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: samba:1 glob failed for /var/log/samba/*.log
Mar 22 04:02:02 mtz logrotate: error: found error in /var/log/samba/*.log , skipping
Mar 22 04:02:02 mtz logrotate: error: error accessing /var/log/mail: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: syslog:2 glob failed for /var/log/mail/*.log
Mar 22 04:02:02 mtz logrotate: error: found error in /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 , skipping
Mar 22 04:02:02 mtz logrotate: error: stat of /var/log/mpd/mpd.log failed: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: stat of /var/log/mpd/mpd.error failed: No such file or directory
Mar 22 04:02:02 mtz logrotate: error: stat of /var/log/security.log failed: No such file or directory
Mar 22 05:01:01 mtz CROND[9587]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)
Mar 22 06:01:01 mtz CROND[9800]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)



my system backup only 4 logs named "syslog.1.gz", "syslog.2.gz","syslog.3.gz","syslog.4.gz". Do you also only have 4 or more? I was working under an assumption that rotation program gets confused when it reached the last one.

Is this at the end of the last syslog or at the beginning of the new one? I haven't looked at the end of my current .gz but I don't see anything like this at the start of my current syslog.

Also, the latest syslog.x.gz is always called "syslog.1.gz". (all the others get renamed and move up on the list). I also only have 4 but they "roll off / get deleted?" and continue.  

[muungwana]

Those log entries show up everyday and i see them everytime the log daemon work as expected and continue to log after rotation. What entries do you have at 4 in the morning?

I am going to file this one as a problem that shows up only on my system since nobody else seem to be having it. A cron job to restart system logger should solve it for me too