Chrome Err Empty Response occasionally when going to homepage

Posted on January 10, 2020

Up until recently, I have been seeing on chrome err_empty_response when going to my website homepage. It rarely happens, but lately it has been noticeably happening more frequently.

After refreshing a few times it comes back.

In the error logs I can see a few of the following lines:

child pid 23559 exit signal Segmentation fault (11), possible coredump in /etc/apache2

Using wordpress on apache and ubuntu, with W3 total cache and Autoptimize.

Can anyone recommend any action that might help with this? Thanks

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby

January 10, 2020

Hello,

I could suggest a few things:

If you do not want to spend time investigating this straight away, try to upgrade your Apache, PHP, Wordpress version along with all plugins and see if the problem persists.
If this does not help, then you would need to enable core dumps for your Apache instance and then analyze the core dumps

If you need to do that, here’s what you would have to do:

SSH to your Droplet
Edit the following file

/etc/default/apport

And change enabled from “0” to a “1” so it looks like this.

Note, for more information about Apport check out the official documentation here.

Then edit your apache config apache2.conf and add the following:

CoreDumpDirectory /tmp/apache2-core-dump

Create that directory and make sure Apache can write to the file:

sudo mkdir  /tmp/apache2-core-dump
sudo chmod 777 /tmp/apache2-core-dump

Remove the file size limit:

ulimit -c unlimited

Than try to cause the segmentation fault again and you should see a core dump popup in the /tmp/apache2-core-dump directory.
After that to analyze the core dump use the gdb command:

gdb apache2 /tmp/apache2-core-dump/coredump-TIMESTAMP

Right after this, to see stack trace details, in gdb run:

where

This would give you more information on what’s causing the segmentation fault.

Hope that this helps! Regards, Bobby

matt41f5576fd18eff1f5bf8ed

February 7, 2020

This comment has been deleted

matt41f5576fd18eff1f5bf8ed

February 7, 2020

Hi Bobby The result of your answer gives the following output

[Thread debugging using libthread_db enabled] Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”. Core was generated by `/usr/sbin/apache2 -k start’. Program terminated with signal SIGILL, Illegal instruction.