[BlueOnyx:22569] Re: Odd Wordpress issue

Mon Dec 24 20:09:24 -05 2018

Don,

I recently had a client’s wordpress site start crashing in a similar way till I increased memory to 256MB in my case. This started after the site auto-updated the wordpress version. In my case I had to clear the cache in wp-super-cache to get things back to more or less normal. 

What led me to look there first is I’ve seen similar issues before and clearing the cache took care of it. It’s also taken care of other strange wordpress behavior from time to time. Kind of my go-to first thing with wordpress issues is to clear any cache whether wp-super-cache or some other caching add-in or caching integrated into some templates.

Used to be wp-super-cache really sped up a site, but now with some involved browser caching and other optimizations in .htaccess there seems little benefit for my clients’ sites and sometimes sites even seem to make them run more slowly.

The other big thing for sites that were working suddenly breaking is malicious software getting placed into the site… but that’s another problem. 

Hope this gives a little help.

                Thanks,

                                -Stephanie

From: Blueonyx [mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of Don Teague
Sent: Sunday, December 23, 2018 8:52 PM
To: BlueOnyx General Mailing List
Subject: [BlueOnyx:22567] Odd Wordpress issue

Sorry, right now I don't know where else to turn to.

Summary: Front end of WP 5.0.2 is throwing various PHP errors, but backend is working fine.

History:
Server is a new 5209, all yum updates installed. Built the site on the same server under a different domain name. That site is still up and is reachable. I then used a backup/restore utility to copy site from account A to account B. On 'newdomain' it was working fine, and I was doing some final clean up work before taking the site live. Currently DNS for the domain is redirecting to a place holder site. DNS is not hosting on the machine. I'm using windows hosts file to get to the 'newdomain'. Old site (build) is in DNS. As I would make the changes I would refresh the newdomain site so I could see the changes. After one simple change (as in just adding an <a href> to a line of text) it started throwing errors.

Both sites are using PHP 5.6.24, purchased from BlueOnyx. Once this error kicked in I had to bump memory up to 1024M before I could even see the error message. It was at 128 or 256 (I honestly forget) and was working fine. Made that one change (listed above) and it wouldn't load. Noticed php memory errors, and pushed up to 1024. Then the new error message below.

/var/log/httpd/error_log

[Sun Dec 23 19:08:42.892735 2018] [core:error] [pid 6765] [client 172.241.112.92:65032] End of script output before headers: index.php

[Sun Dec 23 19:14:40.902367 2018] [core:error] [pid 6766] [client 172.241.112.92:65418] End of script output before headers: index.php

Dec 23 19:23:36 [servername] kernel: php-cgi[7665]: segfault at 7fff041bdff8 ip 00000000008069ae sp 00007fff041be000 error 6 in php-cgi[400000+a67000]

When trying to visit the site you get this error: ('newdomain' via Windows Hosts file.)

The server encountered an internal error or misconfiguration and was unable to complete your request. Your administrator may not have enabled CGI access for this directory.

Anyone smarter than me have an idea where I could start looking?

Don Teague   

photo

Email: <mailto:don at replytodon.com>  don at replytodon.com
Website: <http://www.donteague.com>  http://www.donteague.com
Website: <http://iml.donteague.com>  http://iml.donteague.com

 <http://facebook.com/don.teague> https://dn3tzca2xtljm.cloudfront.net/social_icons/16px/facebook.png

 <http://www.instagram.com/don_teague/> https://dn3tzca2xtljm.cloudfront.net/social_icons/16px/instagram.png

 <http://twitter.com/don_teague> https://dn3tzca2xtljm.cloudfront.net/social_icons/16px/twitter.png

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20181224/fc1ad169/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1535 bytes
Desc: not available
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20181224/fc1ad169/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 265 bytes
Desc: not available
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20181224/fc1ad169/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 702 bytes
Desc: not available
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20181224/fc1ad169/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 309 bytes
Desc: not available
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20181224/fc1ad169/attachment-0002.png>