topic Re: Cannot run cmviewcl - hangs then errors. in Operating System - HP-UX

Cannot run cmviewcl - hangs then errors.

tazhasan — Thu, 13 Dec 2018 15:04:12 GMT

Hi

I am getting the following when running cmviewcl:

cmviewcl: Cannot view the cluster configuration: No such file or directory.
Either this node is not configured in a cluster, user doesn't have
access to view the cluster configuration, or 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.

I rebooted the vpar last night, cmviewcl worked, then this morning when I came in, I see this message.

Hope you can help.

Regards

Tariq

Re: Cannot run cmviewcl - hangs then errors.

tazhasan — Thu, 13 Dec 2018 15:37:50 GMT

syslog show this:

Dec 13 15:33:10 NODE2 cmclconfd[28674]: cl_session_send: Socket is not connected

and the other node in the cluster shows this:

CLUSTER STATUS
giscl up

NODE STATUS STATE
NODE1 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkfis up running enabled NODE1
pkgis up running enabled NODE1
pkinsight up running enabled NODE1

NODE STATUS STATE
NODE2 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkfisuat up running enabled NODE2
pkgisuat up running enabled NODE2
pkcms2 up running enabled NODE2

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
pkisituat down halted disabled unowned
pknavig8 down halted disabled unowned

It's NODE2 that isn't showing the cmviewcl output (The above output is from NODE1)
Both of the NODES (vpars) were rebooted last night.

Re: Cannot run cmviewcl - hangs then errors.

NayakSandeep — Mon, 17 Dec 2018 07:13:16 GMT

See if any of these documents help.

https://internal.support.hpe.com/hpsc/doc/public/display?docId=emr_na-c01063288

https://internal.support.hpe.com/hpsc/doc/public/display?docId=emr_na-c02907520

Re: Cannot run cmviewcl - hangs then errors.

tazhasan — Mon, 17 Dec 2018 11:00:40 GMT

Hi NayakSandeep

Thanks for the links. host files and everything look OK. Looks like the cmclconfd -p daemon timestamp shows the same time as some security software called Nessus ran a scan against this node, and did something funny to lead to this. Anyway I am rebooting this host tomorrow evening, so let's see what happens.

Thanks for your help.