I have a file- and printserver running Suse 6.3. It has suddenly stopped writing to the logfiles. The files /var/log/mail and /var/log/messages are empty and have the date when the logging stopped. With same date as the empty log-files is gz-files with the peviusly periods logfiles archived. The /var-partition has 400 M unused diskplace. Do yopu have any ideas about, what might have stopped the log's?> greetings... Morten Christensen -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Fri, 17 Mar 2000, Morten Christensen wrote:
I have a file- and printserver running Suse 6.3.
It has suddenly stopped writing to the logfiles.
The files /var/log/mail and /var/log/messages are empty and have the date when the logging stopped.
With same date as the empty log-files is gz-files with the peviusly periods logfiles archived.
The /var-partition has 400 M unused diskplace.
Okay, my first thought was space, but you already have that covered. The dumping of old data to a gz file is done by a cron script about midnight. The same script also deletes sufficiently-old gz files, I believe. But it sounds like it is NOT telling the syslog daemon to reinitialize. Try this command: killall -HUP syslogd Then look at /var/log/messages and see if it has a new line at the bottom (syslogd logs the fact that it was reinitialized). If that takes care of the problem, then investigate your cron configuration, along with /etc/logfiles, to see why that action doesn't happen automatically. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Fri, 17 Mar 2000, Morten Christensen wrote:
I have a file- and printserver running Suse 6.3.
It has suddenly stopped writing to the logfiles. The files /var/log/mail and /var/log/messages are empty and have
date when the logging stopped. With same date as the empty log-files is gz-files with the
----- Original Message -----
From: Warrl
periods logfiles archived.
The dumping of old data to a gz file is done by a cron script about midnight. The same script also deletes sufficiently-old gz files, I believe.
But it sounds like it is NOT telling the syslog daemon to reinitialize.
Try this command:
killall -HUP syslogd
I tried yopur advice, and it has startet logging again. Thanks for your help:-)
If that takes care of the problem, then investigate your cron configuration, along with /etc/logfiles, to see why that action doesn't happen automatically.
If it stops again, I will have to go deeper into this. mvh... Morten Christensen -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi, On Sun, 19 Mar 2000, Morten Christensen wrote:
The dumping of old data to a gz file is done by a cron script about midnight. The same script also deletes sufficiently-old gz files, I believe.
But it sounds like it is NOT telling the syslog daemon to reinitialize.
Try this command:
killall -HUP syslogd
I tried yopur advice, and it has startet logging again. Thanks for your help:-)
If that takes care of the problem, then investigate your cron configuration, along with /etc/logfiles, to see why that action doesn't happen automatically.
If it stops again, I will have to go deeper into this.
There was a buglet in the logfile rotation scripts. Update the package aaa_base, there is an update RPM on our ftp site. Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer 90443 Nuernberg, Germany -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Have you restarted the Syslogd ? I have seen this on one server before. Try to start it, then less -f messages and ping the box and see if the logs are generated......... Regards, Jon ______________________ Jon R. Doyle SuSE Inc. Systems Integration Engineer 580 Second Street, Suite 210 Oakland, Ca. 94607 + 510 - 628 - 3380 ______________________ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
grimmer＠suse.de -
m--c＠indbakke.dk -
marsaro＠suse.com -
warrl＠blarg.net