Problems with /var/log/messages
I'm having the following problem: Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered. The only solution I found sofar is rebooting the machine, there has to be a simpler solution ! Best regards, Geert-Jan de Laat
Hi, On Wed, 2 Aug 2000 Geert-Jan.Laat-de@dsm-group.com wrote:
I'm having the following problem:
Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered. The only solution I found sofar is rebooting the machine, there has to be a simpler solution !
Yes, there was a bug in the log rotating scripts in SuSE 6.4, IIRC. Please update aaa_base.rpm from our ftp site. Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany You tell 'em Envelope, you're well posted.
I'm having the following problem:
Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered. The only solution I found sofar is rebooting the machine, there has to be a simpler solution !
Best regards,
Geert-Jan de Laat
There is. Either "kill -1 `pidof syslogd`" or upgrade the package aaa_base. The problem is that the syslogd only opens the logfiles once. If you remove one of the logfiles, syslogd will happily continue writing into it. This isn't wrong since it's the admin's fault if he removes files. Some versions of the logfile rotation parts of the daily cron scripts didn't take this behaviour into account, newer do it again. Thanks, Roman. -- - - | Roman Drahtmüller <draht@suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -
I'm having the following problem:
Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered.
I have a similar situation here, however just the mail log stops after logrotate runs.
The only solution I found sofar is rebooting the machine, there has to be a simpler solution !
You don't need to reboot, just restart syslogd: /sbin/init.d/syslog restart However this is not a solution. I've posted this question before but gotno answers. I'm running SuSE 6.3. rgrds, Bráulio Gergull
On Thu, 3 Aug 2000, Br�ulio Gergull wrote:
I'm having the following problem:
Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered.
I have a similar situation here, however just the mail log stops after logrotate runs.
The only solution I found sofar is rebooting the machine, there has to be a simpler solution !
You don't need to reboot, just restart syslogd:
/sbin/init.d/syslog restart
However this is not a solution. I've posted this question before but gotno answers.
I'm running SuSE 6.3.
See Suse's earlier reaction (Roman sent it I think?): update the aaa_base package, there is a bug in the older distros concerning log-rotating.
rgrds, Br�ulio Gergull
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Stefan ========================================== Stefan Suurmeijer Network Specialist University of Groningen tel: (+31) 50 363 3423 fax: (+31) 50 363 7272 E-mail (business): s.m.suurmeijer@let.rug.nl E-mail (private): stefan@symbolica.nl ========================================== Quis custodiet ipsos custodes? (Who'll watch the watchmen?) - Unknown
-----BEGIN PGP SIGNED MESSAGE----- The solution is quite simple actually: here's what i've found in /etc/logfiles (SuSE 6.4) # # This file tells cron.daily, which log files have to be watched # # File max size mode ownership service # (reload if changed) and then it goes something like: /var/log/httpd/access_log +4096k 644 root.root apache So you could add to /var/log/messages, or whatever you use, syslogd - --- Bogdan Zapca System Administrator SC EcoSoft SA Internet Service Provider 1-7 Deva st, Cluj-Napoca, Romania Tel: +40 64 199696 PGP: http://www.itotal.ro/lupe@admin2.ecosoft.ro.pgp http://www.ecosoft.ro On Thu, 3 Aug 2000, Br�ulio Gergull wrote:
I'm having the following problem:
Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered.
I have a similar situation here, however just the mail log stops after logrotate runs.
The only solution I found sofar is rebooting the machine, there has to be a simpler solution !
You don't need to reboot, just restart syslogd:
/sbin/init.d/syslog restart
However this is not a solution. I've posted this question before but gotno answers.
I'm running SuSE 6.3.
rgrds, Br�ulio Gergull
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
-----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQCVAwUBOYplo9Pv6ylvTc6pAQFDuQP/cjtSwSqZOJILupWbGK5A+bsalBWV+grP 0Bwdgf+VkB6xroQjM1sx5bF0d8RBVfoyFXGCCbHULxOZsDPF+EDuhq25S5pWNwvg I86yZ8zYBSLLhca32HzktWVsj6Ve4Q4YU79lNU/kiTzSjSav3We6jpo/zzrGFVHN q0eNqXrRDms= =bV0c -----END PGP SIGNATURE-----
participants (6)
-
Bogdan Zapca -
Br�ulio Gergull -
Geert-Jan.Laat-de＠dsm-group.com -
Lenz Grimmer -
Roman Drahtmueller -
Stefan Suurmeijer