cation loc_ms_IPaddr2_1_U-HB-HA-NODE-1 ms_IPaddr2_1 inf: U-HB-HA-NODE-1
location loc_ms_IPaddr2_1_U-HB-HA-NODE-2 ms_IPaddr2_1 inf: U-HB-HA-NODE-2
property $id="cib-bootstrap-options" \
stonith-enabled="false" \
dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec
Hi Marcus,
A quick update.. both nodes are seeing ping requests at the interface as
suspected using a broadcast mac address.
The proxy as you provided, resolves issue with assigned mac addresses..
There is something going awry . local route tables for the network are
good, ssh connects 70% of t
as
well.. it could be the same issue, I can't inspect the routing tables on
the vmware internal switch.
again thanks
On Fri, Aug 9, 2013 at 2:30 AM, Marcus Bointon wrote:
> On 9 Aug 2013, at 06:29, Gary Mazzaferro wrote:
>
> > Additionally, the traffic to the nodes seem interleav
Hi
Been a while since I last used heartbeat/pacemaker for a two node A/P IP
failover.
I can't seem to get one node to become master. Both nodes are listed as
slaves.
I have no other services configured.
Additionally, the traffic to the nodes seem interleaved, random connection
to node1/node2 fr
te -c from one
of the dom0's. You may also want to ensure that in the "extra" line you
also add "xencons=tty" as without this directive it can prevent console
messages from displaying after the console driver loads during the vm boot
process.
hth,
Gary W. Stansbury
is easy to configure Pacemaker to simply alert a sysadmin of
problems?
Many thanks for any advice.
Gary
___
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
h
its own ilo, since it can't suicide itself with the riloe stonith plugin.
Gary W. Stansbury II
Lead LAN Engineer
gary_stansb...@nexweb.org
757-631-3356
From:
ow... this looks a lot like when
the stonith daemon on the dc broadcasts for help to stonith a failed node, it
gives up too quickly or ignores the success response from the "whodoit" node
that actually (successfully!) peforms the stonith.
Thanks in advance for your help,
Gary
- Original Message -
From: Michael Schwartzkopff
To: General Linux-HA mailing list
Sent: Wednesday, April 02, 2008 1:24 PM
Subject: Re: [Linux-HA] Setup HA on Openvz
Am Mittwoch, 2. April 2008 17:45 schrieb Gary:
> Yes, I am very interested in your setup. I am new
- Original Message -
From: "Michael Schwartzkopff" <[EMAIL PROTECTED]>
To: "General Linux-HA mailing list"
Sent: Tuesday, April 01, 2008 3:03 PM
Subject: Re: [Linux-HA] Setup HA on Openvz
Am Dienstag, 1. April 2008 17:03 schrieb Gary:
I am tring to setu
- Original Message -
From: "Michael Schwartzkopff" <[EMAIL PROTECTED]>
To: "General Linux-HA mailing list"
Sent: Tuesday, April 01, 2008 3:03 PM
Subject: Re: [Linux-HA] Setup HA on Openvz
Am Dienstag, 1. April 2008 17:03 schrieb Gary:
I am tring to setu
tbeat: [21746]: CRIT: Killing pid 21743 with
SIGTERM
Apr 1 10:13:40 cluster-dev2 heartbeat: [21746]: CRIT: Emergency Shutdown(MCP
dead): Killing ourselves.
Does anybody know how to setup HA in Openvz?
Gary
___
Linux-HA mailing list
Linux-HA@lists.linux-h
permitted
Mar 21 13:41:37 cluster-dev1 heartbeat: [16233]: info: Link
cluster-dev1.Test.net:eth0 up.
How can I fix these errors? Will my heartbeat still work?
Gary
~
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.o
bove scenario. All
advice is welcome.
Thanks,
Gary
___
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
Even though I configure the option --disable-ipmilan when building HA,
when running "make rpm" it still requires OpenIPMI-devel. Is
OpenIPMI-devel really still necessary?
Gary
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://l
.
Is there a way around this?
Gary
Dejan Muhamedagic wrote:
Hi,
On Fri, Jan 11, 2008 at 10:22:48AM -0500, Gary Schlachter wrote:
I have a problem with heartbeat dying. I have a 3 node cluster running
HA 2.0.8 on Fedora Core 1. They are providing a single IP address
resource. They are
I have a problem with heartbeat dying. I have a 3 node cluster
running HA 2.0.8 on Fedora Core 1. They are providing a single IP
address resource. They are using eth0 as the heartbeat mechanism. If I
disconnect the eth0 cable from the node which is providing the IP
address, one of the ot
? I have scoured the website but the examples are
out-of-date with the DTD.
Thanks in advance,
Gary
___
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
g/ha-debug
logfile /var/log/ha-log
entity logd
What am I missing so that I can stop all of the syslog messages from
being sent. I know I can change syslog.conf but I thought, based on
various articles, that I could disable the syslog messages from ever
being sent.
Thanks in adv
19 matches
Mail list logo
