Hi Sebastian
Sorry for the delay, I'm still catching up on the last few emails that
arrived during my vacation...
Unfortunately the hb_report is missing the pengine files I need to
debug this.
Having said that, you've probably come across a bug I spent some of
last week fixing...
There will be a new pacemaker release in about 2 weeks containing the
latest batch of bugfixes.
But it is probably worth checking that the behavior you're seeing is
definitely resolved... do you still have the /var/lib/heartbeat/
pengine contents relevant to this hb_report?
Andrew
On Feb 27, 2008, at 6:05 PM, Sebastian Reitenbach wrote:
Hi,
I have a two node cluster, the resources are divided into two
groups. Both
groups are collocated=false and ordered=false. There are some
constraints to
keep the group on a given host, and some orders, but nothing what
could
explain me why happened what I have seen.
I stopped one resource in group_Master102, AFH_5, so this one
stopped, but
all other resources in that group were restarted too. I cannot see the
reason why the other resources in that group were restarted too,
when I just
wanted to shutdown only one of them.
I expected only the AFH_5 resource to be stopped, and the others
just stay
running. When starting a stopped resource in a group, this
phenomenon does
not happen. I've appended the output of hb_report tool.
I'm on sles10sp1 x86_64, running heartbeat 2.1.2.
kind regards
Sebastian
<report.out2.tar.gz>_______________________________________________
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
