1834189 Members
2727 Online
110064 Solutions
New Discussion

cmquerycl error

 
SOLVED
Go to solution
yulianto piyut
Valued Contributor

cmquerycl error

guys,

I want to 3rd node to running cluster. Existing cluster consists of 2 node. when i run command cmqueycl, there are some error message.
bash-2.04# cmquerycl -v -C clconfig.ascii -n eaipapp1 -n eaipapp2 -n eaipapp6

Begin checking the nodes...
Warning: Unable to determine local domain name for eaipapp1
Looking for other clusters ... Done
Gathering configuration information .......... Done
Warning: The disk at /dev/dsk/c1t2d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t1d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t2d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t3d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t4d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t5d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t6d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t7d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t8d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t9d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t10d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t11d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t12d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t13d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t14d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t15d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t1d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t2d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t3d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t4d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t5d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t6d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t7d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t8d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t9d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t10d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t11d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t12d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t13d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t14d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t15d0 on node eaipapp1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c1t2d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t1d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t2d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t3d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t4d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t5d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t6d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t7d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t8d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t9d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t10d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t11d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t12d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t13d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t14d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c8t15d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t1d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t2d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t3d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t4d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t5d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t6d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t7d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t8d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t9d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t10d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t11d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t12d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t13d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t14d0 on node eaipapp2 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c10t15d0 on node eaipapp2 does not have an ID, or a disk label.
Error: Permission denied accessing node eaipapp6.
Error: Unable to determine device configuration: failed to receive device query reply from node eaipapp6
Warning: Disks which do not have IDs cannot be included in the topology description.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.
Error: Permission denied accessing node eaipapp6.
Error: Unable to determine lvm configuration: failed to receive lvm query reply from node eaipapp6
Error: Permission denied accessing node eaipapp6.
Error: Permission denied accessing node eaipapp6.
Error: Unable to determine network configuration: failed to setup for probing the network on node eaipapp6: Permission denied
Failed to probe network
Warning: Network interface lan0 on node eaipapp1 couldn't talk to itself.
Warning: Network interface lan3 on node eaipapp1 couldn't talk to itself.
Warning: Network interface lan1 on node eaipapp1 couldn't talk to itself.
Warning: Network interface lan2 on node eaipapp1 couldn't talk to itself.
Warning: Network interface lan0 on node eaipapp2 couldn't talk to itself.
Warning: Network interface lan3 on node eaipapp2 couldn't talk to itself.
Warning: Network interface lan1 on node eaipapp2 couldn't talk to itself.
Warning: Network interface lan2 on node eaipapp2 couldn't talk to itself.
Failed to gather configuration information.

each system have /.rhosts and cmclnodelist.

thx
10 REPLIES 10
yulianto piyut
Valued Contributor

Re: cmquerycl error

hi,

running cluster consists of 2 nodes (eaipapp1 & eaipapp2). I run cmqueycl in node eaipapp1. I try to querycl in new node (eaipapp6) and i have got new ascii file.

"cmquerycl -v -C clconfig.ascii -c cluster_wM -n eaipapp1 -n eaipapp2 -n eaipapp6"

when i want to check my ascii file, there are some error:

bash-3.00# cmcheckconf -v -C clconfig.ascii

Checking cluster file: clconfig.ascii
Note : a NODE_TIMEOUT value of 2000000 was found in line 144. For a
significant portion of installations, a higher setting is more appropriate.
Refer to the comments in the cluster configuration ascii file or ServiceGuard
manual for more information on this parameter.
Checking nodes ... Done
Checking existing configuration ... Done
Warning: Unknown message version: 108
Error: Error performing security validation. Please verify that identd is running properly.
Error: Failed to lookup /cluster in configuration database.
Error: Fail to load data from configuration database.
Internal error: Unable to open communications to configuration daemon: No such file or directory
Gathering configuration information ... Done
Gathering configuration information ............. Done

Error: Unable to determine device configuration: failed to send device query to node eaipapp1
Error: Unable to determine lvm configuration: failed to send lvm query to node eaipapp1
Warning: Not probing node eaipapp1 as it is currently unreachable.
This may cause network partitions to be reported.
cmcheckconf : Unable to reconcile configuration file clconfig.ascii
with discovered configuration information.

somebody knows about this ?

many thanks for your valuable time to troubleshoot my case!

-yut-
Matti_Kurkela
Honored Contributor

Re: cmquerycl error

"Warning: Unknown message version: 108"
Are you sure your new node is using the same version of ServiceGuard as your old nodes?

"Error: Error performing security validation. Please verify that identd is running properly."
Do as it says. All ServiceGuard nodes must have identd in working order, and each node must also be able to access each other's identd.

"Warning: Not probing node eaipapp1 as it is currently unreachable."
Looks like your node eaipapp1 is not reachable from the node you ran the command from. Find out why, and fix this.

MK
MK
yulianto piyut
Valued Contributor

Re: cmquerycl error

Matti,

thx for your command. what you ask to me is same what i ask to forum..:)
yulianto piyut
Valued Contributor

Re: cmquerycl error

hi,

in existing node, there is no patch PHSS_34505 MC/ServiceGuard A.11.15.00

is it can fix my problem if i install this patch to existing node ? i think need reboot cluster when install this patch

