Any update on this ?
On Sat, Jul 12, 2014 at 11:55 PM, K Mehta wrote:
> Andrew,
> Attached is the report.
>
> Regards,
> Kiran
>
>
> On Fri, Jul 11, 2014 at 4:26 AM, Andrew Beekhof
> wrote:
>
>> Can you run crm_report for the period covered by your test and attach the
>> result please?
>>
>
Dear all,
The problem is solved.
Teenigma
On Tue, Jul 15, 2014 at 1:53 PM, Teerapatr Kittiratanachai
wrote:
> Dear Honza,
>
> Sorry to say this, but I found new error again. LOL
>
> This time, I already install the 1.4.1-17 as your advice.
> And the nodename, without altname, is map to IPv6 usi
On Mon, Jul 14, 2014, at 02:07, Andrew Beekhof wrote:
>
> On 10 Jul 2014, at 11:17 am, Giuseppe Ragusa
> wrote:
>
> > On Thu, Jul 10, 2014, at 00:06, Andrew Beekhof wrote:
> >>
> >> On 9 Jul 2014, at 10:28 pm, Giuseppe Ragusa
> >> wrote:
> >>
> >>> On Tue, Jul 8, 2014, at 02:59, Andrew Beek
Hello Lars,
I was just trying in my virtual lab.
Thanks anyway
2014-07-15 20:48 GMT+02:00 Lars Marowsky-Bree :
> On 2014-07-15T14:03:00, emmanuel segura wrote:
>
>> Thanks Lars for you answer,
>>
>> I was using crm_resource, because using crmsh i can't start a resource
>> on a specific node.
>
On 07/15/2014 02:31 PM, Andrew Daugherity wrote:
Message: 1
Date: Sat, 12 Jul 2014 09:42:57 -0400
From: Ken Gaillot
To: pacemaker@oss.clusterlabs.org
Subject: [Pacemaker] Occasional nonsensical resource agent errors
since Debian 3.2.57-3+deb7u1 kernel update
Hi,
We run multiple deploym
On 2014-07-15T14:03:00, emmanuel segura wrote:
> Thanks Lars for you answer,
>
> I was using crm_resource, because using crmsh i can't start a resource
> on a specific node.
crm_resource can't do that either directly; you need to do this in two
steps, moving a resource to a node and then starti
> Message: 1
> Date: Sat, 12 Jul 2014 09:42:57 -0400
> From: Ken Gaillot
> To: pacemaker@oss.clusterlabs.org
> Subject: [Pacemaker] Occasional nonsensical resource agent errors
> since Debian 3.2.57-3+deb7u1 kernel update
> Message-ID: <53c13b61.7080...@gleim.com>
> Content-Type: text/plain;
Hi,
On 15.07.2014 14:03, emmanuel segura wrote:
> I was using crm_resource, because using crmsh i can't start a resource
> on a specific node.
>
> example:
>
> crm(live)resource# start Dummy2 node02
> usage: start
You can "move" a stopped resource, then start it:
crm resource move Dummy2 nod
Thanks Lars for you answer,
I was using crm_resource, because using crmsh i can't start a resource
on a specific node.
example:
crm(live)resource# start Dummy2 node02
usage: start
2014-07-15 12:59 GMT+02:00 Lars Marowsky-Bree :
> On 2014-07-15T12:44:49, emmanuel segura wrote:
>
>> Hello Lar
On 2014-07-15T12:44:49, emmanuel segura wrote:
> Hello Lars,
>
> I saw the same problem on suse 11, this is the example command i found
> in the man page for stop a resource
>
> man crm_resource
> Start or stop a resource:
Please use the crm shell to start/stop resources.
crm res
Hello Lars,
I saw the same problem on suse 11, this is the example command i found
in the man page for stop a resource
man crm_resource
Start or stop a resource:
crm_resource -r my_first_ip -p target_role -v stopped
::
On Tue, Jul 15, 2014 at 3:36 PM, Andrew Beekhof wrote:
>
> On 15 Jul 2014, at 8:00 pm, Arjun Pandey wrote:
>
>> Right. Actually the issue i am facing is that i am starting the
>> pacemaker service remotely from a wrapper and thus pacemakerd dies
>> when the wrapper exits.nohup solves the problem
On 15 Jul 2014, at 8:00 pm, Arjun Pandey wrote:
> Right. Actually the issue i am facing is that i am starting the
> pacemaker service remotely from a wrapper and thus pacemakerd dies
> when the wrapper exits.nohup solves the problem but then HUP cannot be
> used by pacemaker. Is this workaround
Right. Actually the issue i am facing is that i am starting the
pacemaker service remotely from a wrapper and thus pacemakerd dies
when the wrapper exits.nohup solves the problem but then HUP cannot be
used by pacemaker. Is this workaround ok ?
I was checking out the current pacemaker code.setsid
On 15 Jul 2014, at 7:13 pm, Arjun Pandey wrote:
> Hi Andrew
>
> AFAIK linux daemons don't terminate on SIGHUP.
Read the man page, POSIX specifies that the default action is 'term' ie.
'terminate'.
> They typically reload
> configuration on receiving this signal.Eg- rsyslogd. I thought it was
Hi Andrew
AFAIK linux daemons don't terminate on SIGHUP. They typically reload
configuration on receiving this signal.Eg- rsyslogd. I thought it was
safe to make this assumption here as well.
Regards
Arjun
On Tue, Jul 15, 2014 at 2:15 PM, Andrew Beekhof wrote:
>
> On 15 Jul 2014, at 6:19 pm, Ar
On 15 Jul 2014, at 6:19 pm, Arjun Pandey wrote:
> Hi all
>
> I am running pacemaker version 1.1.10-14.el6 on CentOS 6. On setting
> up cluster if I send SIGHUP to either pacemaker or corosync services ,
> they die.
> Is this a bug ? What is the intension behind this behavior?
Standard default
On 15 Jul 2014, at 6:12 pm, Lars Marowsky-Bree wrote:
> On 2014-07-15T17:04:52, Andrew Beekhof wrote:
>
>> Enjoy tinkering with clusters and have a background in software development?
>> There might be some positions working with yours truly at Red Hat soon, drop
>> me a note if you're inter
Hi all
I am running pacemaker version 1.1.10-14.el6 on CentOS 6. On setting
up cluster if I send SIGHUP to either pacemaker or corosync services ,
they die.
Is this a bug ? What is the intension behind this behavior?
Regards
Arjun
___
Pacemaker mailing
On 2014-07-15T17:04:52, Andrew Beekhof wrote:
> Enjoy tinkering with clusters and have a background in software development?
> There might be some positions working with yours truly at Red Hat soon, drop
> me a note if you're interested.
> Hitting Reply-All can and will be used against you :-)
Enjoy tinkering with clusters and have a background in software development?
There might be some positions working with yours truly at Red Hat soon, drop me
a note if you're interested.
Hitting Reply-All can and will be used against you :-)
[/Shameless plug for my employer]
-- Andrew
signat
21 matches
Mail list logo
