AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080721100337.03e7d7c7@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<glyn.bowden@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0AFF176F@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 21 Jul 2008 10:03:57 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Glyn Bowden" <glyn.bowden@onstor.com>
Subject: Re: Defect  Yes TED00024828 Nfxsh system report "rmc_pm_dispatch():
 sess{:pm.0.0} down" Sybase
Message-ID: <20080721100357.2ab6a171@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0AFF176F@onstor-exch02.onstor.net>
References: <ONSTOR-EXCH0122c1Ab00002f6b@onstor-exch01.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0AFF176F@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Quite frankly the only thing I can think of is that pm binary got
corrupted somehow.

Many of the nfxsh commands don't need pm to work.  system verify might
work without it, or system upgrade.  If you can get system verify to
work it might be worth seeing the output.

On Mon, 21 Jul 2008 09:44:40 -0700 "Glyn Bowden"
<glyn.bowden@onstor.com> wrote:

> Hi Andy,
> 
> PM failed as soon as the box was booted. It didn't crash or dump but
> simply wasn't responding. We constantly saw the rmc_pm_dispatch
> messages. System Config Reset wouldn't run because of this. In fact as
> you can imagine, nothing ran because of this. Rebooting it manually
> from root comes back to the same condition.
> 
> Glyn
> 
> 
> 
> Glyn Bowden
> Professional Services Engineer
> 
> ONStor, Inc.
> mobile: +44 7917 824 906
> glyn.bowden@onstor.com
> http://www.onstor.com
> 
> 
> EMEA Support Line
> Phone:	+44 (0) 8707 347 448
> Email:	Support@ONStor.com
> Web:	Support.ONStor.com
> 
> 
> -----Original Message-----
> From: andy.sharp@onstor.com [mailto:andy.sharp@onstor.com] 
> Sent: 21 July 2008 17:26
> To: dl-Escalation
> Cc: Andy Sharp; Xian Hong
> Subject: Defect Yes TED00024828 Nfxsh system report
> "rmc_pm_dispatch(): sess{:pm.0.0} down" Sybase
> 
> company_name: Sybase
> id: TED00024828
> Headline: Nfxsh system report "rmc_pm_dispatch(): sess{:pm.0.0} down"
> State: Opened
> Note_Entry: 
> That message comes out because pm isn't running, even when that's
> on purpose.  I could have sworn that we got rid of it, but anyway
> ignore the message for now and focus on what isn't working.  If it
> isn't rebooting after a system config reset, what happens when you do
> reboot it?
> Does pm still refuse to run?  Can you get through the initial install?
> 
> Release_Project: 3.1.1.1
> 
