From owner-freebsd-proliant@FreeBSD.ORG Tue Feb 7 10:13:13 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 893CB16A420 for ; Tue, 7 Feb 2006 10:13:13 +0000 (GMT) (envelope-from greg@wholemeal.net) Received: from warprecords.com (dsl-212-135-210-82.dsl.easynet.co.uk [212.135.210.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id B110843D49 for ; Tue, 7 Feb 2006 10:13:11 +0000 (GMT) (envelope-from greg@wholemeal.net) Received: from [192.168.100.33] (HELO [192.168.0.2]) by warprecords.com (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5916477; Tue, 07 Feb 2006 10:13:10 +0000 In-Reply-To: <43E7E27E.9060501@henriklidstrom.se> References: <43E7E27E.9060501@henriklidstrom.se> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <214C059F-21D7-4827-801A-BD823D9F7CF7@wholemeal.net> Content-Transfer-Encoding: quoted-printable From: Greg Eden Date: Tue, 7 Feb 2006 10:13:10 +0000 To: =?ISO-8859-1?Q?Henrik_Lidstr=F6m?= X-Mailer: Apple Mail (2.746.2) Cc: freebsd-proliant@freebsd.org Subject: Re: hpasmcli locks up a DL380G3 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 10:13:13 -0000 On 6 Feb 2006, at 23:57, Henrik Lidstr=F6m wrote: >> >> Hello >> >> First of all many thanks for the port of these tools to FreeBSD, =20 >> something I'd dreamt about for a long time. The lack of RAID =20 >> management tools for FreeBSD on DLxxx hardware was quite =20 >> crippling. OK, they have been removed but at least I know they =20 >> are actively being worked on. >> >> Sadly though I've been experiencing problems with the hpasmcli =20 >> utility on a number of machines, which today culminated in the =20 >> locking up of a production webserver. I was taking what seem to be =20= >> a small risk running it in that environment but initial tests had =20= >> shown it to be quite stable. >> >> The box that locked up was a DL380G3 which reports as below, =20 >> running FreebSD 5.3R-p5 >> >> System : ProLiant DL380 G3 >> Serial No. : xxxxxxxxxxxx >> ROM version : P29 05/01/2004 >> iLo present : Yes >> Embedded NICs : 2 >> NIC1 MAC: xxxxxxxxxxxxxxxxxx >> NIC2 MAC: xxxxxxxxxxxxxxxxxx >> >> Processor: 0 >> Name : Intel Xeon >> Stepping : 9 >> Speed : 2800 MHz >> Bus : 400 MHz >> Socket : 1 >> Level2 Cache : 512 KBytes >> Status : Ok >> >> Processor total : 1 >> >> Memory installed : 1024 MBytes >> ECC supported : Yes >> >> What appears to happen is thus: >> >> 1. For a period of days or weeks the hpasmcli and hpasmd work just =20= >> fine. >> 2. After some period of time, in the order of weeks, when hpasmcli =20= >> is run it will just print: >> >> HP management CLI for FreeBSD (v7.22) >> Copyright 2003,2005 Hewlett-Packard Development Group, L.P. >> >> ---------------------------------------------------------------------=20= >> --- -- >> NOTE: Some hpasmcli commands may not be supported on all Proliant =20= >> servers. >> Type 'help' to get a list of all top level commands. >> ---------------------------------------------------------------------=20= >> --- -- >> >> and then hang, without showing the hpasmcli> prompt for input. In =20 >> the past it's been possible to Ctrl-C break out. Restarting the =20 >> hpasmd daemon will see hpasmcli working fine again. Given the =20 >> usefulness of the utility I've been willing to live with that. =20 >> However today running hpasmcli seems to have instantly locked the =20= >> box, both at the console and via ssh. I've been using hpasmcli =20 >> since it's public release. >> >> The other HP boxes I have include two DL360G4s with FreeBSD 5.4-=20 >> p1 and a DL360G3 with FreeBSD 5.3-p4 . They have shown the =20 >> hpasmcli hanging behaviour, but never locked up hard. >> >> Unfortunately all the HP boxes I have are currently in production =20 >> and I can't run any further diagnostics, traces etc. >> >> Has anyone else seen this behaviour? Is a fix likely? >> >> best wishes >> >> greg. >> > > Hi! > > Sorry for being late on this one, found this browsing around. > > Yes, I have had ONE machine lock up on me once. > And older HP Proliant DL380G1 UP. Just as you describe, it had been =20= > working great for > a couple of weeks, then suddenly when starting hpasmcli it froze. > Couldn't even ping the machine. > > This particualar machine really is not doing anything, and as I belive > it still is running (Moved/changed job) and I could probably =20 > recreate the lockup. > I still have access to this machine, so if anyone want me to try =20 > something, I can do it. > The machine is 600km away from me now, so if lockup occurs it can =20 > take some time to get it > powercycled though. > > Oh, 5.3 or 5.4 as I recall. > > Have you seen any other lockup Greg? I haven't tempted fate that way yet. I always restart the hpasmd =20 before using the client on a machine. This seems to avoid the problem. Thanks for responding to my mail, you're the third person to confirm =20 the problem, which given that it locks the machine up hard, is a very =20= serious one. best. greg.=