-yut-
Matti_Kurkela
Honored Contributor

Re: cmquerycl error

Well, I can't really go to your site and check that your cables are attached and your network switches are properly configured.

To solve the problem for you, we would need to know _at least_:
- which HP-UX version in each node?
- which ServiceGuard version in each node?
- what is your storage configuration (SCSI or FibreChannel, which devices are cluster disks)?
- what is your LAN configuration (how the nodes are connected together, which network interfaces are for production traffic and which for heartbeat)?
- after running cmquerycl, you should have edited the .ascii file to fill in some information. Did you? What did you put in?
- are you using a lock LUN or a quorum server in your cluster?
- why does your cluster have so many disks with no ID or disk label? Are they unused?
- do you have firewalls or packet filters in your network that might block communication between cluster members?
- do you have ipfilter installed on any of the nodes? It could also block connections like a firewall.

In the first cmquerycl, it says "Warning: Unable to determine local domain name for eaipapp1". That suggests there is some problem with /etc/nsswitch.conf, /etc/resolv.conf and/or /etc/hosts.
- so how is your name resolving *supposed* to be configured, and what does it say in these files on eaipapp1 now?

You might want to read the "Managing Serviceguard" manual.

http://docs.hp.com/en/ha.html#Serviceguard

The "Managing Serviceguard" book assumes the reader is competent with basic HP-UX system administration, like setting up name resolving, confirming identd is configured or using ping and linkloop to verify that the network physically works. Trying to set up Serviceguard without those basic skills would be like trying to run before you have learned to walk.

MK
MK
yulianto piyut
Valued Contributor

Re: cmquerycl error

thx,

now, i tried to do in new node (eaipapp6), and success in cmquerycl, i got ascii file (clconfig.ascii). when i want to check the ascii file (cmcheckconf), there are error:

# cmcheckconf -v -C clconfig.ascii

Checking cluster file: clconfig.ascii
Note : a NODE_TIMEOUT value of 2000000 was found in line 144. For a
significant portion of installations, a higher setting is more appropriate.
Refer to the comments in the cluster configuration ascii file or ServiceGuard
manual for more information on this parameter.
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information ............. Done

Error: Unable to determine device configuration: failed to send device query to node eaipapp6
Error: Unable to determine lvm configuration: failed to send lvm query to node eaipapp6
Warning: Not probing node eaipapp6 as it is currently unreachable.
This may cause network partitions to be reported.
cmcheckconf : Unable to reconcile configuration file clconfig.ascii
with discovered configuration information.


each server using hpux 11.i
freddy_21
Respected Contributor
Solution

Re: cmquerycl error

ok, i try to check one by one.

prerequisite:
1. check all serviceguard version same
2. check all QPK, HWE all server have same version.
3. check all patches SG for all servers.
4. check all kernel parameter for all server.
5. set IP for primary lancard and heartbeat ( different subnet). add ip adress for third servers at /etc/host. ( do for all server)
6. test connection for all lancard ( using linkloop ).
- 1 lancard for primary lancard
- 1 lancard for standby lancard
- 1 lancard for heart beat
Make sure :
- heart beat to primary lancard no connection
- heart beat to standby lancard no connection
- primary to standby have connection.
7. if using vglock, import vglock to third server.
8. import all disk to third server.


for implementation:
1. activate remote host for all server.
2. add file cmclnodelist for third server. and copy to all server.
3. cmquerycl -C cmclconfig.ascii -n n1 -n n2 -n n3
4. check for cmclconfig file that already created.
5. apply using cmapplyconf -v -C cmclconfig.ascii
6. run the third node
cmrunnode n3
7. continue to modify package configuration.



i hope it's help u.

thanks
freddy
yulianto piyut
Valued Contributor

Re: cmquerycl error

how about this?

# cmcheckconf -v -C cmclconfig.ascii

Checking cluster file: cmclconfig.ascii
Note : a NODE_TIMEOUT value of 2000000 was found in line 144. For a
significant portion of installations, a higher setting is more appropriate.
Refer to the comments in the cluster configuration ascii file or ServiceGuard
manual for more information on this parameter.
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information ............. Done

Error: Unable to determine device configuration: failed to send device query to node eaipapp6
Error: Unable to determine lvm configuration: failed to send lvm query to node eaipapp6
Warning: Not probing node eaipapp6 as it is currently unreachable.
This may cause network partitions to be reported.
cmcheckconf : Unable to reconcile configuration file cmclconfig.ascii
with discovered configuration information.
Steve Lewis
Honored Contributor

Re: cmquerycl error

For a start, increase your NODE_TIMEOUT value of 2000000 to 9000000 to make the warning go away.

Secondly check that you have the root account in cmnodelist on eaipapp6,
The new server eaipapp6 must be able to speak to ITSELF as well as the other servers.

then add the eaipapp6 node to the /etc/hosts file on all boxes, together with an FQDN for your hosts e.g.
1.2.3.4 eaipapp6.yourcompany.com eaipapp6

Then, check that this new node does not already have a duplicate volume group name as one of the VGs in a package. It must be the same VG with the same group file minor number, created with a vgimport or vxvm equivalent.

You have done the vgimport already haven't you?




yulianto piyut
Valued Contributor

Re: cmquerycl error

still failed!