Operating System - HP-UX
1823920 Members
3180 Online
109667 Solutions
New Discussion юеВ

Re: syslog not able to trap error message

 
sjana
Occasional Advisor

syslog not able to trap error message

Hello HP Gurus,

Kindly find the error attached. Mail me the solution.

My advance thanks to all.

tar
siva
8 REPLIES 8
Michael_356
Frequent Advisor

Re: syslog not able to trap error message

Hi there,

/var/mail/root is the mailfile for root.
Could you please open it with elm or mail and post the message, which describe your faulty process.

Regards

Michael
Florian Heigl (new acc)
Honored Contributor

Re: syslog not able to trap error message

hi there,

I think syslog just relayed a programs error message to You.
please check if there is still a process around with id 9992.

On the other thing, You can check Your mail with either 'mail' or by 'tail /var/mail/root' (it's a file not a directory :)

hth,
florian
yesterday I stood at the edge. Today I'm one step ahead.
Stephen Keane
Honored Contributor

Re: syslog not able to trap error message

For those that can't read a bitmap file.


Jan 12 17:00:00 mbpscw01 syslog: Pid 9992. Program <> Failed to open Error Log file <>. Err=
Jan 12 17:00:00 mbpscw01 syslog: Pid 9992. Failed to open Info Log file<>. Err=

you have mail in /var/mail/root
#
# cd /var/mail/root
sh: /var/mail/root: the specified path name is not a directory.
#


If you want to read the mail, log in as root and type in ...

# mail

sjana
Occasional Advisor

Re: syslog not able to trap error message

hello all

no mails are there as in error itself it is showing /var/mail/root not a directory and even when i log in by root and give mail it is showing no mail.

tar
siva
Michael_356
Frequent Advisor

Re: syslog not able to trap error message

Hi there,

First check the mailfile: ll /var/mail/root
If its size is not 0 (zero) then
mail -f /var/mail/root

Regards

Michael
Michael_356
Frequent Advisor

Re: syslog not able to trap error message

Hmmm...

17:00:00?
It seems to be a job started by cron, isn't it?
What jobs are in roots crontab starting at 17:00?

Michael
Stephen Keane
Honored Contributor

Re: syslog not able to trap error message

Also check /var isn't full. Do you have access to the console, are ther any other errors displayed there?
Henk Geurts
Esteemed Contributor

Re: syslog not able to trap error message

hi
my idea is that a cron script can't find a file it needs as imput and therefor generates a error message to mail root.

check your crontab
# crontab -l
for 00 * * * * scriptname

good luck
Henk