Mailing list and website availability

Hi All,

I will be migrating the clusterlabs.org server to openSUSE11.1 either  
today or some time later this week.  Until this is complete, there may  
be some periods of downtime for the website and mailing lists.

Your patience and understanding is appreciated 

Andrew

Ignore: Mailman server test

Ignore this, it is merely to check if mailman is functioning correctly
again

Andrew

Re: unpack_rsc_op: Hard error - Preventing from re-starting

On Wed, Dec 24, 2008 at 12:45, Raoul Bhatia [IPAX] <r.bhatia@...> wrote:
> hi,
>
> how do i force a restart of a resource in a hard-error state:
>> unpack_rsc_op: Hard error - mysql-server_start_0 failed with rc=4: Preventing mysql-server from
re-starting on wc02

you need to clean out the error with crm_resource -C

or in 1.0 you can have it time out

>
> background information: changes to the mysql ra made the monitor
> operation fail. i fixed the issue and want to restart mysql-server
> without restarting heartbeat on that node.
>
> cheers,
> raoul
> --
> ____________________________________________________________________
> DI (FH) Raoul Bhatia M.Sc.          email.          r.bhatia@...
> Technischer Leiter
>
> IPAX - Aloy Bhatia Hava OEG         web.          http://www.ipax.at
> Barawitzkagasse 10/2/2/11           email.            office@...
> 1190 Wien                           tel.               +43 1 3670030
> FN 277995t HG Wien                  fax.            +43 1 3670030 15
> ____________________________________________________________________
>
> _______________________________________________

Re: Pacemaker 1.0.2rc debian bulds (was: Re: Happy Holidays)

On Wed, Dec 24, 2008 at 15:08, Raoul Bhatia [IPAX] <r.bhatia@...> wrote:
> Andrew Beekhof wrote:
>> You're probably better off just rolling your own.
>>
>>   http://www.clusterlabs.org/mw/Install#Debian_Builds
>
> that's what i already did. i had to patch some files inside the
> debian directory thou. i *think* it is only related to openais and
> therefore not relevant to a heartbeat backed setup.

Did you have openais installed?
The debian directory that comes with pacemaker assumes it is.

I'd welcome any patch that made it optional 

>
> nevertheless, please use with care!
>
> another thing i noticed. both heartbeat 2.99.2 and pacemaker do not
> specify autoconf/automake as well as mercurial as their build
> requirements. i guess that this is the case because i am building
> a snapshot coming directly from the source repository, right?
>
> cheers,
> raoul
> --
> ____________________________________________________________________
> DI (FH) Raoul Bhatia M.Sc.          email.          r.bhatia@...
> Technischer Leiter
>

Re: check_action_definition: Parameters to stonith_rackpdu:0_start_0 on ... changed

On Fri, Dec 5, 2008 at 19:55, Raoul Bhatia [IPAX] <r.bhatia@...> wrote:
> Raoul Bhatia [IPAX] wrote:
>> what does this tell me?
>>
>>> crm_verify[10183]: 2008/12/05_19:40:28 WARN: check_action_definition: Parameters to
stonith_rackpdu:0_start_0 on wc01 changed: recorded c3ac995d0635bdd6516b948af0dc9176 vs.
a7d889e947eddfa525c0e195cc52ad66 (all:3.0) 0:0;169:8:0:ff82b9d0-ac0d-4dae-98d5-c97daaa4c099
>>> crm_verify[10183]: 2008/12/05_19:40:28 WARN: check_action_definition: Parameters to
stonith_rackpdu:1_start_0 on wc02 changed: recorded c3ac995d0635bdd6516b948af0dc9176 vs.
a7d889e947eddfa525c0e195cc52ad66 (all:3.0) 0:0;172:8:0:ff82b9d0-ac0d-4dae-98d5-c97daaa4c099

it claims that the definition of the resource or action changed.

usually this is caused by setting/changing target-role as a regular
attribute rather than a meta option
are you sure it was supplied?  if so, can you create a bug pls?

>
> i found some more information in the logfiles and decided to create an
> hb_report for that.
>
> the odd thing is that it only showed after i tried to stop a resource:
>> crm_resource -r pure-ftpd -v 'Stopped' --meta -p target-role
>
> i created two hb_reports. the first one (less information) is attached.
>
> the longer one (since 14:00) can be found under [1].
>
> cheers,
> raoul

