Strange error/behavior.

[Gene Kornacki_3]

Running cmviewcl -v on node 1 of a two node cluster gives me:

cmviewcl : Cannot view the cluster configuration. Either this node is not configured in a cluster, or else there is some obstacle to viewing the configuration. Check the syslog file for more information. For a list of possible causes, see the ServiceGuard manual for cmviewcl.

On the other node I run the same command and get:

CLUSTER STATUS
cluster1 up

NODE STATUS STATE
manure up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/0/0/0 lan0
PRIMARY up 0/4/0/0 lan1
STANDBY up 0/7/0/0 lan2

NODE STATUS STATE
smelly up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/0/0/0 lan0
STANDBY up 0/7/0/0 lan2
PRIMARY up 0/4/0/0 lan1

Node 1 will not serv outside requests until it is reboot, and then all is fine.

Has anyone seen this behavior? There were no error messages in syslog when this happened. I could not telnet into the box, but had an open window on a PC. The DB was accesible from both nodes.

I know this is vague, but I have nothing more to go on.

[Sridhar Bhaskarla · Accepted solution]

Hi Gene,

You said you were not able to telnet to the box. Since you had an open window, did you try to troubleshoot?. For ex., restarting inetd etc?.

I think it was not a serviceguard issue. ServiceGuard was one of the components that got affected by the connection issue.

-Sri

[Gene Kornacki_3]

I restarted inetd with inetd -k and then inetd.

I think you're right, that it really wasn't serviceguard.

I just learned there was an amature on the machine not long before the problem occured. Questioning him provides no detail. I guess I can write this one off as an ID 10 T error. As long as it doens't happen again....

Thanks for your quick response.