On 05/13/2010 03:29 PM, Tim Serong wrote:
On 5/14/2010 at 07:39 AM, Paul Graydon wrote:
Hi,
One of my nodes decided to throw a wobbly this morning and locked up
it's network card for about a minute. Pacemaker came to the rescue,
merrily transferred everything over to the other
back across.
Is is possible at all to make resources sticky? i.e. resources start on
node 1. Node 1 fails, resources migrate to node 2. Node 1 recovers,
but resources stay on node 2 until node 2 fails, at which point they'd
migrate to node 1.
Paul
--
Paul Graydon
Senior Systems Adm
g/doc/Cluster_from_Scratch.pdf
--
Paul Graydon
Senior Systems Administrator
eHawaii.gov - Hawaii's State Internet Portal
808-695-4619
eHawaii.gov
p...@ehawaii.gov
*
CONFIDENTIALITY NOTICE:
This email and any attachments are confidential. If you
are not the intended
m our monitoring platform, but
was hoping there would be some kind of pacemaker method.
Regards,
Paul
--
Paul Graydon
Senior Systems Administrator
eHawaii.gov - Hawaii's State Internet Portal
808-695-4619
eHawaii.gov
p...@ehawaii.gov
*
CONFI
ng up the wrong tree, feel free to tell me :)
Paul
--
Paul Graydon
Senior Systems Administrator
eHawaii.gov - Hawaii's State Internet Portal
808-695-4619
eHawaii.gov
p...@ehawaii.gov
*
CONFIDENTIALITY NOTICE:
This email and any attachments are conf
ir, for example).
I found that meta target-role in primitives that are members of a group
conflict with the target-role of the group, so i got rid of these in the
primitives.
Tom
In this case, no, it's not but thats an interesting thought. I'm going
to knock up a couple o
On 2/18/2010 2:10 AM, Dejan Muhamedagic wrote:
Hi,
On Wed, Feb 17, 2010 at 04:59:16PM -1000, Paul Graydon wrote:
On 2/16/2010 1:04 PM, Angie T. Muhammad wrote:
On Wed, Feb 17, 2010 at 12:21 AM, Paul Graydonmailto:p...@ehawaii.gov>> wrote:
On 2/16/2010 10:48 AM, Andrew B
On 2/16/2010 1:04 PM, Angie T. Muhammad wrote:
On Wed, Feb 17, 2010 at 12:21 AM, Paul Graydon <mailto:p...@ehawaii.gov>> wrote:
On 2/16/2010 10:48 AM, Andrew Beekhof wrote:
The first error doesn't concern me particularly, it's a known
Apache bug
relating
dling e.g. the monitoring & automated service restarts.
--
Paul Graydon
Senior Systems Administrator
Hawaii Information Consortium
Internet Portal Partner with the Aloha state
808-695-4619 office
808-695-4618 fax
p...@ehawaii.gov
*
CONFIDENTIALITY NOTICE
On 2/16/2010 1:04 PM, Angie T. Muhammad wrote:
On Wed, Feb 17, 2010 at 12:21 AM, Paul Graydon <mailto:p...@ehawaii.gov>> wrote:
On 2/16/2010 10:48 AM, Andrew Beekhof wrote:
The first error doesn't concern me particularly, it's a known
Apache bug
relating
king about
setting that to be the IP address of the server it's on. Both seem to
work, but I've no idea what it should be and what the implications of it
being set wrong are. I'm inclined to trust "man corosync.conf" which
tells you to use the .0 network address, o
ver a hassle there.
The documentation does seem to make a large number of assumptions about
what users do or don't know about pacemaker style clustering, and it's
been far from a simple process to implement what should be a
straightforward 2 node failover. There is no obvious w
12 matches
Mail list logo
