On 2008-03-06T11:03:05, Luis Motta Campos <[EMAIL PROTECTED]> wrote:
> All four machines are the same "CentOS 5 (final)", all four machines are
> using the same package set and where installed from the same DVD copy.
> They literally share the same hardware, under VMware, and everything
> else is "virtual hardware" cloned from a single copy.
>
> The first two machines (let's call them "Set A") works perfectly.
>
> The other two machines ("Set B") doesn't: I got this error, and no
> results at all.
>
> I wonder how a packaging error could produce such results.
> Anyway, I will try and report it and see what happens. Maybe they have
> similar reports over there.
That is indeed weird, but on the other hand, I know of no option in any
part of the heartbeat/CRM configuration which could cause that. The only
possible causes I can think of are installation, packaging, or OS
environment errors somewhere.
If they are all cloned, rpm --verify might point out some differences,
or even diff -r on the filesystems themselves.
Does /usr/share/heartbeat/BasicSanityCheck succeed on all systems?
Good luck and please let us know if you find out what caused this.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
