On 2006-08-28T09:00:31, Scott Simpson <[EMAIL PROTECTED]> wrote:
> Redhat 4, 2.6.9-42.0.2.ELsmp kernel, Heartbeat 2.0.7-1
>
> I was running heartbeat 2.0.4 just fine for a while until I upgraded
> some RPMs. Then things started breaking. I upgraded to 2.0.7 and that
> didn't solve my problem. I seem to be having some problem at the comms
> or membership layer since when I do a "ccm_tool -p" on vaha01 it returns
> "vaha01" but when I do a "ccm_tool -p" on the backup vaha02 it returns
> nothing. The networking set up is just fine (ping, routing tables, all
> that stuff is OK and hasn't changed). Also, I'm getting messages like
Is the ha.cf identical on both nodes? Firewall rules? Your logs are
typical of a setup where the nodes do not communicate.
"just fine until I upgraded some RPMs" doesn't sound too good; was it
just heartbeat you updated, or what did you change? Your phrasing
indicates that the breakage prompted you to upgrade heartbeat as the
second step, but then I'd venture that heartbeat isn't responsible, just
a victim ...
Which heartbeat packages did you install? Did you build them yourself on
the RHEL boxes?
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
