Diagmond Process Fails after every few hours

[Paul Bardeskar]

Dear Friends,

While analysing the syslog.log file on HP-UX server ,We have found that the diagmond process is dying aftre every 64 mintues from the time it starts.Here is the output of syslog.log

Apr 22 02:52:20 unix01 diagmond[8235]: started
Apr 22 03:56:35 unix01 diagmond[8235]: Exit due to initialization failure
Apr 22 05:02:21 unix01 diagmond[18042]: started
Apr 22 06:06:37 unix01 diagmond[18042]: Exit due to initialization failure
Apr 22 07:36:07 unix01 diagmond[6383]: started
Apr 22 08:40:24 unix01 diagmond[6383]: Exit due to initialization failure

I have tried running the daemon using two commands :
1. # /usr/sbin/stm/uut/bin/sys/diagmond
2. # /sbin/init.d/diagnostic start

These command does start the diagmond daemon, but it dies after few hours.

I have also checked the config files and they are also present.
13942 drwxrwxrwx 2 root other 1024 Dec 10 2001 .
13696 drwxrwxrwx 4 bin bin 96 Sep 14 2000 ..
13374 -rw------- 1 root sys 123 Dec 10 2001 HealthCheck.cfg
14650 -rw-rw-r-- 1 bin bin 4535 Feb 15 2002 diaglogd.cfg
15967 -rw-rw-r-- 1 bin bin 5432 Feb 15 2002 diagmond.cfg
15968 -rw-rw-r-- 1 bin bin 1695 Feb 15 2002 psmctd.cfg

Kindly help me out.

Regards,
Paul

[melvyn burnard]

firstly, you do not specify which OS or wich version of Diagnostics you have.
Secondly, has the current version ever worked? or has it always been doing this?

You might want to start by checking the version and patch levels, and possibly updating to the latest version for your OS version.

Failing that, if it has started happening recently, try to tie the failures up with any changes made, new software introduced etc.

[Helen French]

Check and make sure that you have all required patches installed on the system. This link also might be useful:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1082654663494+28353475&threadId=206224

[Paula J Frazer-Campbell]

Hi

It is taking 1hour 4 mins each time to fail- have a look at log to see what it was trying to do.


Paula

[Andrew Merritt_2]

I'd echo the previous suggestions to check you have an up-to-date version of the OnlineDiags.

Diagmond can exhibit this behaviour if some other process is using port 1508, or if it is killed somehow, and psmctd is still using port 1508 (the port used by the STM framework).

Do you run a port-scanner on this system? If so, you definitely need to check your OnlineDiags revision, since that is a known problem that was fixed; where a port scanner would kill diagmond, and leave psmctd on port 1508 so diagmond couldn't restart.

Andrew