• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Find who is causing Apache segmentation fault

Amin Taheri

Golden Pleskian
Plesk Certified Professional
hello,

We have been seeing something similiar to this lately

[date] [notice] child pid 19642 exit signal Segmentation fault (11)

so I then tried to look through the clients error logs

grep -i 'Wed Oct 24 13:42' /var/www/vhosts/*/statistics/logs/error_log

This only showed a couple of 404 errors with directories or files not existing

then the server access log -> this came back with nothing

and the server error log only reported the seg fault line we already had.

Even if I check before and after that line for any clues, it doesnt seem to help me too much

grep -i -B3 -A1 'Wed Oct 24 13:42' /var/log/httpd/error_log
[Wed Oct 24 13:37:20 2007] [notice] Apache configured -- resuming normal operations
[Wed Oct 24 13:37:20 2007] [warn] long lost child came home! (pid 12756)
[Wed Oct 24 13:41:51 2007] [error] [client 65.55.210.25] File does not exist: /var/www/vhosts/default/htdocs/Kbc.cfm
[Wed Oct 24 13:42:31 2007] [notice] child pid 24389 exit signal Segmentation fault (11)

How do we find which user is causing this to occur?
 
Back
Top