• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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