panic: pipeinit: cannot allocate pipe -- out of kvm --
James Ponder
We have an OpenBSD 2.3-something machine that panics with the message:
pipeinit: cannot allocate pipe -- out of kvm -- code = 3
It dies in this way at least twice a day, ever since we increased
kern.maxfiles to 4096 instead of 1774 or so, which the was the default for
our kernel.
Before we increased kern.maxfiles, the kernel used to log to syslog
'file: table is full' (or suchlike), and die slowly. The reason this happens
is that we increased the number of tables and connections mysql is allowed
to consume, and the reason we did this was because mysql started refusing
connections due to the heavy use of our server.
We also get the line:
vm_map_entry_create: allocated 73 new entries.
Logged every now and again, is this good or bad?
We've had vmstat running whilst the machine panics, the last line logged
was:
procs memory page disks faults cpu
r b w avm fre flt re pi po fr sr w0 w1 f0 in sy cs us sy id
114 0893144 57160 1101 136 40 0 0 0 4 3 0 331 1899 187 10 42 48
It doesn't seem to indicate anything out of the ordinary there.
Any help would be appreciated. Perhaps we're experiencing a bug that has
been fixed betwee 2.3 and 2.6, or we're hitting some resource limit?
Best wishes, James
-*- James Ponder -*- ja...@oaktree.co.uk -*- http://www.oaktree.co.uk/ -*-
Oaktree Internet Solutions Ltd. is part of the IS4B Inc. group (NASDAQ:ISFB)
Internet Solutions for Business, Internet House, Canal Basin, Coventry CV1 4LY
Artur Grabowski
> Hi,
>
> We have an OpenBSD 2.3-something machine that panics with the message:
>
> pipeinit: cannot allocate pipe -- out of kvm -- code = 3
>
> It dies in this way at least twice a day, ever since we increased
> kern.maxfiles to 4096 instead of 1774 or so, which the was the default for
> our kernel.
>
> Before we increased kern.maxfiles, the kernel used to log to syslog
> 'file: table is full' (or suchlike), and die slowly. The reason this happens
> is that we increased the number of tables and connections mysql is allowed
> to consume, and the reason we did this was because mysql started refusing
> connections due to the heavy use of our server.
Too many pipes in the system.
If this is an i386, it will help to upgrade to 2.6 (you'll be able to create
twice as many pipes at least). But this sounds like bad designed software.
You are not supposed to have that many pipes. I had to create thousands of
pipes to force this panic.
//art
Hannah Schroeter
On Wed, Feb 16, 2000 at 05:56:26PM +0100, Artur Grabowski wrote:
> [...]
> You are not supposed to have that many pipes. I had to create thousands of
> pipes to force this panic.
That means, a non-root malicous user can panic the system?
Surely a bug...
Regards, Hannah.
David Leonard
> > You are not supposed to have that many pipes. I had to create thousands of
> > pipes to force this panic.
>
> That means, a non-root malicous user can panic the system?
> Surely a bug...
i just tried this on i386, and got EMFILE: Too many open files in system.
About 1800 pipe ends were opened, but no panic. What's the trick?
d
--
David Leonard David....@csee.uq.edu.au
Dept of Comp. Sci. and Elec. Engg _ Room:78-624 Ph:+61 7 336 52447
The University of Queensland |+| http://www.csee.uq.edu.au/~leonard/
QLD 4072 AUSTRALIA ~` '~ E2A24DC6446E5779D7AFC41AA04E6401
The Stick: Second most useful thing ever. -- DNA