syslogd not logging logs after particular time

[satheeshnp]

Hi all,

I have restarted syslog daemon with default -D option. I am getting logs for only few hours and it gets stop logging msg.

But syslogd is running. I have every thing
filesystem size is also is correct.

I dont know why it is stop logging after a period of time.

Kindly help.

[Shibin_2]

Stops logging what ?

[Jose Mosquera]

Hi,

Please check your syslod current patch level:
#what /usr/sbin/syslogd

Then also check if have a new syslogd cumulative patch that correct this symptom or just update it because reboot is not required.

You can restart syslog daemon by:
#kill -HUP `cat /var/run/syslog.pid`

The event log file /var/adm/syslog should also be reflecting the same symptoms of syslog.log file.

Rgds.

[Laurent Menase]

did you define a new console?

like with "hpterm -C"

check
echo "cons_mux_de/X\ncons_out_dev\X" | adb -o /stand/vmunix /dev/kmem

when it works and when it doesn't

[satheeshnp]

hi jose

I have checked the patch level.

$Revision: 92453-07 linker linker crt0.o B.11.16.01 030415 $
logmsg.c $Date: 2007/04/25 11:13:56 $Revision: r11.23/3 PATCH_11.23 (PHCO_36055)
logmsg.c $Date: 2007/04/25 11:13:56 $Revision: r11.23/3 PATCH_11.23 (PHCO_36055)
syslogd.c $Date: 2007/04/25 11:14:01 $Revision: r11.23/6 PATCH_11.23 (PHCO_36055)
$Revision: @(#) syslogd R11.23_BL2007_0529_1 PATCH_11.23 PHCO_36055
Copyright (c) 1983 Regents of the University of California.


process is running. Servers with same patch level are reporting logs correctly.

Only this is the issue.
help

[Jose Mosquera · Accepted solution]

Hi,

I've noticed that you are in 11.23, I'm not sure in you versión but 11i includes this note at online manual (man syslog):
"syslogd logs messages into a set of files. Once the size of a log file reaches 2 GB, syslogd stops logging to that file. The maximum size of syslogd log files can be configured by setting the variable LOG_SIZE in /etc/default/syslogd. The values of LOG_SIZE can be any positive integer greater than 2, representing the maximum size of the file in GB. When LOG_SIZE=NOLIMIT, syslogd uses the limit imposed by the file system on file size."

Also please check debuggin option at online manual: man syslogd

Rgds.

[Alzhy]

vi /etc/syslog.conf
:set list


check if you have spaces instead of tabs as separators for facilty and destination.

If you have 'em, replace with TABs and restart syslogd.


/sbin/init.d/syslogd stop
/sbin/init.d/syslogd start

[Chandrahasa s]

HI,
Try to monitor /var/adm/syslog/mail.log file
if size of this file crosses limit also causes this issue.
Also try to start syslogd daemon using option -D -d, this will throw any error if any configuration issue.

if still you face issue.

cp -p /etc/syslog.conf /tmp/syslog.conf
cp -p /usr/newconf/etc/syslog.conf /etc
then stop and start syslogd daemon

Chandra

[satheeshnp]

Hi

Jose thanks a lot.

Issue was Syslog size was limited to 2GB. Now I gave Nolimit.

working fine.

Thanks once again.

Special thanks to chandra.

[Viktor Balogh]

Hi,

> Issue was Syslog size was limited to 2GB. Now I gave Nolimit.

as large logfiles are unmanageable, you could consider log rotation, here is the latest logrotate tool from the porting center:

http://hpux.connect.org.uk/hppd/hpux/Sysadmin/logrotate-3.7.9/


or here is a script which does the same for you:

http://h30499.www3.hp.com/t5/General/logroate-equivalent/m-p/3471441#M105277