after upgrading the servers to sp2 (they where running sles10 sp1) the problem server now happily joins the cluster. I'm not sure what happened, but anyway they are now working.
thanks >>> From: Andrew Beekhof<[EMAIL PROTECTED]> To:[email protected] Date: 20/11/08 8:41 Subject: Re: [Linux-HA] second node fails to join cluster after resource change On Wed, Nov 19, 2008 at 14:13, Navatala <[EMAIL PROTECTED]> wrote: > Hi Andrew, > > The changes where made via the gui. > I'm getting the customer to upgrade now. > the interesting thing is if it is two new for one node why is it apparently > not to new for the other? good question - hard to say without knowing exactly what you changed perhaps they're not really both the same version? > I've gone in an removed the changes but that has not resolved the issue, I > need to wait till they upgrade before taking another look. > > tia > > > > >>>> > From: Andrew Beekhof<[EMAIL PROTECTED]> > To:[email protected] > Date: 19/11/08 13:44 > Subject: Re: [Linux-HA] second node fails to join cluster after resource > change > On Tue, Nov 11, 2008 at 15:12, <[EMAIL PROTECTED]> wrote: >> Hi >> >> I made some changes to a group of resources, nothing special just increade >> the timeout values, unfortunately now after restarting heartbeat on both >> nodes I find than only one node will actually come online. >> >> The log files for the other nodes shows warnings and errors sj'uch as >> >> >> Nov? 7 14:45:09 node4 cib: [4108]: WARN: cib_init: CCM Activation failed >> Nov? 7 14:45:09 node4 cib: [4108]: WARN: cib_init: CCM Connection failed 1 >> times (30 max) >> >> and >> >> Nov? 7 14:45:13 node4 crmd: [4112]: ERROR: revision_check_callback: This >> build (2.0.8) does not support the current resource configuration >> Nov? 7 14:45:13 node4 crmd: [4112]: ERROR: revision_check_callback: We can >> support up to CIB feature set 1.3 (current=2.0) >> Nov? 7 14:45:13 node4 crmd: [4112]: ERROR: revision_check_callback: Shutting >> down the CRM >> >> any ideas on what is happening? >> >> I've attached the full log with all the details > > Apart from the actual changes you made :-) > Did make them manually or with the GUI? > > Also, 2.0.8 is really old - I'd highly recommend upgrading. > > Apart from that, the message means what it says - there is something > in your configuration that is too "new" for the version of the > software you have. > So rather than do something wrong, it shuts down. > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
