On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

How to enable core dumps for Apache and trace Apache segmentation fault on a Linux server

Follow

Comments

4 comments

  • Avatar
    Tony

    is there a default directory/location plesk-php74-fpm/error.log core dumps get saved?  I see lines like this but i don't know how to get more information.

    `WARNING: [pool example.com] child 466554 exited on signal 11 (SIGSEGV - core dumped) after 1.221340 seconds from start`

    0
    Comment actions Permalink
  • Avatar
    Tony (Edited )

    nevermind.  i can see now that this information DOES apply to my apache php-fpm server. i did have to find the correct php-fpm to pass 
    root@servername:/var/coredumps# gdb /opt/plesk/php/7.4/sbin/php-fpm /var/coredumps/core-php-fpm-11-10109-1006-505241-1632347775

    0
    Comment actions Permalink
  • Avatar
    Tony

    except 
    apt-get install apache2-dbg

    E: Unable to locate package apache2-dbg

    0
    Comment actions Permalink
  • Avatar
    Tony

    i then found i could enable/disable the core dump for the specific domain by customizing the php directives for that specific domain in plesk eg.
    [php-fpm-pool-settings]
    rlimit_core = unlimited

    (and then remove that to disable the core dumps!   six core dumps from my site were 1.8GB in disk size, so be careful!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request