On Thu, Aug 23, 2007 at 09:43:09AM +0200, Sebastian Reitenbach wrote: > Hi, > > Sebastian Reitenbach <[EMAIL PROTECTED]>,General Linux-HA > mailing list <[email protected]> wrote: > > Hi list, > > > > after upgrading a two node cluster from 2.0.8 to 2.1.2, running on SLES > 10, > > x86_64, I see every 17 seconds the following line in the logs: > > > > lrmd[3651]: 2007/08/22_18:28:30 notice: Not currently connected. > > > > should I worry about that note? > > after recreating the whole configuration via the GUI point n' click orgy, > this notice disappeared. Also the problem described below is gone, the > cluster seems to behave just fine now. > > > > > This happens when one node is stopped. Adding the second node to the > > cluster, then the IPaddr resources start to going crazy. It seems that are > > always the last IP addresses that are configured in the resources cib.xml > at > > the end that fail. Some of the IPaddr resources have no problem. The > > configuration worked for weeks with heartbeat 2.0.8. > > > > heartbeat spams about 5MB/minute into the logfiles, therefore I do not > want > > to append them here (: > > In case anybody is interested in logfiles/configuration old and new one, I > can open a bugzilla entry.
Yes. If it's not too much trouble. Do you still have your old configuration saved? Did you try to find differences between the old and the new one with crm_diff? The whole thing seems to be quite strange. > kind regards > Sebastian > > _______________________________________________ > 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
