Portal Home > Knowledgebase > Articles Database > Reboot failure
Posted by zetaf, 03-18-2008, 08:39 AM so my server dies every day and requires human intervention to fully restart all service to have my site work properly. i suspect sigterm issues as it fails to restart all service as website is still down so i always have to reboot it. Tried recompile apache with no success [Tue Mar 18 06:51:27 2008] [error] [client 203.160.1.39] request failed: erroneous characters after protocol string: If-Modified-Since: Wed, 21 Nov 2007 06:16:52 GMT [Tue Mar 18 10:03:18 2008] [error] Bad pid (7465) in scoreboard slot 16 [Tue Mar 18 10:03:18 2008] [error] Bad pid (27848) in scoreboard slot 17 [Tue Mar 18 10:03:18 2008] [error] Bad pid (27434) in scoreboard slot 18 [Tue Mar 18 10:03:18 2008] [error] Bad pid (30782) in scoreboard slot 19 [Tue Mar 18 10:03:18 2008] [error] Bad pid (7465) in scoreboard slot 16 [Tue Mar 18 10:03:18 2008] [error] Bad pid (27848) in scoreboard slot 17 [Tue Mar 18 10:03:18 2008] [error] Bad pid (27434) in scoreboard slot 18 [Tue Mar 18 10:03:18 2008] [error] Bad pid (30782) in scoreboard slot 19 [Tue Mar 18 10:03:18 2008] [error] Bad pid (7465) in scoreboard slot 16 [Tue Mar 18 10:03:18 2008] [error] Bad pid (27848) in scoreboard slot 17 [Tue Mar 18 10:03:18 2008] [error] Bad pid (27434) in scoreboard slot 18 [Tue Mar 18 10:03:18 2008] [error] Bad pid (30782) in scoreboard slot 19 [Tue Mar 18 10:03:18 2008] [notice] caught SIGTERM, shutting down [Tue Mar 18 10:03:20 2008] [notice] mod_security/1.9.5 configured - Apache/1.3.39 (Unix) PHP/5.2.5 [Tue Mar 18 10:03:20 2008] [notice] Any You Like mod_ssl/2.8.30 OpenSSL/0.9.8g mod_perl/1.29 FrontPage/5.0.2.2510 configured -- resuming normal operations [Tue Mar 18 10:03:20 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Mar 18 10:03:20 2008] [notice] Accept mutex: sysvsem (Default: sysvsem) Last edited by zetaf; 03-18-2008 at 08:43 AM.
Posted by applicurearun, 03-18-2008, 09:03 AM I have a FIX for bad PID: "if (ap_extended_status)", so a bunch of "Bad pid" messages could show up at termination for folks with the default (off) setting for ExtendedStatus. Proposed fix: Index: src/main/http_main.c =================================================================== --- src/main/http_main.c (revision 594940) +++ src/main/http_main.c (working copy) @@ -2661,7 +2661,6 @@ if (status == SERVER_DEAD) { ss->my_access_count = 0L; ss->my_bytes_served = 0L; - ap_scoreboard_image->parent[child_num].pid = 0; } ss->conn_count = (unsigned short) 0; ss->conn_bytes = (unsigned long) 0; @@ -2689,7 +2688,10 @@ ss->vhostrec = r->server; } } - if (status == SERVER_STARTING && r == NULL) { + if (status == SERVER_DEAD) { + ap_scoreboard_image->parent[child_num].pid = 0; + } + else if (status == SERVER_STARTING && r == NULL) { /* clean up the slot's vhostrec pointer (maybe re-used) * and mark the slot as belonging to a new generation. */ --- Try this and if not fix then I may need appach logs.
Add to Favourites 
Print this Article
