Donnerstag, 19. April 2012 14:36
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] OCF Resource agent monitor activity failed due to
temporary error
On 04/19/2012 01:59 PM, Kulovits Christian - OS ITSC wrote:
> Hi Andreas,
> Exactly this is what i want pacemaker to do when my RA i
r
Hi Christian,
On 04/19/2012 01:38 PM, Kulovits Christian - OS ITSC wrote:
> Hi, Andreas
>
> What if the RA gets a response from an external command in the form: "display
> currently unavailable, try later". The RA has 3 possibly states available,
> "Running&quo
way to deal with that problem is to fix the RA ... patches
are always welcome ;-)
Regards,
Andreas
--
Need help with Pacemaker?
http://www.hastexo.com/now
>
> Il giorno 19 aprile 2012 11:29, Kulovits Christian - OS ITSC
> <mailto:christian.kulov...@austrian.com>> ha
Hi,
During a monitor activity for a SRDF Resource a temporary error occurred and
the resource agent cannot determine the state of the resource and returned
OCF_ERR_GENERIC. The cluster restarted the resource and all depending resources
as designed. Is there a way to say that this failed monitor
with message AttributeError: 'NoneType'
object has no attribute 'values'
On 2011-10-13 09:56, Kulovits Christian - OS ITSC wrote:
> Hello,
>
> I tried to do an edit xml within crm and after a vi :wq the crm shell is
> terminated with the following messages. The shad
Hello,
I tried to do an edit xml within crm and after a vi :wq the crm shell is
terminated with the following messages. The shadow cib is an unchanged copy of
the active cib.
shadow[HubNew] # crm
crm(HubNew)# options sort-elements no
crm(HubNew)# configure
crm(HubNew)configure# edit xml
Traceb
Hi Rasto
Both DRBD Console 9.9 and LCMC 1.0 have the same problem, there is only a tab
for the last connected Cluster. The others connected Clusters can only be
selected for disconnect from the main menu.
Regards, Christian
-Original Message-
From: Rasto Levrinc [mailto:rasto.levr...
collocation
On Fri, Jul 1, 2011 at 7:23 PM, Kulovits Christian - OS ITSC
mailto:christian.kulov...@austrian.com>> wrote:
Hello Andrew,
No, there are no ordering constraint between the groups!
Then how is pacemaker supposed to know there is a start/stop order that should
be observed?
R
collocation
On Tue, May 31, 2011 at 10:05 PM, Kulovits Christian - OS ITSC
mailto:christian.kulov...@austrian.com>> wrote:
Hello,
In a 2-node cluster two groups (prod, test) are defined with a collocation
score="-INFINITY". When the node running the group prod failed, the te
Subject: Re: [Pacemaker] IPC Channel is not connected
On Mon, Jun 27, 2011 at 02:27:52PM +0200, Kulovits Christian - OS ITSC wrote:
> Hi
> This message is written every 10 seconds on one node of a 4 node cluster. No
> testing in progress, no fencing device defined.
Let me do a wild gu
, Jun 27, 2011 at 08:17:38AM -0400, imnotpc wrote:
> On Monday, June 27, 2011 08:08:46 Dejan Muhamedagic wrote:
> > Hi,
> >
> > On Mon, Jun 27, 2011 at 10:42:46AM +0200, Kulovits Christian - OS
> > ITSC
> wrote:
> > > Hello
> > >
> > >
: Re: [Pacemaker] IPC Channel is not connected
On Monday, June 27, 2011 08:08:46 Dejan Muhamedagic wrote:
> Hi,
>
> On Mon, Jun 27, 2011 at 10:42:46AM +0200, Kulovits Christian - OS ITSC
wrote:
> > Hello
> >
> > In the corosync log file i can find many lines like thi
Hello
In the corosync log file i can find many lines like this:
Jun 27 10:38:41 amosn3 cib: [1842]: WARN: send_ipc_message: IPC Channel to 414
is not connected
Any idea what this means?
Mit freundlichen Grüßen / with best regards
Christian Kulovits
: Re: [Pacemaker] Resource Agent timeout
Hi,
On Mon, Jun 20, 2011 at 03:15:23PM +0200, Kulovits Christian - OS ITSC wrote:
> Andreas,
> you mean the cluster wide default timeout? I wonder if there is a possibility
> to set the fixed timeout of 5 secs when SIGKILL is issued after the SIGTER
...@linbit.com]
Sent: Montag, 20. Juni 2011 15:08
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Resource Agent timeout
On 2011-06-20 14:28, Kulovits Christian - OS ITSC wrote:
> Hello List,
>
>
>
> When a resource agent times out a SIGTERM is issued when the timeout
>
Hello List,
When a resource agent times out a SIGTERM is issued when the timeout value has
exceeded. When the resource agent will not terminate within the next 5 seconds
a SIGKILL is issued. Is there a way to set this limit? May be to 30 secs or so?
5 seconds may often be insufficient for a pr
: Mittwoch, 01. Juni 2011 10:21
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Group not started/stopped in correct order with -INF
collocation
On 2011-05-31 16:04, Kulovits Christian - OS ITSC wrote:
> Sorry!! Yes, of course
>
> Corosync Cluster Engine, version &#
on
On 2011-05-31 14:05, Kulovits Christian - OS ITSC wrote:
> Hello,
>
> In a 2-node cluster two groups (prod, test) are defined with a
> collocation score="-INFINITY". When the node running the group prod
> failed, the test group on the other node was stopped and the pro
Hello,
In a 2-node cluster two groups (prod, test) are defined with a collocation
score="-INFINITY". When the node running the group prod failed, the test group
on the other node was stopped and the prod group was started. After the failed
node was online again, the prod group was moved to the o
19 matches
Mail list logo
