I am getting it too, after midnight on 2/29 in leap year - looks like a date bug to me :)
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:linux-ha- > [EMAIL PROTECTED] On Behalf Of Sebastian Reitenbach > Sent: Friday, February 29, 2008 12:31 AM > To: [email protected] > Subject: [Linux-HA] ERROR: crm_abort: ha_set_tm_time: Triggered assert > atiso8601.c:887 > > Hi, > > I've seen these messages appearing when I connect the hb_gui to the > mgmtd: > > mgmtd[6819]: 2008/02/29_08:03:51 ERROR: crm_abort: ha_set_tm_time: > Triggered > assert at iso8601.c:887 : rhs->tm_mday < 0 || lhs->days == rhs->tm_mday > > and they are also shown in the output of crm_verify: > > crm_verify -LV > crm_verify[17297]: 2008/02/29_08:24:25 ERROR: crm_abort: > ha_set_tm_time: > Triggered assert at iso8601.c:887 : rhs->tm_mday < 0 || lhs->days == > rhs->tm_mday > > I've made sure using ntp, that both cluster nodes have the same time. > I'm wondering what this message is all about, and how I could clean > that up? > To clean up failed resources, I'd take crm_resource, but how do I clean > this? I already tried to shutdown both cluster nodes, and then removing > all > vital stuff from /var/lib/heartbeat, e.g. rm crm/* h* delhostcache > pengine/*, and then restarted heartbeat, and loaded the cluster > configuration again. Then when connecting the hb_gui again, the error > message showed up again. > > I'm on sles10sp1, running heartbeat 2.1.3 > > 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
