Re: [cobalt-users] RaQ2 went down.

[Mat Kovach <mkovach@xxxxxxxxxxxxxxxxx>]

On Fri, May 19, 2000 at 09:15:27AM -0600, Michael Combe wrote:
: Ouch!  malloc failed in malloc_block()

Hmm, it attempted to allocate memory and could not.  The is not a good 
sign and does indicate a problem with memory.  This means a few things:

o Bad memory
o Bad swap (which is used as memory)
o Badly behaving program (which, generally apache is not)
o Another program is getting up memory
 
: [notice] httpd: child pid 16014 exit signal Bus error (10)

The are releated, since apache attempted to allocate memory and could not.
You see the result, it had an error.  Bus errors generally refer to a
bad read of some type. (generally).
 
You would have to check and see what program may have caused the problem.
You may want to look in the log for error concerning memory and/or bad
disk sectors.

Also, do you have any cgi's or such running on the machine, was the 
traffic high during the period leading up to the error?

If there is not a problem with the hardware, this tends to be a problem
with a cgi script (or additional program on the Raq2) running a muck
and eatting up memory.

I personally have never seen a Raq do this.

Hope that info helps.

-- 
Mat Kovach                                      mkovach@xxxxxxxxxxxxxxxxx
Cleveland Linux User Group                       http://cleveland.lug.net