- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Can i add a new package even if there are errors i...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2007 04:25 PM
07-09-2007 04:25 PM
Can i add a new package even if there are errors in cmcheckconf???
When am doing cmcheckconf it's reporting some problems related to LVM. Is it possible that i can add a new package in cluster while having these errors??
Your urgent response on this is highly apreciated. Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2007 05:40 PM
07-09-2007 05:40 PM
Re: Can i add a new package even if there are errors in cmcheckconf???
I would recommend to solve the problems first anyway.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2007 11:04 PM
07-09-2007 11:04 PM
Re: Can i add a new package even if there are errors in cmcheckconf???
Regards,
Ninad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2007 11:25 PM
07-09-2007 11:25 PM
Re: Can i add a new package even if there are errors in cmcheckconf???
You can add them but they won't run until the errors are resolved. So the real answer is no.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2007 12:46 AM
07-10-2007 12:46 AM
Re: Can i add a new package even if there are errors in cmcheckconf???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2007 02:55 AM
07-10-2007 02:55 AM
Re: Can i add a new package even if there are errors in cmcheckconf???
tppora02:/etc/cmcluster#cmcheckconf -v -C cluster.ascii
Checking cluster file: cluster.ascii
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information ..
Gathering storage information ..
Found 257 devices on node tppovw01
Found 194 devices on node tppovw02
Found 307 devices on node tppora01
Found 281 devices on node tppora03
Found 366 devices on node tppora02
Found 350 devices on node tppora04
Found 162 devices on node tppora05
Found 241 devices on node tppora06
Analysis of 2158 devices should take approximately 25 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 21 volume groups on node tppovw01
Found 15 volume groups on node tppovw02
Found 18 volume groups on node tppora01
Found 17 volume groups on node tppora03
Found 18 volume groups on node tppora02
Found 17 volume groups on node tppora04
Found 23 volume groups on node tppora05
Found 29 volume groups on node tppora06
Analysis of 158 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
.....
Gathering Network Configuration .............. Done
Error: The volume group called /dev/xpvgsiedata1 on node tppora01 is called /dev/BC1_xpvgsiedata1 on other nodes.
Error: The volume group called /dev/xpvgsiedata1 on node tppora03 is called /dev/BC1_xpvgsiedata1 on other nodes.
Error: The volume group called /dev/xpvgsiedata1 on node tppora02 is called /dev/BC1_xpvgsiedata1 on other nodes.
Error: The volume group called /dev/xpvgsiedata1 on node tppora04 is called /dev/BC1_xpvgsiedata1 on other nodes.
Error: The volume group called /dev/xpvgsieapp on node tppora01 is called /dev/BC1_xpvgsieapp on other nodes.
Error: The volume group called /dev/xpvgsieapp on node tppora03 is called /dev/BC1_xpvgsieapp on other nodes.
Error: The volume group called /dev/xpvgsieapp on node tppora02 is called /dev/BC1_xpvgsieapp on other nodes.
Error: The volume group called /dev/xpvgsieapp on node tppora04 is called /dev/BC1_xpvgsieapp on other nodes.
Error: The volume group called /dev/xpvgsiedata5 on node tppora02 is called /dev/BC1_xpvgsiedata5 on other nodes.
Error: The volume group called /dev/xpvgsiedata5 on node tppora04 is called /dev/BC1_xpvgsiedata5 on other nodes.
Error: The volume group called /dev/xpvggendata1 on node tppora01 is called /dev/BC2_xpvggendata1 on other nodes.
Error: The volume group called /dev/xpvggendata1 on node tppora03 is called /dev/BC2_xpvggendata1 on other nodes.
Error: The volume group called /dev/xpvggendata1 on node tppora02 is called /dev/BC2_xpvggendata1 on other nodes.
Error: The volume group called /dev/xpvggendata1 on node tppora04 is called /dev/BC2_xpvggendata1 on other nodes.
Error: The volume group called /dev/xpvggenapp on node tppora01 is called /dev/BC2_xpvggenapp on other nodes.
Error: The volume group called /dev/xpvggenapp on node tppora03 is called /dev/BC2_xpvggenapp on other nodes.
Error: The volume group called /dev/xpvggenapp on node tppora02 is called /dev/BC2_xpvggenapp on other nodes.
Error: The volume group called /dev/xpvggenapp on node tppora04 is called /dev/BC2_xpvggenapp on other nodes.
Error: The volume group called /dev/xpvggendata5 on node tppora01 is called /dev/BC2_xpvggendata5 on other nodes.
Error: The volume group called /dev/xpvggendata5 on node tppora03 is called /dev/BC2_xpvggendata5 on other nodes.
Error: The volume group called /dev/xpvggendata5 on node tppora02 is called /dev/BC2_xpvggendata5 on other nodes.
Error: The volume group called /dev/xpvggendata5 on node tppora04 is called /dev/BC2_xpvggendata5 on other nodes.
Warning: The volume group /dev/BC1_xpvgsiedata1 is activated on more than one node:
tppovw01
tppora02
Warning: The volume group /dev/BC1_xpvgsieapp is activated on more than one node:
tppovw01
tppora02
Warning: The volume group /dev/BC1_xpvgsiedata5 is activated on more than one node:
tppovw01
tppora02
Warning: The volume group /dev/xpvgtibapp is activated on more than one node:
tppora01
tppora02
Warning: Volume group /dev/xpvgtibdata is configured differently on node tppora01 than on node tppora03
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t2d6 on node tppora01 (32147000661180771383).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t2d6 on node tppora01 (32147000661180771383).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t2d7 on node tppora01 (32147000661180771398).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t2d7 on node tppora01 (32147000661180771398).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t3d0 on node tppora01 (32147000661180771423).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t3d0 on node tppora01 (32147000661180771423).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t3d1 on node tppora01 (32147000661180771429).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t3d1 on node tppora01 (32147000661180771429).
Warning: Volume group /dev/xpvgtibdata is configured differently on node tppora03 than on node tppora01
Warning: Volume group /dev/xpvgtibdata is configured differently on node tppora03 than on node tppora02
Warning: Volume group /dev/xpvgtibdata is configured differently on node tppora03 than on node tppora04
Warning: Volume group /dev/xpvgtibdata is configured differently on node tppora02 than on node tppora03
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t2d6 on node tppora02 (32147000661180771383).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t2d6 on node tppora02 (32147000661180771383).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t2d7 on node tppora02 (32147000661180771398).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t2d7 on node tppora02 (32147000661180771398).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t3d0 on node tppora02 (32147000661180771423).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t3d0 on node tppora02 (32147000661180771423).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t3d1 on node tppora02 (32147000661180771429).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t3d1 on node tppora02 (32147000661180771429).
Warning: Volume group /dev/xpvgtibdata is configured differently on node tppora04 than on node tppora03
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c26t2d6 on node tppora04 (32147000661180771383).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c27t2d6 on node tppora04 (32147000661180771383).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c26t2d7 on node tppora04 (32147000661180771398).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c27t2d7 on node tppora04 (32147000661180771398).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c26t3d0 on node tppora04 (32147000661180771423).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c27t3d0 on node tppora04 (32147000661180771423).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c26t3d1 on node tppora04 (32147000661180771429).
Error: Volume group /dev/xpvgtibdata on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c27t3d1 on node tppora04 (32147000661180771429).
Warning: Volume group /dev/xpvgtibdata1 is configured differently on node tppora01 than on node tppora03
Error: Volume group /dev/xpvgtibdata1 on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t2d5 on node tppora01 (32147000661180523594).
Error: Volume group /dev/xpvgtibdata1 on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t2d5 on node tppora01 (32147000661180523594).
Warning: Volume group /dev/xpvgtibdata1 is configured differently on node tppora03 than on node tppora01
Warning: Volume group /dev/xpvgtibdata1 is configured differently on node tppora03 than on node tppora02
Warning: Volume group /dev/xpvgtibdata1 is configured differently on node tppora03 than on node tppora04
Warning: Volume group /dev/xpvgtibdata1 is configured differently on node tppora02 than on node tppora03
Error: Volume group /dev/xpvgtibdata1 on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c30t2d5 on node tppora02 (32147000661180523594).
Error: Volume group /dev/xpvgtibdata1 on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c29t2d5 on node tppora02 (32147000661180523594).
Warning: Volume group /dev/xpvgtibdata1 is configured differently on node tppora04 than on node tppora03
Error: Volume group /dev/xpvgtibdata1 on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c26t2d5 on node tppora04 (32147000661180523594).
Error: Volume group /dev/xpvgtibdata1 on node tppora03 does not appear to have a physical volume corresponding to /dev/dsk/c27t2d5 on node tppora04 (32147000661180523594).
Warning: Volume group /dev/vgcsafscan is configured differently on node tppora05 than on node tppora06
Warning: Volume group /dev/vgcsafscan is configured differently on node tppora06 than on node tppora05
Warning: Volume groups should not be activated on more than one node.
Use vgchange to de-activate a volume group on a node.
cmcheckconf : Unable to reconcile configuration file cluster.ascii
with discovered configuration information.
tppora02:/etc/cmcluster#
I would appreciate if someone help me to rectify the errors as well
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2007 11:28 AM
07-10-2007 11:28 AM
Re: Can i add a new package even if there are errors in cmcheckconf???
is not configured appropriatelly ,I thing.
Anyway, if you say, that it working, try:
#cmcheckconf -v -P
And if you dont have errors:
#cmapplyconf -v -P
to add the package to cluster.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2007 01:54 PM
07-10-2007 01:54 PM
Re: Can i add a new package even if there are errors in cmcheckconf???
update the package directory sync with primary on all alternate nodes.