httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Hartill <r...@imdb.com>
Subject Restarting server problems (fwd)
Date Tue, 30 Apr 1996 16:56:38 GMT

not acked


Sender: ttongue@proteus.imagiware.com
Message-ID: <3186461A.151D861@imagiware.com>
Date: Tue, 30 Apr 1996 11:55:54 -0500
From: Thomas Tongue <ttongue@imagiware.com>
Organization: Imagiware
X-Mailer: Mozilla 3.0b2 (X11; I; Linux 1.2.13 i586)
MIME-Version: 1.0
To: apache-bugs@apache.org
Subject: Restarting server problems
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

We have been running Apache (various versions) for a while now,
with no crippling problems. However, today we have a new demon,
and we are clueless where it came from. The server starts fine
from our rc.local file, but when we send a restart signal to it
(kill -1 pid), it gives us this:

Apr 30 10:38:48 proteus kernel: general protection: 0000
Apr 30 10:38:48 proteus kernel: EIP:    0010:001432d5
Apr 30 10:38:48 proteus kernel: EFLAGS: 00010046
Apr 30 10:38:48 proteus kernel: eax: f000e987   ebx: 00bba60c  ecx:
0286060c   edx: 02852000
Apr 30 10:38:48 proteus kernel: esi: 00140050   edi: 0285ff24   ebp:
0171ed94   esp: 0285fef4
Apr 30 10:38:48 proteus kernel: ds: 0018   es: 0018   fs: 002b   gs:
002b ss: 0018
Apr 30 10:38:48 proteus kernel: Process httpd (pid: 463, process nr: 20,
stackpage=0285f000)
Apr 30 10:38:48 proteus kernel: Stack: 0171ed20 0285ff24 0171ed94
00000010 001319b1 0171ed94 0285ff24 00000010 
Apr 30 10:38:48 proteus kernel:        bffffb90 080114a9 08018d81
bffffbc8 50000002 00000000 00000000 00000000 
Apr 30 10:38:48 proteus kernel:        08015554 00000004 08015554
00000001 00000009 bffffbc8 0171ed94 00000001 
Apr 30 10:38:48 proteus kernel: Call Trace: 001319b1 0014297a 00132354
0011cd27 0013258c 00110319 
Apr 30 10:38:48 proteus kernel: Code: 66 8b 40 0c 66 39 82 12 03 00 00
0f 85 7a ff ff ff 8b 83 9c 

After this kills the httpd, it will not run normally either, giving the
same error. Only rebooting the machine helps. We are running Linux
1.2.13 (ELF) and Apache 1.0.3. This problem exists with 1.0.0, and
0.8.14 as well. Since this problem _just_ cropped up, we think it
is not just an Apache problem, but some combination between our machine
and Apache. Ever seen anything like this before?

-- 
Thomas Tongue
ttongue@imagiware.com
http://imagiware.com/
----- End of forwarded message from Thomas Tongue -----

-- 
Rob Hartill (robh@imdb.com)
The Internet Movie Database (IMDb)  http://www.imdb.com/
           ...more movie info than you can poke a stick at.

Mime
View raw message