468,140 Members | 1,465 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,140 developers. It's quick & easy.

Segmentation fault (11)

Hello everybody,

As of some time ago I started seeing "exit signal Segmentation fault
(11)" in /var/log/apache2/error.log. I'm running the current stable
Debian, php4 and Apache. We have quite a few users and usually hear
about any errors. But although I see a lot of these in the error log,
no one seems to be complaining.

Now, the child dies a couple of seconds later than the last access by
that child according to /var/log/apache2/access.log. So, the page must
be served completely and several seconds later, the child dies. What's
the best way to debug this one? I've enabled core dumping but no cores
are found under /tmp -- is this where they are supposed to appear? The
pages it happens to seem to be kind of random.

I've seen a lot of discussion about "Segmentation fault (11)" but I
didn't see what the resolution was. Sorry if this has been asked
before...

Best regards,
Sergei
Apr 11 '08 #1
3 1864
On 11 Apr, 19:42, surge <gera...@gmail.comwrote:
Hello everybody,

As of some time ago I started seeing "exit signal Segmentation fault
(11)" in /var/log/apache2/error.log. I'm running the current stable
Debian, php4 and Apache. We have quite a few users and usually hear
about any errors. But although I see a lot of these in the error log,
no one seems to be complaining.

Now, the child dies a couple of seconds later than the last access by
that child according to /var/log/apache2/access.log. So, the page must
be served completely and several seconds later, the child dies. What's
the best way to debug this one? I've enabled core dumping but no cores
are found under /tmp -- is this where they are supposed to appear? The
pages it happens to seem to be kind of random.

I've seen a lot of discussion about "Segmentation fault (11)" but I
didn't see what the resolution was. Sorry if this has been asked
before...

Best regards,
Sergei
Read this:

http://aplawrence.com/Linux/limit_core_files.html

Check ulimit and permissions for webserver uid.

C.
Jun 2 '08 #2
Thanks for the reply. I've read the article and tweaked my settings.
Now I'm waiting for a core dump, which, as luck would have it, hasn't
happened all day :)
Jun 2 '08 #3
On Apr 14, 5:18 pm, surge <gera...@gmail.comwrote:
Thanks for the reply. I've read the article and tweaked my settings.
Now I'm waiting for a core dump, which, as luck would have it, hasn't
happened all day :)

Hmm, the cores are still not dumped even though "kill -s SIGSEGV $$"
does create a core in the right directory. Any ideas?
Jun 2 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by sivignon | last post: by
1 post views Thread by Justin Tang | last post: by
11 posts views Thread by Polar | last post: by
27 posts views Thread by Paminu | last post: by
59 posts views Thread by Christian Christmann | last post: by
3 posts views Thread by madunix | last post: by
27 posts views Thread by didacticone | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.