DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23084>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23084 Apache Segfaults and won't dump core Summary: Apache Segfaults and won't dump core Product: Apache httpd-1.3 Version: 1.3.27 Platform: PC OS/Version: Other Status: NEW Severity: Major Priority: Other Component: core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Howdy, We are running Apache 1.3.27 on a pair of Redhat Linux 7.3 web servers. For some reason, Apache will hang every 4 -5 days, and stop answering requests. The only errors we receive are: [Wed Sep 10 13:20:13 2003] [notice] child pid 20902 exit signal Segmentation fault (11) [Wed Sep 10 13:20:53 2003] [notice] child pid 20899 exit signal Segmentation fault (11) [Wed Sep 10 13:21:00 2003] [notice] child pid 24929 exit signal Segmentation fault (11) [Wed Sep 10 13:21:01 2003] [notice] child pid 20901 exit signal Segmentation fault (11) [Wed Sep 10 13:21:50 2003] [notice] child pid 16969 exit signal Segmentation fault (11) [Wed Sep 10 13:21:51 2003] [notice] child pid 16963 exit signal Segmentation fault (11) [Wed Sep 10 13:22:39 2003] [notice] child pid 20861 exit signal Segmentation fault (11) [Wed Sep 10 13:22:46 2003] [notice] child pid 25042 exit signal Segmentation fault (11) as each child dies off. I have read through the archives, and thought that core dumps were not enabled, so I added "ulimit -c unlimited" to the rc script, and added CoreDumpDirectory in my httpd.conf (the directory this points to is writeable by root and the user the web server runs as). When I attach to the main Apache process during one of these hangs, I see the following: (gdb) where #0 0x4020941e in select () from /lib/libc.so.6 #1 0x08086078 in __DTOR_END__ () #2 0x080602bc in standalone_main () #3 0x08060aa3 in main () #4 0x4014a1c4 in __libc_start_main () from /lib/libc.so.6 I relaize this isn't the most helpful bt, but trying to give you as much info as I can. Here is the output of ps during the hang: pache 20154 0.0 0.0 0 0 ? Z Sep07 0:07 [httpd <defunct>] apache 20156 0.0 0.0 0 0 ? Z Sep07 0:07 [httpd <defunct>] apache 24703 0.0 0.0 0 0 ? Z 12:55 0:00 [httpd <defunct>] apache 24713 0.0 0.0 0 0 ? Z 12:56 0:00 [httpd <defunct>] apache 24735 0.0 0.0 0 0 ? Z 12:57 0:00 [httpd <defunct>] apache 24802 0.0 0.0 0 0 ? Z 13:03 0:00 [httpd <defunct>] apache 24803 0.0 0.0 39232 2856 ? S 13:03 0:00 [httpd] apache 24804 0.0 0.0 0 0 ? Z 13:03 0:00 [httpd <defunct>] apache 24823 0.0 0.0 0 0 ? Z 13:05 0:00 [httpd <defunct>] apache 24843 0.0 0.0 0 0 ? Z 13:07 0:00 [httpd <defunct>] apache 24882 0.0 0.0 0 0 ? Z 13:07 0:00 [httpd <defunct>] apache 24883 0.0 0.0 0 0 ? Z 13:07 0:00 [httpd <defunct>] apache 24690 0.0 0.0 39440 3500 ? T 12:55 0:00 [httpd] apache 24884 0.0 0.0 39128 2488 ? T 13:07 0:00 [httpd] apache 16257 0.0 0.1 39912 3984 ? T Sep07 0:07 [httpd] apache 16260 0.0 0.1 39904 3996 ? T Sep07 0:07 [httpd] apache 16360 0.0 0.1 39804 3876 ? T Sep07 0:07 [httpd] root 14716 0.0 0.0 38960 2344 ? T Sep05 0:00 /usr/sbin/httpd - DHAVE_ACCESS -DHAVE_PROXY -DHAVE_AUTH_ANON -DHAVE_ACTIONS -DHAVE_ALIAS - DHAVE_ASIS -DHAVE_AUTH -DHAVE_AUTOINDEX -DHAVE_AUTH_DB -DHAVE_AUTH_DBM - DHAVE_SSL -DHAVE_CERN_META -DHAVE_CGI -DHAVE_DIGEST -DHAVE_DIR -DHAVE_ENV - DHAVE_EXAMPLE -DHAVE_EXPIRES -DHAVE_HEADERS -DHAVE_IMAP -DHAVE_INCLUDE - DHAVE_INFO -DHAVE_LOG_AGENT -DHAVE_LOG_CONFIG -DHAVE_LOG_REFERER -DHAVE_MIME - DHAVE_MIME_MAGIC -DHAVE_MMAP_STATIC -DHAVE_NEGOTIATION -DHAVE_REWRITE - DHAVE_SETENVIF -DHAVE_SPELING -DHAVE_STATUS -DHAVE_UNIQUE_ID -DHAVE_USERDIR - DHAVE_USERTRACK -DHAVE_VHOST_ALIAS -DHAVE_AUTH_LDAP -DHAVE_PHP4 -DHAVE_WL_SSL We are only utilizing the AUTH_LDAP and BEA Weblogic modules, and I have attached teh versions of all the applicable RPMs: glibc-common-2.2.5-42 glibc-2.2.5-42 apache-1.3.27-2 auth_ldap-1.6.0-9 netscape-ldapsdk-opt-5.08-5 openldap-2.0.23-4 nss_ldap-189-4 If you have any recommendations on ways to dump core ( I tried kill -SIGSEGV PID), I am all ears. This would allow me to pinpoint where the hangup is occurring. If there are any additional debug flags I can enable, I can do this as well. The web servers that keep Segfaulting have a pretty decent load on them. Thank you, - Ryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
