X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78E75.BB85ECD7@onstor-exch02.onstor.net>; Fri, 4 May 2007 10:57:51 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: _rmc_pm_dispatch(): sess{:pm.0.0} down_ messages
Date: Fri, 4 May 2007 10:57:50 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E038CA22C@onstor-exch02.onstor.net>
In-Reply-To: <20070504103858.0373f3df@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: _rmc_pm_dispatch(): sess{:pm.0.0} down_ messages
Thread-Index: AceOcxkFiNDpAtMqQ8q5mtIWkgMwhwAAllIw
References: <BB375AF679D4A34E9CA8DFA650E2B04E038CA1A7@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02679C08@onstor-exch02.onstor.net> <20070504103858.0373f3df@ripper.onstor.net>
From: "John Keiffer" <john.keiffer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>
Cc: "May Ma" <may.ma@onstor.com>,
	"Raj Kumar" <raj.kumar@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Eric Crutchlow" <eric.crutchlow@onstor.com>


I just filed defect 19043 for this issue documented here. I'm not really
sure what other info to provide. It kind of relates to defect 18562.

The problem is that it sucks having rmc messages print to the users
screen.



-----Original Message-----
From: Andy Sharp=20
Sent: Friday, May 04, 2007 10:39 AM
To: Sandrine Boulanger
Cc: John Keiffer; May Ma; Raj Kumar; Tim Gardner; Brian DeForest; Eric
Crutchlow
Subject: Re: _rmc_pm_dispatch(): sess{:pm.0.0} down_ messages

There are two bugs going on here, one, if pm is down, and two, this
dang message should not be coming out like spam all over the place.  If
someone can file a defect against #2 that would be a help, so we can
task someone to fix at the very least this annoying behavior.

I don't know if elogging works if pm is down, but it's my opinion that
this message should be relegated to elog, not on the user's terminal.

Perhaps there already is a defect filed on this, but I couldn't find it
with my meager CQ skills.  If so make it a P2.

Cheers,

a

On Fri, 4 May 2007 10:31:03 -0700 "Sandrine Boulanger"
<sandrine.boulanger@onstor.com> wrote:

> Pm never restart if it dies. You should do ps ax | grep pm to see if
> it's running and check for pm core in /var/run. Pm cores defects are
> still opened in CQ, we have usually 2 kind of stack trace
>=20
> =20
>=20
> ________________________________
>=20
> From: John Keiffer=20
> Sent: Friday, May 04, 2007 10:06 AM
> To: Sandrine Boulanger
> Cc: May Ma; Raj Kumar; Andy Sharp
> Subject:=20
>=20
> =20
>=20
> Sandrine,
>=20
> =20
>=20
> I retested "system copy all" to a new flash install. Everything seemed
> to work okay. As I scrolled back through the output I did notice just
> a few of these messages: rmc_pm_dispatch(): sess{:pm.0.0} down. There
> were only a few though this time, and I can't tell if pm went down
> and came back up or not. Below is the section from the elog as far as
> I can tell. Any problem in there? Also, I searched for "pm" in CQ,
> and I can't tell if we have those system command pm crashes entered...
>=20
> =20
>=20
> May  4 09:35:48 eng93 : 0:0:sscccc:INFO: bad read, bytes=3D-1 (client =
1
> socket 13)
>=20
> May  4 09:35:48 eng93 : 0:0:sscccc:NOTICE: closing session for client
> 1
>=20
> May  4 09:38:26 eng93 : 0:0:asd:ERROR: asd_main: Lost connection to
> eventd. Reinitializing conn
>=20
> May  4 09:38:26 eng93 : 0:0:eventd:INFO: close_session: Lost
> connection. Close rmc session 0x1008fc00 for event session 0x1008b608
> app unused 0.
>=20
> May  4 09:38:26 eng93 : 0:0:asd:NOTICE: asd_main: Connected to eventd
>=20
> May  4 09:38:26 eng93 : 0:0:cluster2:INFO: cluster_clientSendRmcRpc:
> Error sending rpc to clusterrpc, flags 820a, name snmpd, rc -20,
> retrying...
>=20
> May  4 09:38:40 eng93 : 0:0:cluster2:INFO: cluster_clientSendRmcRpc:
> Error sending rpc to cluster2, flags 820a, name spm, rc -20,
> retrying...
>=20
> May  4 09:38:46 eng93 : 0:0:tape-driver:ERROR: tape_rpc: rmc_rpc app
> sdm cpu 0 slot 0 failed - -19
>=20
> May  4 09:38:53 eng93 : 0:0:cluster2:INFO: cluster_clientSendRmcRpc:
> Error sending rpc to cluster2, flags 820a, name vsd, rc -20,
> retrying...
>=20
> May  4 09:38:53 eng93 : 0:0:cluster2:INFO: cluster_clientSendRmcRpc:
> Error sending rpc to clusterrpc, flags 820a, name vsd, rc -3,
> retrying...
>=20
> May  4 09:39:34 eng93 : 0:0:sscccc:NOTICE: New client 0: addr
> 10.0.0.107, port 3574; Assigning fd(12)
>=20
> May  4 09:40:25 eng93 : 0:0:ea:INFO: ea_rcvRmcMsg : RMC send not
> successful (-20) on ncm sess
>=20
> May  4 09:40:30 eng93 : 0:0:ea:NOTICE: ea_closeSess : NCM session
> closed
>=20
> May  4 09:40:30 eng93 : 0:0:ea:NOTICE: ea_rcvRmcMsg : NCM session open
> success
>=20
> May  4 09:40:30 eng93 : 0:0:ea:INFO: Error string (Operation failed.
> Request processing aborted.) len (45)
>=20
> =20
>=20
> =20
>=20
> Thank you,
>=20
> John Keiffer
>=20
> =20
>=20
> =20
>=20
