Nico

Well-Known Member
Dec 5, 2001
233
0
316
Edmond, OK
Hello,
We have a server that Apache crahses on everyday about the same time. There does not appear to be any crons running at this time that might cause this and the server load is always near idle with no execessive processes, mysql or httpd connections. The error log show this from yesterday:
Sat Feb 23 07:38:13 2002] [notice] child pid 11233 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11232 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11231 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11230 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11229 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11228 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11227 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11226 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11225 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11224 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11223 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11222 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11253 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11252 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11251 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11250 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11249 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11248 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11247 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11246 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11245 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11244 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11243 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11242 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11241 exit signal Segmentation fault (11), possible coredump in /usr/local/apache

Any idea where to start troubleshooting this? Is there a way to get any useful information from the core file? When opened with a text editor it does not read it well.
 

rpmws

Well-Known Member
Aug 14, 2001
1,822
9
318
back woods of NC, USA
[quote:6e92968270][i:6e92968270]Originally posted by Nico[/i:6e92968270]

Hello,
We have a server that Apache crahses on everyday about the same time. There does not appear to be any crons running at this time that might cause this and the server load is always near idle with no execessive processes, mysql or httpd connections. The error log show this from yesterday:
Sat Feb 23 07:38:13 2002] [notice] child pid 11233 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11232 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11231 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11230 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11229 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11228 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11227 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11226 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11225 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11224 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11223 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:13 2002] [notice] child pid 11222 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11253 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11252 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11251 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11250 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11249 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11248 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11247 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11246 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11245 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11244 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11243 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11242 exit signal Segmentation fault (11), possible coredump in /usr/local/apache
[Sat Feb 23 07:38:14 2002] [notice] child pid 11241 exit signal Segmentation fault (11), possible coredump in /usr/local/apache

Any idea where to start troubleshooting this? Is there a way to get any useful information from the core file? When opened with a text editor it does not read it well. [/quote:6e92968270]

I think that Seg (11) is possible bad ram... do a search for that and I think you will find someone else saying they found a problem with mod_perl. Good luck ;)
 

rpmws

Well-Known Member
Aug 14, 2001
1,822
9
318
back woods of NC, USA
This may help you.

http://support.cpanel.net/obb/read.php?TID=1205
 

feanor

Well-Known Member
Aug 13, 2001
836
0
316
Yea definitely run the memory test that Shaun mentioned in that thread- also notice it is dumping a core in /usr/local/apache, right?

Might want to run strings on that to see where the issues begin- there is a slim chance this still might be the operating system's fault.
 

Nico

Well-Known Member
Dec 5, 2001
233
0
316
Edmond, OK
Strings

This is what the start of the file reports:

[email protected] [/usr/local/apache]# strings core | more
CORE
[email protected]#
CORE
httpd
/usr/local/apache/bin/httpd -DSSL
CORE
httpd
CORE
[:&:]]
[:&:]]
*** unknown regexp error code ***
invalid argument to regex routine
REG_INVARG
&can't happen& -- you found a bug
REG_ASSERT
empty (sub)expression
REG_EMPTY
repetition-operator operand invalid
REG_BADRPT
out of memory
REG_ESPACE
invalid character range
REG_ERANGE
invalid repetition count(s)
REG_BADBR
braces not balanced
REG_EBRACE
parentheses not balanced
REG_EPAREN
brackets ([ ]) not balanced
REG_EBRACK
invalid backreference number
REG_ESUBREG
trailing backslash (\)
REG_EESCAPE
invalid character class
REG_ECTYPE
invalid collating element
REG_ECOLLATE
invalid regular expression
REG_BADPAT
regexec() failed to match
REG_NOMATCH
REG_0x%x
IPAE
IPAE\s
()&&@,;:\&/[]?=
IPAE


Any ideas?
 

jassi

Member
Jun 23, 2006
11
0
151
India
how to fix segmentation fault

you need to remove

rm /tmp/localhost_* and restart apache thats it.

--
Best Regards,
Sarwan Singh Jassi JSA II
System Administrator Lunarpages
[email protected]
Phone: 1-714-521-8150 (International)
 

dryan

Registered
PartnerNOC
Jun 6, 2007
2
0
151
Seg fault in Apache

Hey, it actually just helped me out immensely! Thanks for replying!
 

ravibagul

Member
Mar 16, 2006
16
0
151
child pid xxxxx exit signal Segmentation fault (11)

Error: child pid xxxxx exit signal Segmentation fault (11)

Solution:

Please try to Upgrade/downgrade ZendOptimizer

This will help you.


:)
 
Last edited: