Date: Sun, 13 Jun 2004 11:32:03 +0200 From: Guido Kollerie <gkoller@inter.nl.net> To: "Simon L. Nielsen" <simon@FreeBSD.org> Cc: freebsd-scsi@freebsd.org Subject: Re: raidutil: Engine connect failed: Open Message-ID: <20040613093203.GA621@kollerie.com> In-Reply-To: <20040610065133.GA14542@kollerie.com> References: <20040604085316.GA77766@kollerie.com> <20040609211940.GA829@zaphod.nitro.dk> <20040610065133.GA14542@kollerie.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jun 10, 2004 at 08:51:33AM +0200, Guido Kollerie wrote:
Simon,
> > 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.
>=20
> 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!
And indeed, while upgrading to FreeBSD 4.10, I configured
SysV shared memory according to:
http://developer.postgresql.org/docs/postgres/kernel-resources.html
which boils down to adding the following options or modify them
in the kernel config to:
options SYSVSHM
options SHMMAXPGS=3D4096
options SHMSEG=3D256
options SYSVSEM
options SEMMNI=3D256
options SEMMNS=3D512
options SEMMNU=3D256
options SEMMAP=3D256
Now I can run PostgreSQL and raidutil simultaneously.
--=20
Guido
--PEIAKu/WMn1b1Hv9
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iEYEARECAAYFAkDMHxMACgkQC7vo05+GQSy73QCeLsEpir+NY504GqMveITaslXP
nEsAnR5tB/cqABL4/C3UV7l8sqrqvAL+
=F0Gv
-----END PGP SIGNATURE-----
--PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040613093203.GA621>