When testing fail-over we get into this situation rather easily: ERROR : 0x0002020f 2738929630 25 1 28Nov2007_16.35.52.366 AVD: AN INVALID DATA VALUE at ./avd_avmmsg.c:409 val 0 ERROR : 0x0002020f 2738929630 25 1 28Nov2007_16.39.13.054 AVD: AN INVALID DATA VALUE at ./avd_ndfsm.c:149 val 2 ERROR : 0x0002020f 2738929630 25 1 28Nov2007_16.39.14.137 AVD: AN INVALID DATA VALUE at ./avd_ndfsm.c:149 val 2 ERROR : 0x0002020f 2738929630 25 1 28Nov2007_16.39.15.240 AVD: AN INVALID DATA VALUE at ./avd_ndfsm.c:149 val 2
I.e the active AVD is logging that the other just rebooted controller is in wrong state and it won't let it join the cluster. 'Val 2' means 'STATE_PRESENT'. I have also seen 'val 1' meaning 'STATE_NO_CONFIG' It gets stuck like this forever. Any ideas? I will collect more info tomorrow and update status. Regards, Hans _______________________________________________ Users mailing list [email protected] http://list.opensaf.org/maillist/listinfo/users
