Operating System - HP-UX
1758810 Members
3251 Online
108875 Solutions
New Discussion юеВ

Re: error when run cmcheckconf and cmapplyconf (MC is 11.20)

 
SOLVED
Go to solution
Ji Lei
Frequent Advisor

error when run cmcheckconf and cmapplyconf (MC is 11.20)

Although there are error messages when run cmcheckconf -v -C cmcluster.ascii
and
cmapplyconf -v -C cmcluster.ascii
the cluster seems formed functionally.


==============The error are below=============
ERROR: /etc/cmcluster/cmclfiles2check owner could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/cmcluster/cmclfiles2check checksum could not be checked on nodes dr-his1 dr-his2:
/etc/cmcluster/cmclfiles2check is the same across nodes dr-his1 dr-his2
ERROR: /etc/hosts permissions could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/hosts owner could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/hosts checksum could not be checked on nodes dr-his1 dr-his2:
/etc/hosts is the same across nodes dr-his1 dr-his2
ERROR: /etc/nsswitch.conf permissions could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/nsswitch.conf owner could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/nsswitch.conf checksum could not be checked on nodes dr-his1 dr-his2:
/etc/nsswitch.conf is the same across nodes dr-his1 dr-his2
ERROR: /etc/services permissions could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/services owner could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/services checksum could not be checked on nodes dr-his1 dr-his2:
/etc/services is the same across nodes dr-his1 dr-his2
ERROR: /etc/cmcluster/cmignoretypes.conf permissions could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/cmcluster/cmignoretypes.conf owner could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/cmcluster/cmignoretypes.conf checksum could not be checked on nodes dr-his1 dr-his2:
/etc/cmcluster/cmignoretypes.conf is the same across nodes dr-his1 dr-his2
ERROR: /etc/cmcluster/cmknowncmds permissions could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/cmcluster/cmknowncmds owner could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/cmcluster/cmknowncmds checksum could not be checked on nodes dr-his1 dr-his2:
/etc/cmcluster/cmknowncmds is the same across nodes dr-his1 dr-his2
ERROR: /etc/cmcluster/cmnotdisk.conf permissions could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/cmcluster/cmnotdisk.conf owner could not be checked on nodes dr-his1 dr-his2:
ERROR: /etc/cmcluster/cmnotdisk.conf checksum could not be checked on nodes dr-his1 dr-his2:
/etc/cmcluster/cmnotdisk.conf is the same across nodes dr-his1 dr-his2
Command 'cat /etc/cmcluster/cmclfiles2check | /usr/sbin/cmcompare -W -v -n dr-his1 -n dr-his2' exited with status 2
WARNING: Unable to check consistency of all files listed in /etc/cmcluster/cmclfiles2check
Maximum configured packages parameter is 300.
Configuring 0 package(s).
Creating the cluster configuration for cluster dr-his_cluster
Adding node dr-his1 to cluster dr-his_cluster
Adding node dr-his2 to cluster dr-his_cluster
Marking/unmarking volume groups for use in the cluster
Completed the cluster creation.
3 REPLIES 3
Mel Burslan
Honored Contributor

Re: error when run cmcheckconf and cmapplyconf (MC is 11.20)

Are you sure that these two nodes are communicating with one another using ssh or rsh ? i.e.

if you run from host 1

ssh (or rsh depending on your choice) node2 date

do you get a valid response ?
________________________________
UNIX because I majored in cryptology...
Emil Velez
Honored Contributor
Solution

Re: error when run cmcheckconf and cmapplyconf (MC is 11.20)

welcome to 11.20..

The file called cmclfiles2check contains the names of files that serviceguard needs to check across all of the nodes in the cluster.

You could comment out the lines in that file.

These are not errors.. if a file does not exist on a node or the file is diffeerent you will get these errors and warnings..

Most importantly is the last line.. Completed cluster Creation..

Now start your cluster.

Ji Lei
Frequent Advisor

Re: error when run cmcheckconf and cmapplyconf (MC is 11.20)

Emil Velez is right.

The fact is, the cluster and package can be started and is running very well.