log error at /var/opt/cmomd.log

[yulianto piyut]

hi all,

I have error at /var/opt/cmom/cmomd.log, below:
instance of LogEntryInstTable {
timestamp = "Jul 29 15:24:45";
source = "14839";
category = "ERROR";
path = "omd";
message = "Failed to getpeername on client socket (5): Invalid argument";
};
instance of LogEntryInstTable {
timestamp = "Jul 29 15:24:45";
source = "14839";
category = "FATAL";
path = "omd";
message = "Failed to start inetd network: exiting";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 15:05:43";
source = "20943";
category = "ERROR";
path = "omd";
message = "Failed to getpeername on client socket (5): Invalid argument";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 15:05:43";
source = "20943";
category = "FATAL";
path = "omd";
message = "Failed to start inetd network: exiting";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 15:49:17";
source = "10924";
category = "ERROR";
path = "omd";
message = "Failed to getpeername on client socket (5): Invalid argument";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 15:49:17";
source = "10924";
category = "FATAL";
path = "omd";
message = "Failed to start inetd network: exiting";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 16:06:35";
source = "18867";
category = "ERROR";
path = "omd";
message = "Failed to getpeername on client socket (5): Invalid argument";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 16:06:35";
source = "18867";
category = "FATAL";
path = "omd";
message = "Failed to start inetd network: exiting";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 16:06:50";
source = "19002";
category = "ERROR";
path = "omd";
message = "Failed to getpeername on client socket (5): Invalid argument";
};
instance of LogEntryInstTable {
timestamp = "Aug 28 16:06:50";
source = "19002";
category = "FATAL";
path = "omd";
message = "Failed to start inetd network: exiting";
};

someone know how to fix it ?

[Fabio Ettore]

Hi,

do you have problems with inetd? Is it running?

ps -ef |grep -i inetd

Best regards,
Fabio

[yulianto piyut]

hi,

thx for the answer. my inetd daemon is running.
# ps -ef|grep -i inetd
root 1126 1 0 May 29 ? 81:47 /usr/sbin/inetd
root 16683 16651 0 10:41:37 pts/1 0:00 grep -i inetd
# grep hacl /etc/services
hacl-qs 1238/tcp # HA cluster Quorum Server
hacl-qs 1238/udp # HA cluster Quorum Server
hacl-monitor 3542/tcp # HA cluster monitor
hacl-monitor 3542/udp # HA cluster monitor
hacl-hb 5300/tcp # High Availability (HA) Cluster heartbeat
hacl-hb 5300/udp # High Availability (HA) Cluster heartbeat
hacl-gs 5301/tcp # HA Cluster General Services
hacl-gs 5301/udp # HA Cluster General Services
hacl-cfg 5302/tcp # HA Cluster TCP configuration
hacl-cfg 5302/udp # HA Cluster UDP configuration
hacl-probe 5303/tcp # HA Cluster TCP probe
hacl-probe 5303/udp # HA Cluster UDP probe
hacl-local 5304/tcp # HA Cluster Commands
hacl-local 5304/udp # HA Cluster Commands
hacl-test 5305/tcp # HA Cluster Test
hacl-dlm 5408/tcp # HA Cluster distributed lock manager
# grep hacl /etc/inetd.conf
hacl-probe stream tcp nowait root /opt/cmom/lbin/cmomd /opt/cmom/lbin/cmomd -f /var/opt/cmom/cmomd.log -r /var/opt/cmom
hacl-cfg dgram udp wait root /usr/lbin/cmclconfd cmclconfd -p
hacl-cfg stream tcp nowait root /usr/lbin/cmclconfd cmclconfd -c
# netstat -an |grep 5302
tcp 0 0 127.0.0.1.5302 127.0.0.1.49275 ESTABLISHED
tcp 0 0 127.0.0.1.5302 127.0.0.1.49259 ESTABLISHED
tcp 0 0 127.0.0.1.49275 127.0.0.1.5302 ESTABLISHED
tcp 0 0 *.5302 *.* LISTEN
tcp 0 0 127.0.0.1.49259 127.0.0.1.5302 ESTABLISHED
udp 0 0 *.5302 *.*
# netstat -an |grep 5303
tcp 0 0 *.5303 *.* LISTEN
#

[Fabio Ettore]

Hi,

if inetd is working well then I don't understand why that log is indicating inetd starting issues. Maybe it's a false message and you can ignore it, especially you don't see any kind of problem on your SG environment.
For example check also syslog.log for related issues about SG. In case you would like to invest more on those messages I suggest opening a call by HP to get an explaination cmomd.log is getting those messages.

Best regards,
Fabio

[Ivan Doroshuk]

hello,

Did you find some solution on this one ? I have the same problem.

[Ivan Doroshuk]

Ok, i've found my solution. There was a port scanner scnning my system at that time. cmomd didn't like to be scanned. there's a Serviceguard patch from HP ( since dec 14 ) for that problem.