Pacemaker does not start.

Hi,

I was going to examine latest Pacemaker.(Pacemaker-1-0-25502fb8c98d.tar.gz)

However, an error is given during start, and Pacemaker does not start.

I attach a result of hb_report.

Regards,

Hideo Yamauchi.

_______________________________________________
Pacemaker mailing list
Pacemaker@...
http://list.clusterlabs.org/mailman/listinfo/pacemaker

When STONITH is not completed, a resource starts.

Hi,

About movement of STONITH, I tested it.
(heartbeat 2.99.2 + Pacemaker-1-0-6fd0eebd186e.tar.gz on RHEL5.2(i386VM))

When what I confirmed carries out STONITH from a DC node and a non-DC node.

I confirmed it in the next flow.

1)I make it the state that a resource starts in a standby node.
2)I change it so that a stop error occurs in a dummy resource.
3)I generate the monitor error of the dummy resource in a standby node.
4)After a stop error, STONITH is carried out by a partner node.
5)Keep STONITH from a standby node waiting.
6)While STONITH is not completed, I reboot a standby node.

I watched log. 
Though STONITH from a DC node does not succeed, a resource is started.
When STONITH did not succeed, the resource was not started at a non-DC node.

---------------------------------------------------------------------------
Jan 13 16:01:25 ais-1 crmd: [6003]: info: send_rsc_command: Initiating action 7: start
prmDummy1_start_0 on ais-1
---------------------------------------------------------------------------

When STONITH did not succeed, I thought that the resource did not start.
Does not the behavior when STONITH failed from a DC node have a problem?

I attach a result of hb_report.
 - stonith_exec_dc.tar.gz (A result when STONITH was carried out by a DC node(ais-1))

Re: When STONITH is not completed, a resource starts.

On Jan 14, 2009, at 2:52 AM, <renayama19661014@...>
<renayama19661014@... 
 > wrote:

> Hi,
>
> About movement of STONITH, I tested it.
> (heartbeat 2.99.2 + Pacemaker-1-0-6fd0eebd186e.tar.gz on  
> RHEL5.2(i386VM))
>
> When what I confirmed carries out STONITH from a DC node and a non- 
> DC node.
>
> I confirmed it in the next flow.
>
> 1)I make it the state that a resource starts in a standby node.
> 2)I change it so that a stop error occurs in a dummy resource.
> 3)I generate the monitor error of the dummy resource in a standby  
> node.
> 4)After a stop error, STONITH is carried out by a partner node.
> 5)Keep STONITH from a standby node waiting.
> 6)While STONITH is not completed, I reboot a standby node.

Is this in a two-node cluster?

> I watched log.

>
> Though STONITH from a DC node does not succeed, a resource is started.

Re: Pacemaker does not start.

Nod, I broke it while fixing some coverity errors - should be fixed now.

Sorry.

On Jan 14, 2009, at 2:08 AM, <renayama19661014@...>
<renayama19661014@... 
 > wrote:

> Hi,
>
> I was going to examine latest Pacemaker. 
> (Pacemaker-1-0-25502fb8c98d.tar.gz)
>
> However, an error is given during start, and Pacemaker does not start.
>
> I attach a result of hb_report.
>
> Regards,
>
> Hideo Yamauchi.
> < 
> cannot_start_report 
> .tar.gz>_______________________________________________
> Pacemaker mailing list
> Pacemaker@...
> http://list.clusterlabs.org/mailman/listinfo/pacemaker

Re: Pacemaker does not start.

Hi,

All right.

Thank you.

Hideo Yamauchi.

--- Andrew Beekhof <beekhof@...> wrote:

> Nod, I broke it while fixing some coverity errors - should be fixed now.
> 
> Sorry.
> 
> On Jan 14, 2009, at 2:08 AM, <renayama19661014@...>
<renayama19661014@... 
>  > wrote:
> 
> > Hi,
> >
> > I was going to examine latest Pacemaker. 
> > (Pacemaker-1-0-25502fb8c98d.tar.gz)
> >
> > However, an error is given during start, and Pacemaker does not start.
> >
> > I attach a result of hb_report.
> >
> > Regards,
> >
> > Hideo Yamauchi.