[ previous ] [ next ] [ threads ]
 
 From:  Phil Brutsche <phil at brutsche dot us>
 To:  Joe Lagreca <joe at BIGnetOnline dot com>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] m0n0wall web server crashing?
 Date:  Mon, 01 Oct 2007 13:45:40 -0500
Signal 11 is SIGSEGV (segment violation) and signal 10 is SIGBUS (bus
error). Such errors are usually caused by bad memory, CPU, or motherboard.

Joe Lagreca wrote:
> Last night I was unable to web manage one of my m0n0walls (version
> 1.231).  PPTP server in it was also not working, however it seemed to
> be passing traffic correctly.  This morning I was able to web into it
> for a time, I rebooted it, and all seemed to work fine.  Then I got a
> browser popup error about some authentication problem, and I was
> locked out again.  A few minutes later I could get back into it and
> found this in the logs:
> 
> Oct 1 09:09:11 	/kernel: pid 3008 (mini_httpd), uid 0: exited on signal 10
> Oct 1 09:08:24 	/kernel: pid 2903 (mini_httpd), uid 0: exited on signal 11
> Oct 1 09:05:38 	/kernel: pid 2530 (mini_httpd), uid 0: exited on signal 11
> Oct 1 09:03:45 	/kernel: pid 2278 (php), uid 0: exited on signal 11
> Oct 1 09:01:47 	/kernel: pid 2033 (mini_httpd), uid 0: exited on signal 10
> Oct 1 09:01:40 	/kernel: pid 2020 (mini_httpd), uid 0: exited on signal 10
> Oct 1 09:01:28 	/kernel: pid 1995 (mini_httpd), uid 0: exited on signal 11
> 
> Looks like the web server is crashing?  Any ideas?
> 


-- 

Phil Brutsche
phil at brutsche dot us