From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 10 06:52:20 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED3AE16A4CE; Thu, 10 Jun 2004 06:52:20 +0000 (GMT) Received: from kollerie.com (148-198.bbned.dsl.internl.net [217.149.198.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FA9A43D2F; Thu, 10 Jun 2004 06:52:20 +0000 (GMT) (envelope-from gkoller@kollerie.com) Received: by kollerie.com (Postfix, from userid 1001) id E75942F8FE; Thu, 10 Jun 2004 08:51:33 +0200 (CEST) Date: Thu, 10 Jun 2004 08:51:33 +0200 From: Guido Kollerie To: "Simon L. Nielsen" Message-ID: <20040610065133.GA14542@kollerie.com> References: <20040604085316.GA77766@kollerie.com> <20040609211940.GA829@zaphod.nitro.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20040609211940.GA829@zaphod.nitro.dk> User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org Subject: Re: raidutil: Engine connect failed: Open X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2004 06:52:21 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 09, 2004 at 11:19:40PM +0200, Simon L. Nielsen wrote: > On 2004.06.04 10:53:16 +0200, Guido Kollerie wrote: Simon, > > I have an ADAPTEC 2400A installed in my server. Every night I run > > the following job from cron: > >=20 > > /usr/local/dpt/raidutil -L all > >=20 > > and have its output emailed to me. This seemed to worked fine for > > quite a while, however last night I received the following output > > from this job: > >=20 > > Engine connect failed: Open > >=20 > > What's causing this and how can I resolve it? >=20 > Check if you are running out of SysV shared memory... I have to stop > PostgreSQL to run raidutil, since I haven't gotten around to bumping > SysV memory in my kernel. That did the trick. I happened to have installed PostgreSQL recently but never made the link with raidutil failing. Stopping PostgreSQL allows raidutil to run without any problems! Thank you very much! --=20 Guido --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iEYEARECAAYFAkDIBPUACgkQC7vo05+GQSyRlACfQO30qHqVisN3cdhGKfmQ0D/H OJkAn1+5qORcqXctGm8X0G6g/BWqXIP7 =M2Kv -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o--