syslogd terminated

[Michael Steele_2]

What are the error messages from dmesg?
What are the error messages on the console?

[Mel Burslan]

Just for the kick, instead of starting syslogd, using the init script, what happens if you start it directly from the command line as in

/usr/sbin/syslogd

without putting it in background (i.e. daemon mode) is it staying up or dying down immediately ?

Open another terminal window to the same system and run:

while true; do
ps -ef | grep syslogd
done

continuously. This will impact the performance more than likely. So, if this is a production system, you might want to do it after hours. Also capture the terminal session as the output will most probably flow too fast for your eyes to catch anything meaningful.

This may give you a bit more insight and won't hurt anything just by trying.

Just a thought

[Laurent Menase]

try to start /usr/sbin/syslogd -d

[atul2701]

all above things i have already tried and no luck..

when it dies its creating the core file..
# what core
core:
$ PATCH_11.31/PHCO_39177 May 21 2009 06:51:02 $
$ PATCH_11.31/PHCO_40292 Jul 6 2010 09:44:47 $
92453-07 linker dld HP Itanium(R) B.12.55
92453-07 linker uld HP Itanium(R) B.12.55
#

[atul2701]

Thanks all for your valuable time and support.. Finaly i got the solution.

Under syslog dir mail.log file size was 2Gb. i have trimmed the same and after that start the syslogd daemon and running fine..

Atul

[Ismail Azad]

Hey atgupta,

Well I guess the moral of this scenario turns out to be trimming certain stuff once in a while on the /var filesystem... Be it the syslog, or let's say the wtmps or btmps file. That's why on a server that you consider important it's momentous to check if the /var is reaching let's say 98% with very less free space left.

Regards
Ismail Azad

[atul2701]

Its not bcoz /var fs is running out of space. /var utilization was around 58% only.

there is a bug in 11.31 Syslogd is checking or calling mail.log. That’s the reason need to trim down some files with near or greater than 2GB or modifying the LOG_SIZE=NOLIMIT in /etc/defaults/syslogd file.