On Fri, May 27, 2011 at 2:21 PM, veghead wrote:
> veghead writes:
> > Todd Nine writes:
> > Wow. The example pacemaker config and the trick of starting
> > heartbeat before
>
> crm configure < myconfigure.txt
>
I've had to use crm configure load replace properties_file
> So that leaves me w
veghead writes:
> Todd Nine writes:
> Wow. The example pacemaker config and the trick of starting
> heartbeat before
Bah. So close. But I still don't have it completely automated.
If I start heatbeat on the first node and then run:
crm configure < myconfigure.txt
That fails. If I start heart
On Fri, May 27, 2011 at 1:46 PM, Serge Dubrouski wrote:
>
>
> On Fri, May 27, 2011 at 1:39 PM, "Roman Schartlmüller" <
> roman_schartlmuel...@gmx.at> wrote:
>
>>
>> Original-Nachricht
>> > Datum: Fri, 27 May 2011 20:30:47 +0200
>> > Von: Jelle de Jong
>> > An: pacemaker@oss.clu
Todd Nine writes:
> I have a setup nearly working. Would you be willing to share recipes?
...
> It's not quite working yet, but it's close. Since you've managed to get
> this working, you may be able to finish these off. I have everything
> working except the init start/stop hooks for pacema
On Fri, May 27, 2011 at 1:39 PM, "Roman Schartlmüller" <
roman_schartlmuel...@gmx.at> wrote:
>
> Original-Nachricht
> > Datum: Fri, 27 May 2011 20:30:47 +0200
> > Von: Jelle de Jong
> > An: pacemaker@oss.clusterlabs.org
> > Betreff: Re: [Pacemaker] corosync-quorumtool configurat
Original-Nachricht
> Datum: Fri, 27 May 2011 20:30:47 +0200
> Von: Jelle de Jong
> An: pacemaker@oss.clusterlabs.org
> Betreff: Re: [Pacemaker] corosync-quorumtool configuration
> On 27-05-11 18:19, Roman Schartlmüller wrote:
> > Can anybody please help me with configuration? M
On 27-05-11 18:19, Roman Schartlmüller wrote:
> Can anybody please help me with configuration? Maybe there is something
> wrong.
Maybe lose the "no-quorum-policy=ignore" options. And a html mail with
tables really :D
Kind regards,
Jelle de Jong
___
Hi,
I have Problems with corosync-quorumtool. I have set up a cluster with 2
nodes which uses corosync.
For testing purposes, I am trying to establish a quorum to the cluster,
because I want to understand the quorum-corosync tool.
I want to tag a node with 2 votes so that it can continue o
Hi,
On Fri, May 27, 2011 at 02:15:07PM +0400, ruslan usifov wrote:
> hello
>
> How can i separate RA output from common pacemaker log output?. Now i have
You can't, unless you use syslog filtering.
Thanks,
Dejan
> follow loging conf (corosync.conf):
>
>
> logging {
> fileline: off
>
2011/5/27 项磊 :
> Hi, friends, I have a problem with Pacemaker 1.1.5.
>
> When I configure a master resource as usual, and set target-role=“Master”,
> but all instances are in slave state, no instance is promoted to master
> state.
>
> Who can tell me how to promote a instance to master?
have your
On Fri, May 27, 2011 at 05:45:51PM +0900, Kazunori INOUE wrote:
> Hi Dejan,
>
> Thanks for the advice.
> Is your advice to be done as follows?
>
> # diff cibconfig.py.ORG cibconfig.py -urN
> --- cibconfig.py.ORG 2011-04-28 12:23:55.0 +0900
> +++ cibconfig.py 2011-05-27 12:00:27.4271
hello
How can i separate RA output from common pacemaker log output?. Now i have
follow loging conf (corosync.conf):
logging {
fileline: off
function_name: on
timestamp: on
to_stderr: no
to_logfile: yes
to_syslog: no
logfile: /var/log/clust
Hi Florian,
good pointer, I asked a while ago about a RA on lxc-users but didn't get
any response.
The existing lxc RA seems to work. I had to create the
/var/run/resource-agent directory (seems to be a known bug) and insert
the powerfail line (as mentioned in the description of the RA).
I will
Hi Dejan,
Thanks for the advice.
Is your advice to be done as follows?
# diff cibconfig.py.ORG cibconfig.py -urN
--- cibconfig.py.ORG2011-04-28 12:23:55.0 +0900
+++ cibconfig.py2011-05-27 12:00:27.427168202 +0900
@@ -1514,6 +1514,16 @@
def import_cib(self):
'Par
Hi, friends, I have a problem with Pacemaker 1.1.5.When I configure a master
resource as usual, and set target-role=“Master”, but all instances are in slave
state, no instance is promoted to master state.Who can tell me how to promote a
instance to master?I guess it is a change in version 1.1.5
Hi, friends, I have a problem with
Pacemaker 1.1.5.
When I configure a master resource as
usual, and set target-role=“Master”, but all instances are in slave state, no
instance is promoted to master state.
Who can tell me how to promote a instance
to master?
I guess it is a change in version 1
16 matches
Mail list logo