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
I also found the same error right now! Not only from mgmtd, crmd and pengine caught them. crmd[4796]: 2008/02/29_16:40:26 ERROR: crm_abort: ha_set_tm_time: Triggered assert at iso8601.c:887 : rhs->tm_mday < 0 || lhs->days == rhs->tm_mday pengine[5057]: 2008/02/29_16:41:02 ERROR: crm_abort: ha_set_tm_time: Triggered assert at iso8601.c:887 : rhs->tm_mday < 0 || lhs->days == rhs->tm_mday I run heartbeat 2.1.3-15.1 + pacemaker 0.6.2-11.1 on redhat 5.1. Is it something about bissextile day? Thanks, Junko > 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
