You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by je...@apache.org on 2002/02/26 09:37:57 UTC

Re: os-bsdi/9940: Apache 2.0 crashes

[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: Apache 2.0 crashes

Comment-Added-By: jerenkrantz
Comment-Added-When: Tue Feb 26 00:37:57 PST 2002
Comment-Added:
I'm not at all sure what problem you are seeing here?

What's your ulimit set at?  Have you tried increasing it?


Re: os-bsdi/9940: Apache 2.0 crashes

Posted by Aaron Bannert <aa...@clove.org>.
On Tue, Feb 26, 2002 at 10:59:10PM -0700, System Administrator a.k.a. The Root of the Problem wrote:
> Bad news, yese apache 2 start BUT the server panics BIG time!!
> 
> kmem_suballoc: bad status return of 1.
> panic(cpu-1): kmem_suballoc
> syncing discs ...
> 
> Not a pretty picture.

If a userspace non-root program like Apache is able to cause a kernel
panic, then you've got bigger problems than an Apache bug.

Re: os-bsdi/9940: Apache 2.0 crashes

Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Tue, Feb 26, 2002 at 10:59:10PM -0700, System Administrator a.k.a. The Root of the Problem wrote:
> On Tue, Feb 26, 2002 at 09:17:59PM -0800, Justin Erenkrantz wrote:
> > On Tue, Feb 26, 2002 at 10:12:00AM -0700, System Administrator a.k.a. The Root of the Problem wrote:
> > > > Shouldn't you have more than 64 open files available?
> > > > Try "ulimit -n 500"?
> > > > 
> > > > It sounds like we are opening all log files at startup,
> > > > which may or may not be reasonable.  -- justin
> > > > 
> > >  How is that does universally in bash?
> > 
> > You could set this in your .bash_profile.
> > 
> > But just try:
> > 
> > ulimit -n 500
> > apachectl start
> > 
> > See what it does then.  -- justin
> > 
> 
> 
> Bad news, yese apache 2 start BUT the server panics BIG time!!
> 
> kmem_suballoc: bad status return of 1.
> panic(cpu-1): kmem_suballoc
> syncing discs ...
> 
> Not a pretty picture.

I'm afraid I'm out of my depth here.  How did this cause a kernel
panic?  Is there something else going on here?  Could you try
with different ulimit values?  -- justin


Re: os-bsdi/9940: Apache 2.0 crashes

Posted by "System Administrator a.k.a. The Root of the Problem" <ro...@doctor.nl2k.ab.ca>.
On Tue, Feb 26, 2002 at 09:17:59PM -0800, Justin Erenkrantz wrote:
> On Tue, Feb 26, 2002 at 10:12:00AM -0700, System Administrator a.k.a. The Root of the Problem wrote:
> > > Shouldn't you have more than 64 open files available?
> > > Try "ulimit -n 500"?
> > > 
> > > It sounds like we are opening all log files at startup,
> > > which may or may not be reasonable.  -- justin
> > > 
> >  How is that does universally in bash?
> 
> You could set this in your .bash_profile.
> 
> But just try:
> 
> ulimit -n 500
> apachectl start
> 
> See what it does then.  -- justin
> 


Bad news, yese apache 2 start BUT the server panics BIG time!!

kmem_suballoc: bad status return of 1.
panic(cpu-1): kmem_suballoc
syncing discs ...

Not a pretty picture.

-- 
contact:
Dave Yadallee  NetKnow  The Internet Knowledge Company
root@nl2k.ab.ca	 http://www.nl2k.ab.ca
990-3244

Re: os-bsdi/9940: Apache 2.0 crashes

Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Tue, Feb 26, 2002 at 10:12:00AM -0700, System Administrator a.k.a. The Root of the Problem wrote:
> > Shouldn't you have more than 64 open files available?
> > Try "ulimit -n 500"?
> > 
> > It sounds like we are opening all log files at startup,
> > which may or may not be reasonable.  -- justin
> > 
>  How is that does universally in bash?

You could set this in your .bash_profile.

But just try:

ulimit -n 500
apachectl start

See what it does then.  -- justin


Re: os-bsdi/9940: Apache 2.0 crashes

Posted by "System Administrator a.k.a. The Root of the Problem" <ro...@doctor.nl2k.ab.ca>.
On Tue, Feb 26, 2002 at 08:48:46AM -0800, Justin Erenkrantz wrote:
> On Tue, Feb 26, 2002 at 09:37:27AM -0700, The Doctor wrote:
> > > I'm not at all sure what problem you are seeing here?
> > 
> > First off the problem that Apache 1.X start all 5000+ Virtual servers
> > without question, but apache 2.X is halting at about 256th virtual server.
> > 
> > > 
> > > What's your ulimit set at?  Have you tried increasing it?
> > > 
> > 
> > Script started on Tue Feb 26 07:48:57 2002
> > doctor.nl2k.ab.ca/~$ ulimit -a
> > core file size (blocks)     unlimited
> > data seg size (kbytes)      262144
> > file size (blocks)          unlimited
> > max locked memory (kbytes)  256026
> > max memory size (kbytes)    768076
> > open files                  64
> > pipe size (512 bytes)       2
> > stack size (kbytes)         2048
> > cpu time (seconds)          unlimited
> > max user processes          64
> > virtual memory (kbytes)     264192
> > 
> > What needs to be done to get Aapche 2.X to start?
> 
> Shouldn't you have more than 64 open files available?
> Try "ulimit -n 500"?
> 
> It sounds like we are opening all log files at startup,
> which may or may not be reasonable.  -- justin
> 
 How is that does universally in bash?

-- 
contact:
Dave Yadallee  NetKnow  The Internet Knowledge Company
root@nl2k.ab.ca	 http://www.nl2k.ab.ca
990-3244

Re: os-bsdi/9940: Apache 2.0 crashes

Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Tue, Feb 26, 2002 at 09:37:27AM -0700, The Doctor wrote:
> > I'm not at all sure what problem you are seeing here?
> 
> First off the problem that Apache 1.X start all 5000+ Virtual servers
> without question, but apache 2.X is halting at about 256th virtual server.
> 
> > 
> > What's your ulimit set at?  Have you tried increasing it?
> > 
> 
> Script started on Tue Feb 26 07:48:57 2002
> doctor.nl2k.ab.ca/~$ ulimit -a
> core file size (blocks)     unlimited
> data seg size (kbytes)      262144
> file size (blocks)          unlimited
> max locked memory (kbytes)  256026
> max memory size (kbytes)    768076
> open files                  64
> pipe size (512 bytes)       2
> stack size (kbytes)         2048
> cpu time (seconds)          unlimited
> max user processes          64
> virtual memory (kbytes)     264192
> 
> What needs to be done to get Aapche 2.X to start?

Shouldn't you have more than 64 open files available?
Try "ulimit -n 500"?

It sounds like we are opening all log files at startup,
which may or may not be reasonable.  -- justin


Re: os-bsdi/9940: Apache 2.0 crashes

Posted by The Doctor <do...@doctor.nl2k.ab.ca>.
On Tue, Feb 26, 2002 at 08:37:57AM -0000, jerenkrantz@apache.org wrote:
> [In order for any reply to be added to the PR database, you need]
> [to include <ap...@Apache.Org> in the Cc line and make sure the]
> [subject line starts with the report component and number, with ]
> [or without any 'Re:' prefixes (such as "general/1098:" or      ]
> ["Re: general/1098:").  If the subject doesn't match this       ]
> [pattern, your message will be misfiled and ignored.  The       ]
> ["apbugs" address is not added to the Cc line of messages from  ]
> [the database automatically because of the potential for mail   ]
> [loops.  If you do not include this Cc, your reply may be ig-   ]
> [nored unless you are responding to an explicit request from a  ]
> [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
> 
> 
> Synopsis: Apache 2.0 crashes
> 
> Comment-Added-By: jerenkrantz
> Comment-Added-When: Tue Feb 26 00:37:57 PST 2002
> Comment-Added:
> I'm not at all sure what problem you are seeing here?

First off the problem that Apache 1.X start all 5000+ Virtual servers
without question, but apache 2.X is halting at about 256th virtual server.

> 
> What's your ulimit set at?  Have you tried increasing it?
> 

Script started on Tue Feb 26 07:48:57 2002
doctor.nl2k.ab.ca/~$ ulimit -a
core file size (blocks)     unlimited
data seg size (kbytes)      262144
file size (blocks)          unlimited
max locked memory (kbytes)  256026
max memory size (kbytes)    768076
open files                  64
pipe size (512 bytes)       2
stack size (kbytes)         2048
cpu time (seconds)          unlimited
max user processes          64
virtual memory (kbytes)     264192

What needs to be done to get Aapche 2.X to start?

doctor.nl2k.ab.ca/~$ exit
exit

Script done on Tue Feb 26 07:49:02 2002
-- 
Member - Liberal International	On 11 Sept 2001 the WORLD was violated.
This is doctor@nl2k.ab.ca	Ici doctor@nl2k.ab.ca
Society MUST be saved! Extremists must dissolve.  
Spammer:  21st Century Version of the Elctronic Neanderthal Man

Re: os-bsdi/9940: Apache 2.0 crashes

Posted by "System Administrator a.k.a. The Root of the Problem" <ro...@doctor.nl2k.ab.ca>.
On Tue, Feb 26, 2002 at 08:37:57AM -0000, jerenkrantz@apache.org wrote:
> [In order for any reply to be added to the PR database, you need]
> [to include <ap...@Apache.Org> in the Cc line and make sure the]
> [subject line starts with the report component and number, with ]
> [or without any 'Re:' prefixes (such as "general/1098:" or      ]
> ["Re: general/1098:").  If the subject doesn't match this       ]
> [pattern, your message will be misfiled and ignored.  The       ]
> ["apbugs" address is not added to the Cc line of messages from  ]
> [the database automatically because of the potential for mail   ]
> [loops.  If you do not include this Cc, your reply may be ig-   ]
> [nored unless you are responding to an explicit request from a  ]
> [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
> 
> 
> Synopsis: Apache 2.0 crashes
> 
> Comment-Added-By: jerenkrantz
> Comment-Added-When: Tue Feb 26 00:37:57 PST 2002
> Comment-Added:
> I'm not at all sure what problem you are seeing here?
> 
> What's your ulimit set at?  Have you tried increasing it?
> 

As you were asking:


Script started on Tue Feb 26 07:48:57 2002
doctor.nl2k.ab.ca/~$ ulimit -a
core file size (blocks)     unlimited
data seg size (kbytes)      262144
file size (blocks)          unlimited
max locked memory (kbytes)  256026
max memory size (kbytes)    768076
open files                  64
pipe size (512 bytes)       2
stack size (kbytes)         2048
cpu time (seconds)          unlimited
max user processes          64
virtual memory (kbytes)     264192
doctor.nl2k.ab.ca/~$ exit
exit

Script done on Tue Feb 26 07:49:02 2002
-- 
contact:
Dave Yadallee  NetKnow  The Internet Knowledge Company
root@nl2k.ab.ca	 http://www.nl2k.ab.ca
990-3244