[EMAIL PROTECTED] wrote:
Hi all,
I tried to start the resource IPaddr using OCF script. I could do
that successfully.
Now I am trying to start another resource xinetd using lsb. But I am
not able to start this xinetd service.
I am attaching the xml file and the log and I am
I think I ran into this exact issue. I was calling crm_master -v 100 to
upgrade to master status too frequently. The postgres database needs to
stay in master state once its there, and not transition frequently. Are
there any other command line tools that could be used to retrieve what
state CRM
Peter Kruse wrote:
Hi!
Alan Robertson wrote:
Could you make a patch-format file for this, and send it to the list as
an ASCII attachment?
attached.
BTW, the error message you get when you try to stonith with the wrong
apcmastersnmp.so is somewhat misleading:
# stonith -t apcmastersnmp -p
Hi Dave,
Dave Blaschke wrote:
I cannot find the Config info syntax: message in the latest or any of
the most recent 2.0.x code - what version of heartbeat are you using?
Oops, yes that was an old version, but that doesn't make a difference
concerning the oids.
Regardless, you should get a
On 4/3/07, Doug Knight [EMAIL PROTECTED] wrote:
Thanks. Yes, I'm concerned that I'm seeing the spinning and your not.
However, I need to push through to getting my OCF script working, and using
my version of crm_master will allow me to do that. I'll have to take the
added demote into
The key word in my question was thinks. It would be useful to the RA
if it could know what state the CRM thought it was in, so in case the RA
determines on its own that its already in that state, it doesn't have to
do anything. But, if the RA finds that the CRM thinks its in a different
state,
Peter Kruse wrote:
Hi Dave,
Dave Blaschke wrote:
I cannot find the Config info syntax: message in the latest or any
of the most recent 2.0.x code - what version of heartbeat are you
using?
Oops, yes that was an old version, but that doesn't make a difference
concerning the oids.
Doug Knight wrote:
I think I ran into this exact issue. I was calling crm_master -v 100 to
upgrade to master status too frequently. The postgres database needs to
stay in master state once its there, and not transition frequently. Are
there any other command line tools that could be used to
Dave Blaschke wrote:
Peter Kruse wrote:
Hi Dave,
Dave Blaschke wrote:
I cannot find the Config info syntax: message in the latest or any
of the most recent 2.0.x code - what version of heartbeat are you
using?
Oops, yes that was an old version, but that doesn't make a difference
