topic Re: syslog guidelines in Operating System - HP-UX

syslog guidelines

Ralph Grothe — Tue, 31 Oct 2000 10:10:46 GMT

Hi forumers,

coming from Linux I was a bit surprised that each time the HP-UX system reboots there seems to be started a new syslog.log while the pending version is moved to OLDsyslog.log.
I guess you can configure this behaviour somewhere (syslog.conf?) but haven't found out where yet.

From Linux'es /var/log/messages I'm not used to such odd (undeliberate) logrotation.
Probably because a desktop is expected to be rebooted more frequently.

I just would like to hear from others whether they have devised a rotation system for this most important logfile.

How long do you keep your syslogs (because with the preset behaviour after 2 reboots important information may be lost)?

Do you store excerpts in a database (flatfile, dbm file, RDBMS)?

Any guidelines are most welcome.

Regards
Ralph

Re: syslog guidelines

Andreas Voss — Tue, 31 Oct 2000 10:18:08 GMT

Hi,

a agree with you. Rebooting twice and your older syslog.log is gone.
So i changed the rc script that does the renaming:
/sbin/init.d/syslogd
I changed:
mv /var/adm/syslog/syslog.log /var/adm/syslog/OLDsyslog.log
TO
mv /var/adm/syslog/syslog.log /var/adm/syslog/syslog.log_`date '+%d.%m.%y_%H:%M'`
This will rename old syslog files with time stamp on it.

Regards

Re: syslog guidelines

Andreas Voss — Tue, 31 Oct 2000 10:18:56 GMT

Re: syslog guidelines

Victor BERRIDGE — Tue, 31 Oct 2000 11:50:45 GMT

I keep 3 copies:Old, previous, and current, and depending on the gap between 2 reboots, I permute the files myself, and reinitialize a new mail.log and syslog.log, based on size essentialy (some machines are up >200 days I have one up 468 days...)

Regards

Victor

Re: syslog guidelines

Ralph Grothe — Tue, 31 Oct 2000 13:07:52 GMT

to Andreas,

first I thought I could reply in German since apart from you no one else seemed inclined to drop a line.
But now I see Victor in line, and I think in Geneve they speek french (do they Victor?).

Thanks for pointing me to the init script of the syslog daemon.
Now I will also alter the mv statement to something more bootproof.

BTW, what is the question mark in your 2nd posting telling us?

To Victor,
unfortunately I haven't had uptimes over 200 days yet, as there was ample need to reboot the machines due to panics, kernel patches, firmware upgrades etc.
Sometimes I got the impression that my Linux box at home (standard of the shelf Intel PC) exhibited a more stable behaviour.
But maybe there is an HP Rep. reading this who would like to prove me wrong. ;-)

Re: syslog guidelines

Paula J Frazer-Campbell — Tue, 31 Oct 2000 13:26:19 GMT

Gutten tag
Bon Jour
Good Afternoon

Hi to all and thanks to Andreas for his syslogd modification which I now have in place on 2 K class and one N Class server I have also tested in on my N Class as at the moment it is my "Play" machine.

Re: syslog guidelines

Andreas Voss — Tue, 31 Oct 2000 13:32:16 GMT

Hi,
i put the question mark into reply because today i get several posting errors. To prevent replies of same content i simply typed a ? and hit the submit button.
Just ignore that reply.

Regards

Re: syslog guidelines

Andreas Voss — Tue, 31 Oct 2000 13:38:51 GMT

Hi,

just one addition of modifying /sbin/init.d/syslogd.
You have to take care when installing patches or other OS software that affects this file.
It will be overwritten (This script is not configurable!)
So before any swinstall make a save copy of the syslogd file.

Regards

Re: syslog guidelines

Victor BERRIDGE — Tue, 31 Oct 2000 13:54:11 GMT

Yes Ralph,
Here we speak french, and I have found this forum as only alternative for not forgetting English, as long as the others forgive me for all my mistakes...
The difficult part is when your trying to reply and have a phone with someone speaking to you in french, you finish up writing something incoherent...

I feel less lonely since Ive started to be active (a bit) in this forum and I thank you all for that!

Best regards
Victor

Re: syslog guidelines

Ralph Grothe — Tue, 31 Oct 2000 14:28:05 GMT

To Andreas' last reply,

thank you for stressing the volatility of init scripts with regard to OS upgrades.

Since I've contributed some of my own startup scripts and modified others I knew of this peril and keep backup copies.
(e.g. static routes, for which I didn't like HP's way to have 4 array entries for each route in /etc/rc.config.d/netconf, SAP start/stop)

Re: syslog guidelines

Tom Danzig — Tue, 31 Oct 2000 14:41:57 GMT

Personal opinion: Since I review the logs regularly, I see no need to keep the old ones. Just my $ 0.02

Re: syslog guidelines

Kevin Urschatz — Tue, 31 Oct 2000 16:20:27 GMT

I also see no point in keeping more than the current and the OLD syslog.

If you really need a syslog from a few reboots ago then a restore of the file is an option.

Just my 2 cents.

Re: syslog guidelines

Benjamin Heitmann — Wed, 08 Aug 2001 09:44:57 GMT

Thank god, I found that post.

I was in the exactly same situation. Well and so that maybe more people find this post I am goint to put some more keywords here:

syslog old files rotation backup

;)

Re: syslog guidelines

Uffe Gavnholt_1 — Wed, 08 Aug 2001 10:42:57 GMT

Hi Ralph,

The solution for this is quite simple, I would suggest you made your own startup script to do whatever you want with the old syslog.

on hpux, simply put your script in /sbin/init.d, and put a link, with a name starting with an S### The "S" means it's a startup script, the number is the order of the startup.

Your script will be run, whenever the system changes to the runlevel you put your script in - make sure it's executed after the syslog script.

If you want to keep old syslogs, you can save them in a directory, renaming then to add a time stamp after the name.

Or you can append all of them to one big file. Doesn't have to be complicated.

Good luck with it

Uffe

Re: syslog guidelines

Mark Vollmers — Wed, 08 Aug 2001 13:46:00 GMT

Ralph-

I have a cron job set up to copy the logs weekly, just so I have a record of them. I agree with what you're saying about the double reboot wiping out old ones, but normally, if that happens, I'm the one who's issuing the command. If I reboot and there are problems, I always try to go in as single user and copy the log so I can see what it's doing before the second reboot wipes it clean.

Mark