On Thu, Aug 23, 2007 at 12:29:04PM +0200, Andrew Beekhof wrote: > On 8/23/07, Dejan Muhamedagic <[EMAIL PROTECTED]> wrote: > > On Wed, Aug 22, 2007 at 06:44:52PM +0200, Sebastian Reitenbach 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? > > > > Yes, I've noticed these appearing too. They are not very > > informative either. Must be annoying. I'll see if I can make them > > I think that must have been me. > Sorry, I'm used to crm logging that automagically includes the > function name which provides context. > > > disappear. Otherwise, you shouldn't worry about it: it happens > > when a stonith client wants to disconnect from stonithd, but it > > was not connected in the first place. > > why would the lrm be doing this? > i think thats the better bug to try and fix :-)
Yep, and that's what I meant with "make them disappear". > > > > > > 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. > > > > An interesting problem. Can't say anything without logs, just > > that it is unexpected that 2.1.2 misbehaves when compared to > > 2.0.8. > > > > > heartbeat spams about 5MB/minute into the logfiles, therefore I do not > > > want > > > to append them here (: > > > > Could you please open a bugzilla for this. Attach the > > configuration, logs, and whatever else you find relevant. > > > > Thanks, > > > > Dejan > > > > > Is this known to somebody else? > > > > > > 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 > > > _______________________________________________ > 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
