[Pacemaker] IPC Channel is not connected

Kulovits Christian - OS ITSC Christian.Kulovits at austrian.com
Mon Jun 27 10:58:00 EDT 2011


Hi Lars,
Thank you for your answer. Yes I am using DRBD MC. And yes, if I close the MC the message is not written any more. Thank You.
Christian

-----Original Message-----
From: Lars Ellenberg [mailto:lars.ellenberg at linbit.com] 
Sent: Montag, 27. Juni 2011 16:26
To: pacemaker at oss.clusterlabs.org
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 guess:

You are using DRBD MC.
This message is a side effect of "nothing happens", and DRBD MC probing for "cib still alive?":
it just does a connect to the cib,
but then closes the socket right away, so the "welcome new client, what can I do for you" message triggers that warning: client connection was disconnected even before the welcome message could be delivered.

Which, btw, is fixed in current DRBD MC development, and will of course be released with the next update.

This message triggers, whenever an ipc message is queued, but then can not be delivered because the client connection was closed "unexpectedly".

If it was closed "expectedly", no further ipc messages are queued.
If it was closed "unexpectedly", but between that, and noticing it, no further ipc message is queued, the message does not trigger either.

It can safely be ignored, and only annoyingly fills up the log files.

Hth,
	

> Christian
> 
> -----Original Message-----
> From: imnotpc [mailto:imnotpc at rock3d.net]
> Sent: Montag, 27. Juni 2011 14:18
> To: The Pacemaker cluster resource manager
> Subject: 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 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?
> > 
> > Probably the other process crashed.
> 
> Are these normal warnings when testing fencing, etc?
> 
> Jeff
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org 
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org Getting started: 
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: 
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacema
> ker
> 
> ________________________________________________
> Austrian Airlines AG, Office Park 2, P.O. Box 100, 1300 Vienna-Airport, Austria, registered office: Vienna, registered with Vienna Commercial Court under FN 111000k, DVR 0091740. This e-mail is confidential and is subject to disclaimers. Details can be found at: http://www.austrian.com/disclaimer.
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org 
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org Getting started: 
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: 
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacema
> ker

--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

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

Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker




More information about the Pacemaker mailing list