Hello! what could be the reason that suse won´t write into my /var/log/messages anymore? The last activity was from the 11th of September. Anyone any idea? Thank you, Spiekey
Hello, On Fri, 14 Sep 2001, spiekey wrote:
Hello! what could be the reason that suse won�t write into my /var/log/messages anymore? The last activity was from the 11th of September. Anyone any idea?
Maybe you have no space on your /var or /var/log partition? Check it: df-H
Thank you, Spiekey
Best regards, Graham
At 14:16 14.09.2001 +0200, Graham Jones wrote:
Hello,
On Fri, 14 Sep 2001, spiekey wrote:
Hello! what could be the reason that suse won´t write into my /var/log/messages anymore? The last activity was from the 11th of September. Anyone any idea?
I have got the same problem: Whenever some program (or script?) compresses /var/log/messages a new messages file is created but always with 0 values. Nothing is written to it. I have to restart syslog and then it works fine. That also happens with /var/log/mail. I use SuSe version 6.3 Richard Hegewald
On 17 Sep 01, at 9:37, r.hegewald wrote:
Whenever some program (or script?) compresses /var/log/messages a new messages file is created but always with 0 values. Nothing is written to
You should not create a new log file but erase its content with cat /dev/null > /som/log/file mfg ar -- mailto:andreas@rittershofer.de http://www.rittershofer.de PGP-Public-Key http://www.rittershofer.de/ari.htm
At 12:59 17.09.2001 +0200, Andreas Rittershofer wrote:
On 17 Sep 01, at 9:37, r.hegewald wrote:
Whenever some program (or script?) compresses /var/log/messages a new messages file is created but always with 0 values. Nothing is written to
You should not create a new log file but erase its content with cat /dev/null > /som/log/file
I don't create new log files. It is Suse with some (which??) cronjobs switching log files whenever they grow to a certain size, I guess. I think the intention is OK, but still nothing is written to the new log file.
mfg ar
-- mailto:andreas@rittershofer.de http://www.rittershofer.de PGP-Public-Key http://www.rittershofer.de/ari.htm
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Am Montag, 17. September 2001 13:33 schrieb r.hegewald:
At 12:59 17.09.2001 +0200, Andreas Rittershofer wrote:
On 17 Sep 01, at 9:37, r.hegewald wrote:
Whenever some program (or script?) compresses /var/log/messages a new messages file is created but always with 0 values. Nothing is written to
You should not create a new log file but erase its content with cat /dev/null > /som/log/file
I don't create new log files. It is Suse with some (which??) cronjobs switching log files whenever they grow to a certain size, I guess. I think the intention is OK, but still nothing is written to the new log file. It's done with cron-daily (config file: /etc/cron.daily/aaa_base_rotate_logs) You can define sizes and id's of logfiles in /etc/logfiles
-- Best Regards, Manfred Schirmer CSE GmbH network administrator mailto:manfred.schirmer@cse.de
syslogd and e.g. sendmail will loose theire file handle cauz file moved to *.gz e.g. so they have to be restarted with SIGHUP killall -HUP sendmail killall -HUP syslogd a cron job (/etc/crontab) is crunching the log file regulary. Simply add in crontab e.g. # -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-cron && killall -HUP syslogd && killall -HUP sendmail to restart the daemons the call cron -r cron /etc/crontab cron -l shows the changes Michael -----Original Message----- From: r.hegewald [mailto:rh@medoil.de] Sent: Monday, September 17, 2001 9:37 AM To: Graham Jones; spiekey Cc: suse-security@suse.com Subject: Re: [suse-security] SuSE is not logging anymore.. At 14:16 14.09.2001 +0200, Graham Jones wrote:
Hello,
On Fri, 14 Sep 2001, spiekey wrote:
Hello! what could be the reason that suse won´t write into my /var/log/messages anymore? The last activity was from the 11th of September. Anyone any idea?
I have got the same problem: Whenever some program (or script?) compresses /var/log/messages a new messages file is created but always with 0 values. Nothing is written to it. I have to restart syslog and then it works fine. That also happens with /var/log/mail. I use SuSe version 6.3 Richard Hegewald -- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Appeldorn wrote: [..]
# -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-cron && killall -HUP syslogd && killall -HUP sendmail
or define the service to restart in the /etc/logfiles configuration file. [..]
Michael
Tom
participants (7)
-
Andreas Rittershofer -
Appeldorn -
Graham Jones -
Manfred Schirmer -
r.hegewald -
spiekey -
Tom Ribbens