This is a discussion on Sun Cluster 3.1 - Strange Errors within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> Hi I've just put together a Sun Cluster 3.1 installation on Solaris 9. When the second node boots, the ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi I've just put together a Sun Cluster 3.1 installation on Solaris 9. When the second node boots, the following gets reported in /var/adm/messages Feb 8 16:10:54 eastgate xntpd[227]: couldn't resolve `clusternode16-priv', giving up on it Feb 8 16:10:59 eastgate INITUCMM: Notice: not OK to join, retry in 10 seconds (#1) Feb 8 16:11:10 eastgate INITUCMM: Notice: not OK to join, retry in 10 seconds (#2) Feb 8 16:11:21 eastgate INITUCMM: Notice: not OK to join, retry in 10 seconds (#3) Feb 8 16:11:32 eastgate INITUCMM: Notice: not OK to join, retry in 10 seconds (#4) Feb 8 16:11:42 eastgate INITUCMM: Notice: not OK to join, retry in 10 seconds (#5) Feb 8 16:12:02 eastgate ID[SUNWudlm.udlm]: Unix DLM version (2) and SUN Unix DLM library version (1): compatible. What do the INITUCMM messages mean, and how can I track down the cause. Eventually the node joins the cluster formed by the first node. At which point the cluster seems to be okay. Occasionally I also get the following message in /var/adm/messages. Any ideas what means and is it serious. Again the cluster seems to operate normally. # Feb 8 17:50:24 eastgate xntpd[226]: two instances of default interface for 172.16.194.6 in hash table Thanks for your time. -- Regards Nick nick@nickhavardxyz.com P.S. Remove xyz to reply |