make_recovery

[Joe Profaizer]

During our make_recovery, I received the following errors -- please let me know the criticality.
--------------
WARNING: Unable to parse ServiceGuard query command (/usr/sbin/cmquerycl -n
$(hostname) -l lvm -v 2> /dev/null | /usr/bin/awk '{print $1}').
WARNING: Service Guard was detected by the presence of the
"/usr/sbin/cmquerycl" command. However, "/usr/sbin/cmquerycl" failed
to return the required volume group information. A second attempt
will be made using vgdisplay(1M)
------------------

Thanks,
..Joe

[John Palmer · Accepted solution]

It doesn't sound 'critical' to me. It looks as though Ignite tried using 'cmquerycl' to obtain LVM information because it noted that you had it installed. Are you using Serviceguard and can you run cmquerycl yourself?

Having detected that cmquerycl failed, Ignite resorted to using vgdisplay to obtain the LVM information. Presumably this is what it does if Serviceguard is not installed anyway.

[Rita C Workman]

It could be a patch issue.....check and see if you have the following (depending on your o/s version):

PHSS_21867 (10.2)
PHSS_21866 (11.0)

Just a thought,

[Stefan Farrelly]

make_recovery is doing a cmquerycl -n -l lvm command to see the VG/Lvm info on your server, but it returned an error or warning. Try running the command manually and see if you can resolve the errors/warnings. Personally I dont think its anything to worry about, the cmquerycl command often reports problems which arent problems, happens on our SG nodes also. Just let make_recovery carry on.

[Cheryl Griffin]

Starting with Ignite version 2.2, make_recovery will attempt to use cmquerycl to capture the lvm information on any system that uses Service Guard. It is important to use cmquerycl so that the shared volume information and all other lvm information is written to the archive.

If cmquerycl fails, make_recovery will resort to using vgdisplay to capture the LVM information.

If this is a true Service Guard environment, you might want to run cmquerycl to see if it fails. If it does, you may have a networking problem that needs to be addressed.
# cmquerycl -v -n [node1] -n [node2] -C [asciifile]

[Joe Profaizer]

Thanks all -- for the help. We don't even have MC/ServiceGuard installed -- to my knowledge. Therefore, I'll just let ignite ride on.

..Joe

[Wodisch_1]

Hi Joe,
what version of Ignite/UX do use use?
Only the most recent ones support MC/SG!
i.e 2.4 and 2.5 - hence, download/install
those.
HTH,
Wodisch