[Bug 663367] New: logrotate fails to backup /var/log/messages & /var/log/warn
https://bugzilla.novell.com/show_bug.cgi?id=663367 https://bugzilla.novell.com/show_bug.cgi?id=663367#c0 Summary: logrotate fails to backup /var/log/messages & /var/log/warn Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: estellnb@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 If there was a crash I always have to boot a rescue system because otherwise important files like /var/log/messages and /var/log warn are destroyed. Sometimes noentheless logrotate seems to make backups of messages; however they are always at least a year old and not of any value. You will usually need the last messages and warn from rsyslogd as Xorg provides an Xorg.0.log.old or the kernel a /var/log/boot.omsg. Consequently I would suggest a logrotate -f to be called early enough in the boot process and logrotate to be configured appropriately (rotate 2, no dateext, no compress) for this purpose. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=663367
https://bugzilla.novell.com/show_bug.cgi?id=663367#c
wei wang
https://bugzilla.novell.com/show_bug.cgi?id=663367
https://bugzilla.novell.com/show_bug.cgi?id=663367#c1
Petr Uzel
If there was a crash I always have to boot a rescue system because otherwise important files like /var/log/messages and /var/log warn are destroyed.
Could you please be more specific? What crashes? What destroys the logfiles? Do they just disappear? How does rescues system help? Sorry, I'm confused.
Sometimes noentheless logrotate seems to make backups of messages; however they are always at least a year old and not of any value.
Logrotate's job is to rotate the logs if they are too big/old. It has nothing to do with backups...
You will usually need the last messages and warn from rsyslogd as Xorg provides an Xorg.0.log.old or the kernel a /var/log/boot.omsg. Consequently I would suggest a logrotate -f to be called early enough in the boot process and logrotate to be configured appropriately (rotate 2, no dateext, no compress) for this purpose.
Why? Could you please elaborate more on this?
Reproducible: Always
How? :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=663367
https://bugzilla.novell.com/show_bug.cgi?id=663367#c2
Elmar Stellnberger
https://bugzilla.novell.com/show_bug.cgi?id=663367
https://bugzilla.novell.com/show_bug.cgi?id=663367#c3
Petr Uzel
4. The most important logfiles like /var/log/messages and /var/log/warn are constantly destroyed as soon as you reboot into the system that just has crashed.
I tried this and it does not happen on my system (VM, after hard reset, the logs didn't get destroyed). I think we should first figure out why this is happening on your system, before changing the way how we handle logging. Reassigning to syslogd maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=663367
https://bugzilla.novell.com/show_bug.cgi?id=663367#c4
Dr. Werner Fink
participants (1)
-
bugzilla_noreply@novell.com