09-12-2012 01:27 AM
Hi All ,
i am getting following error while joining 2 cluster nodes .
please help me out seggregate the issue and resolve the problem.
here mdmd2_node is not joining cluster .
2012/08/29 04:39:54 VCS INFO V-16-1-10077 Received new cluster membership
2012/08/29 04:39:54 VCS NOTICE V-16-1-10112 System (mdmd_node) - Membership: 0x7, DDNA: 0x0
2012/08/29 04:39:54 VCS ERROR V-16-1-10079 System mdmd2_node (Node '3') is in Down State - Membership: 0x7
2012/08/29 04:39:54 VCS INFO V-16-6-15004 (mdmd_node) hatrigger:Failed to send trigger for sysoffline; script doesn't exist
2012/08/29 04:40:40 VCS INFO V-16-1-10077 Received new cluster membership
2012/08/29 04:40:40 VCS NOTICE V-16-1-10112 System (mdmd_node) - Membership: 0x7, DDNA: 0x8
2012/08/29 04:40:40 VCS ERROR V-16-1-10113 System mdmd2_node (Node '3') is in DDNA Membership - Membership: 0x7, Visible: 0x0
2012/08/29 04:52:42 VCS NOTICE V-16-1-10322 System (Node '3') changed state from UNKNOWN to INITING
2012/08/29 04:52:42 VCS ERROR V-16-1-10111 System mdmd2_node (Node '3') is in Regular and Jeopardy Memberships - Membership: 0xf, Jeopardy: 0x8
Regards
Siddesh
Solved! Go to Solution.
09-12-2012 01:43 AM
DDNA means "Daemon Dead Node Alive", so there is a problem with "had" daemon on the node trying to join - you could perhaps try killing "had" and wait for "hadshadow" to restart "had", or kill both "had" and "hadshadow" and run hastart.
Mike
09-12-2012 01:43 AM
DDNA means "Daemon Dead Node Alive", so there is a problem with "had" daemon on the node trying to join - you could perhaps try killing "had" and wait for "hadshadow" to restart "had", or kill both "had" and "hadshadow" and run hastart.
Mike
09-12-2012 01:46 AM
agree with Mike - check the logs on node mdmd2_node to find out if 'had' process is exiting abruptly.
09-18-2012 01:33 AM
any updates?
09-19-2012 05:46 AM
yes , had was issue , i brought down had and hashadow brought it back up cleanly .
09-19-2012 05:46 AM
thanks to both of you .