After I migrated wordpress from a shared host to my own VPS I got the unpleasant surprise that half of the back-end pages on my websites rendered a No data receive ERR_EMPTY_RESPONSE.
Determined to find out what caused the problem I started troubleshooting. 7 of my 8 websites were affected, all running wordpress 4.1.5. Upgrading to 4.2.2 did not fix the problem.
The only unaffected website is an old website running on wordpress 3.3.1. Upgrading this website to run 4.2.2 results in the same errors. When I try to do a fresh wordpress install the same error pops up after step one (both when installing 4.2.2 and 3.3.1).
The 7 sites are running on 4 different themes, and I tried dis-enabling all plugins, still no luck.
I had a look at the error logs, I will copy a fragment here since they might provide some useful info. I've been googling all these lines but can't find the solution yet.
[Sun Jun 21 10:22:41 2015] [notice] caught SIGTERM, shutting down
[Sun Jun 21 10:22:42 2015] [notice] SSL FIPS mode disabled
[Sun Jun 21 10:22:42 2015] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Sun Jun 21 10:22:42 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Jun 21 10:22:43 2015] [notice] SSL FIPS mode disabled
[Sun Jun 21 10:22:43 2015] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Sun Jun 21 10:22:43 2015] [notice] Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips DAV/2 PHP/5.2.17 configured -- resuming normal operations
[Sun Jun 21 10:22:59 2015] [notice] child pid 3943 exit signal Segmentation fault (11)
[Sun Jun 21 10:23:00 2015] [notice] child pid 3944 exit signal Segmentation fault (11)
[Sun Jun 21 10:23:02 2015] [notice] child pid 3945 exit signal Segmentation fault (11)
[Sun Jun 21 10:23:03 2015] [notice] child pid 3942 exit signal Segmentation fault (11)
[Sun Jun 21 10:23:04 2015] [notice] child pid 4080 exit signal Segmentation fault (11)
[Sun Jun 21 10:23:05 2015] [notice] child pid 3946 exit signal Segmentation fault (11)
[Sun Jun 21 10:23:06 2015] [notice] child pid 4083 exit signal Segmentation fault (11)
[Sun Jun 21 10:23:07 2015] [notice] child pid 4082 exit signal Segmentation fault (11)
Related
Mac Apache 2.4 / PHP Version 7.3.6 stack. I'm not using MAMP. I have several web-project folders in the web-root directory. All sites work fine except two which are both WordPress sites with similar theme/code.
When accessing index.php file of those two projects the browser wont finish loading the page and gives an error page "The Connection has been reset". I can login and reset the permalinks and then the page will load again.
I have concluded that it is the .htacess file since if I delete it (or reset permalinks as mentioned above), the page will load fine.
However, after some time (hours or even the next day), the problem has returns. I have scanned for viruses using WordFence but I have not gone through all the source code to try and find the problem.
The /var/log/apache2/error_log file output includes this for every page load I attempt:
[Mon Jul 22 17:50:31.470224 2019] [core:notice] [pid 80] AH00052: child pid 37499 exit signal Segmentation fault (11)
[Mon Jul 22 17:50:32.544341 2019] [core:notice] [pid 80] AH00052: child pid 37677 exit signal Segmentation fault (11)
[Mon Jul 22 17:50:33.620666 2019] [core:notice] [pid 80] AH00052: child pid 37680 exit signal Segmentation fault (11)
[Mon Jul 22 17:50:33.620762 2019] [core:notice] [pid 80] AH00052: child pid 37679 exit signal Bus error (10)
[Mon Jul 22 17:50:34.707740 2019] [core:notice] [pid 80] AH00052: child pid 37684 exit signal Segmentation fault (11)
[Mon Jul 22 17:50:34.707818 2019] [core:notice] [pid 80] AH00052: child pid 37683 exit signal Segmentation fault (11)
[Mon Jul 22 17:50:34.707840 2019] [core:notice] [pid 80] AH00052: child pid 37682 exit signal Segmentation fault (11)
[Mon Jul 22 17:50:34.707859 2019] [core:notice] [pid 80] AH00052: child pid 37681 exit signal Bus error (10)
[Mon Jul 22 17:50:35.780855 2019] [core:notice] [pid 80] AH00052: child pid 37685 exit signal Segmentation fault (11)
I have tried clearing the browser cache. Safari, Firefox, and Chome all behave the same.
I have also md5 checksummed the fresh and functional .htaccess file and the .htaccess file when the page refuses to load. They md5 outputs are the same.
What could be causing the .htaccess file to cause Apache to Seg-fault? Is there another possible explanation?
Check if you have AddType directives in .htaccess and remove them.
I had the same problem which started with Catalina, and removing AddType fixed the problem.
My PHP version is 7.3.25 and Apache version is 2.4.41.
I recently updated to the latest version of macOS and can't get an old MAMP-dependent project I have to run. It was working fine right before I upgraded. I googled my way around thinking the upgrade might be something simple like the previous OS upgrade fix that required simply renaming the file but I couldn't fine anything.
Has anyone else had any MAMP issues with the latest macOS update or what are some common local environment fixes to look into after an OS update?
apache_error_log:
[Sun Nov 27 17:40:12 2016] [notice] FastCGI: process manager initialized (pid 2517)
[Sun Nov 27 17:40:12 2016] [notice] Digest: generating secret for digest authentication ...
[Sun Nov 27 17:40:12 2016] [notice] Digest: done
[Sun Nov 27 17:40:13 2016] [notice] Apache/2.2.26 (Unix) mod_fastcgi/2.4.6 mod_wsgi/3.4 Python/2.7.6 PHP/5.5.10 DAV/2 mod_ssl/2.2.26 OpenSSL/0.9.8zh mod_perl/2.0.8 Perl/v5.18.2 configured -- resuming normal operations
[Sun Nov 27 18:41:25 2016] [notice] caught SIGTERM, shutting down
[Sun Nov 27 18:41:34 2016] [notice] FastCGI: process manager initialized (pid 2928)
[Sun Nov 27 18:41:34 2016] [notice] Digest: generating secret for digest authentication ...
[Sun Nov 27 18:41:34 2016] [notice] Digest: done
[Sun Nov 27 18:41:35 2016] [notice] Apache/2.2.26 (Unix) mod_fastcgi/2.4.6 mod_wsgi/3.4 Python/2.7.6 PHP/5.5.10 DAV/2 mod_ssl/2.2.26 OpenSSL/0.9.8zh mod_perl/2.0.8 Perl/v5.18.2 configured -- resuming normal operations
I was also having trouble with MAMP after having upgraded the Mac operating system to the High Sierra. The Apache Server was not starting. My MAMP is an old version (version 1.9). To solve I just created a folder called logs inside the Library folder. Only that and MAMP returned to normal operation.
I found this solution by seeing in the logs folder. In the Apache log (apache_error_log) I saw that it was looking for the "logs" folder inside the "Library" folder, which did not exist. So just creating this folder solved.
Ok so this happened to me the other day and I was able to resolve it by reinstalling WordPress, my WordPress theme and all of its plugins (took forever)
It has now happened again so I need to get to the root of the issue.
I have a website running on my localhost (using MAMP)
When I visit localhost:8888/ I am able to access my entire file directory.
All other sites on my localhost are loading without issue, except for the site I need to access. I am getting a 500 error in the browser.
When I enable WP Debug it doesn't change from the 500 error in the browser.
I have not modified this site in any way to cause this issue, it literally just randomly bricks itself. The same thing happened before to the exact same site.
I have gone through a ton of guides and am completely lost at what is causing the issue.
Would really appreciate some help troubleshooting.
This is my latest error log from apache.
[Tue Jul 05 14:43:49 2016] [notice] caught SIGTERM, shutting down
[Tue Jul 05 14:43:52 2016] [notice] Digest: generating secret for digest authentication ...
[Tue Jul 05 14:43:52 2016] [notice] Digest: done
[Tue Jul 05 14:43:52 2016] [notice] FastCGI: process manager initialized (pid 1372)
[Tue Jul 05 14:43:52 2016] [notice] Apache/2.2.29 (Unix) mod_wsgi/3.4 Python/2.7.8 PHP/5.5.23 mod_ssl/2.2.29 OpenSSL/0.9.8zh DAV/2 mod_fastcgi/2.4.6 mod_perl/2.0.8 Perl/v5.20.0 configured -- resuming normal operations
[Tue Jul 05 14:44:05 2016] [notice] caught SIGTERM, shutting down
[Tue Jul 05 14:44:07 2016] [notice] Digest: generating secret for digest authentication ...
[Tue Jul 05 14:44:07 2016] [notice] Digest: done
[Tue Jul 05 14:44:07 2016] [notice] FastCGI: process manager initialized (pid 1414)
[Tue Jul 05 14:44:07 2016] [notice] Apache/2.2.29 (Unix) mod_wsgi/3.4 Python/2.7.8 PHP/5.6.7 mod_ssl/2.2.29 OpenSSL/0.9.8zh DAV/2 mod_fastcgi/2.4.6 mod_perl/2.0.8 Perl/v5.20.0 configured -- resuming normal operations
[Tue Jul 05 16:48:35 2016] [error] [client ::1] client denied by server configuration: /Users/brettgolding/Google Drive/htdocs/.DS_Store
Site was working fine this morning and now just a white screen after about a 45 second load. Latency is super high and saw a huge spike in database requests before crash. Here is some info from the error log:
[Tue Jan 20 19:35:35.758727 2015] [:error] [pid 5259] [client 10.164.61.169:9962] PHP Notice: Undefined offset: 0 in /var/app/current/content/themes/thereserve/_modules/z_interactive_map/_admin/settings-properties.php on line 217
[Tue Jan 20 19:35:35.761324 2015] [:error] [pid 5259] [client 10.164.61.169:9962] PHP Notice: Trying to get property of non-object in /var/app/current/content/themes/thereserve/_modules/z_interactive_map/_admin/settings-properties.php on line 217
[Tue Jan 20 19:41:34.521481 2015] [mpm_prefork:error] [pid 1867] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
[Tue Jan 20 20:53:29.784736 2015] [mpm_prefork:notice] [pid 1867] AH00171: Graceful restart requested, doing restart
[Tue Jan 20 20:53:34.308282 2015] [auth_digest:notice] [pid 1867] AH01757: generating secret for digest authentication ...
[Tue Jan 20 20:53:34.344476 2015] [lbmethod_heartbeat:notice] [pid 1867] AH02282: No slotmem from mod_heartmonitor
[Tue Jan 20 20:53:34.427428 2015] [mpm_prefork:notice] [pid 1867] AH00163: Apache/2.4.6 (Amazon) configured -- resuming normal operations
[Tue Jan 20 20:53:34.427451 2015] [core:notice] [pid 1867] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
The fact that the "server reached MaxRequestWorkers setting" is a little alarming. I can't answer why that happens, but that might be the result of another problem.
If hitting the MaxRequestWorkers setting itself is not the RESULT of another problem but the problem itself, you can raise the "MaxRequestWorkers" ceiling in /etc/apache2/mods-available/mpm_worker.conf, then restart Apache.
I can access the actual wordpress site via WAMP's localhost route, but I cannot log into the admin/dashboard page of the wordpress site.
I think it is a problem with apache.
Can anybody help me?
here are messages from the apache error logs:
[Sun Nov 03 07:11:17.294107 2013] [mpm_winnt:notice] [pid 2700:tid 416] AH00422: Parent: Received shutdown signal -- Shutting down the server.
[Sun Nov 03 07:11:19.296221 2013] [mpm_winnt:notice] [pid 5784:tid 324] AH00364: Child: All worker threads have exited.
[Sun Nov 03 07:11:19.328223 2013] [mpm_winnt:notice] [pid 2700:tid 416] AH00430: Parent: Child process 5784 exited successfully.
[Sun Nov 03 07:11:22.842424 2013] [mpm_winnt:notice] [pid 5408:tid 416] AH00455: Apache/2.4.4 (Win32) PHP/5.4.16 configured -- resuming normal operations
[Sun Nov 03 07:11:22.842424 2013] [mpm_winnt:notice] [pid 5408:tid 416] AH00456: Server built: Feb 23 2013 13:07:34
[Sun Nov 03 07:11:22.842424 2013] [core:notice] [pid 5408:tid 416] AH00094: Command line: 'c:\\wamp\\bin\\apache\\apache2.4.4\\bin\\httpd.exe -d C:/wamp/bin/apache/Apache2.4.4'
[Sun Nov 03 07:11:22.844424 2013] [mpm_winnt:notice] [pid 5408:tid 416] AH00418: Parent: Created child process 4348
[Sun Nov 03 07:11:24.173500 2013] [mpm_winnt:notice] [pid 4348:tid 324] AH00354: Child: Starting 150 worker threads.
More info:
The error is not a 404. Rather wordpress doesnt recognize my username/password.
final edit:
found a solution to my problem:
http://www.velvetblues.com/web-development-blog/how-to-add-an-admin-user-to-a-wordpress-database/