Hello all,
I've been using heartbeat for a couple of years now to manage a
couple of virtual IPs for replicating Mysql servers. I have to redo a
similar setup now and was looking to use the new heartbeat 3.
I was looking for the quorumd that I used to use, but from what I read
it seems to
with --template xxx.tmp).
> > Please note that the CN in both client and server cert
> should be same
> > as the cluster name.
> >
> > Tell me the result. Thanks!
> >
> > On 5/10/07, Benjamin Lawetz <[EMAIL PROTECTED]> wrote:
> > > I've
on the ha "universe" page there was an
> information about this.
> >> But I don't understand why heartbeat dont try the first node just
> >> once again. If the first node is ok why heartbeat shouln'd
> move the
> >> resource back to the fi
-n mysql_running -d 3s -v 1
> exit 0
> else
> /usr/sbin/attrd_updater -n mysql_running -d 3s -v 0
> exit 3
> fi
> ;;
> *)
> echo $"Usage: $0 {start|stop|status} (start|stop faked)"
> exit 1
> esac
>
> --
>
Hi Markus,
I ran into the same problem. Didn't find any better way than to
modify the monitoring script of mysql and add in the case of a failure:
/usr/sbin/attrd_updater -n mysql_running -d 5s -v 0
And in the case of a success:
/usr/sbin/attrd_updater -n mysql-mod_running -d 5s -v 1
I've been trying to get the quorum server to work for the past couple of
days. But whenever I launch heartbeat I juste get on the quorumd server
logs:
May 8 14:50:42 quorumd: [10151]: WARN: handshake failed
May 8 14:50:42 quorumd: [10151]: ERROR: on_listen tls handshake failed
I'm sure it's a st
> > I've been running some tests on my heartbeat setup with STONITH.
> > When I go live, there will a serial connection, a crossover
> ethernet
> > and the main ethernet for heartbeat. For the purpose of my
> tests, I've
> > changed the config just to broadcast the heartbeat on the
> cross
e: [Linux-HA] Stonith in 2 node setup
>
> Benjamin Lawetz wrote:
> > Hi,
> >
> > I've been running some tests on my heartbeat setup with STONITH.
> > When I go live, there will a serial connection, a crossover
> ethernet
> > and the main ethernet
Hi,
I've been running some tests on my heartbeat setup with STONITH.
When I go live, there will a serial connection, a crossover ethernet and the
main ethernet for heartbeat. For the purpose of my tests, I've changed the
config just to broadcast the heartbeat on the crossover cable.
Using cibadmin
For example to create a node:
Create a file node.xml containing your node definition ex:
Then run
cibadmin -C -o nodes -X node.xml
Deleteing,updating of resources can also be done with cibadmin. Juste use
cibadmin --help to find out more.
Dave.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Dave Blaschke
> Sent: May 2, 2007 2:30 PM
> To: General Linux-HA mailing list
> Subject: Re: [Linux-HA] External STONITH timeout
>
> Benjamin Lawetz wrote:
&
Hi all,
I've written an external stonith plugin for a Sentry power switch.
It works fine from the command line (save that it takes 25s for the ssh to
login). This causes problems when the STONITH tries to kill the other
server. From the logs I can tell the stonith times out after 30s:
te
I have a 2 node setup giving HA for an IP for mysql servers.
The Mysql servers are replicating and therefore should always be running. So
I don't want them to be managed by heartbeat. But I do need the monitoring.
So I made a classic 2 node IP sharing with pingd clones to check for it's
connectivit
I'm upgrading my existing mysql replication to new servers and moving up
from heartbeat 1.x to 2.x
I've got the basics up and running and was reading up on the monitoring
feature. I'm a little confused so I just wanted to run this by you guys to
make sure I understood correctly:
I have 2 mysql ser
14 matches
Mail list logo
