RE: Apache and segfaults
> From: Felix Laate [mailto:felix@enternett.no]
> Sent: Friday, February 04, 2005 1:39 AM
>
> This morning my logwatch told me this:
>
> WARNING: Kernel Errors Present
> apache[4407]: segfault at 00000000ff7fdf7c rip 0000000055f3dd2a rsp
> 00000000ff7fdf80 error 6...: 1 Time(s)
> apache[4529]: segfault at 00000000ff7fdf7c rip 0000000055f3dd2a rsp
> 00000000ff7fdf80 error 6...: 1 Time(s)
>
> 1 Time(s): apache[4407] bad frame in 32bit signal deliver
> frame:00000000ff7fdca0 rip:55f3dd2a rsp:ff7fdf80 orax:ffffffffffffffff
> 1 Time(s): apache[4529] bad frame in 32bit signal deliver
> frame:00000000ff7fdca0 rip:55f3dd2a rsp:ff7fdf80 orax:ffffffffffffffff
>
> What does this mean? What is a segfault?
segfault is a segmentation fault. It occurs when a program tries to access
memory it is not allowed to access (either unprivlidged process or trying to
write to read-only memory). It generaly results in a core dump and the
processess being terminated.
> The apache server is still up (and never went down).
As I understand apache (I just looked at apache for the 1st time last week),
it starts multiple processes upon startup (to avoid the overhead of forking
when multiple request come in). Apache as a whole may not have gone down,
but i would almost guarantee that at least 2 of your apache processes were
killed (pid 4407 & 4529).
In any event, as already mentioned, its either a bug or bad hardware.
Reply to: