On 08/08/2013, at 3:49 PM, Thomas Glanzmann <tho...@glanzmann.de> wrote:
> Hello Andrew,
>
>> It really helps to read the output of the commands you're running:
>
>> Did you not see these messages the first time?
>
>> apache-03: WARN: Unknown cluster type: any
>> apache-03: ERROR: Could not determine the location of your cluster logs,
>> try specifying --logfile /some/path
>> apache-04: ERROR: Could not determine the location of your cluster logs,
>> try specifying --logfile /some/path
>
>> Try adding -H and --logfile {somevalue} next time.
>
> I'll do that and report back.
>
>> An updated pacemaker is the important part. Whether you switch to
>> corosync too is up to you.
>
> I'll do that.
>
>> Pacemaker+heartbeat is by far the least tested combination.
>
> What is the best tested combination? Pacemaker and corosync? Any
> specific version or should I go with the lastest release of both?
SUSE tests corosync 1.x (with the plugin) and is starting to dabble with
corosync 2.x
I, and Red Hat, test corosync 1.x (with cman) and corosync 2.x
>
>> Best to poke the debian maintainers
>
> I'll do that as well.
>
>> Do you mean "See that the monitors _work, then_ take the system out of
>> maintance mode..."? If so, then yes.
>
> Yes, that is what I want to do. :-)
>
> Cheers,
> Thomas
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
