May 25, 2016 at 8:24 am #5991
I am getting a 500 error that only is happening on my buddypress pages not on my theme’s pages.
The error is: [Wed May 25 06:19:38.376238 2016] [core:error] [pid 45757] [client 126.96.36.199:61064] End of script output before headers: index.php
Can anybody help with this?
SimonMay 26, 2016 at 6:38 am #5994
I’m going to need a bit more information to help you find out why this is occurring. To begin with, are you using any plugins beyond those supplied with CBOX? Have you made any changes to the theme?
Best wishes, ChristianMay 26, 2016 at 7:17 am #5995
I am not using the CBOX theme. I do have all of the CBOX plugins activated. I am also using a third party plugin for sign up integration.
Everything was working fine until I actually registered my first two members. One of them made his first status post. I went to reply and got the first 500 error.
Nobody seems to be able to help. I hope you can.
SimonMay 26, 2016 at 11:47 am #5996
I would say that your best chance of solving this is to do some digging into the error logs to find out in greater detail why the error is happening. First add
error_reporting(E_ALL);to the top of your index.php file to get more verbose logging. Then look at the error logs for your server for the details of the error. Your server host should be able to point you to the PHP error log if you’re not sure where it is. If you can post the relevant bits of the log here, I may be able to help further.
My best guess (and that’s only a guess in the absence of detailed logging) is that PHP is running out of memory before the page has been sent to the browser.
Cheers, ChristianMay 26, 2016 at 2:34 pm #5997
I am trying to get the server folks to run the test for me as I am sure to screw things up.
So far they did find this:
“After doing some testing and hair pulling, here’s what I’ve discovered, it most definitely is one or more of your plugins that is causing the issue. Renaming the /wp-content/plugins folder to /wp-content/plugins.bak, and calling those BuddyPress pages, the error no longer occurs on the server. The page doesn’t load all the way (it’s probably looking for a plugin), but the header of the dashboard does come up, and the error on the server resolves itself.”
If I deactivate CBOX just to test will I lose anything?
SimonMay 26, 2016 at 4:18 pm #5998
It looks like it is the new theme. It worked for a week so I didn’t suspect it. Maybe it was an update. Working with the theme developers now. Thanks for your help.May 27, 2016 at 11:05 am #5999
Unfortunately – I am no closer to an answer.
The tech’s at the server write, “I did enable the logging they asked, but nothing was logged.”
The theme developer writes, ”
We tried to upload a file to show all PHP functions and we see that PHP memory is set to 512MB, so that should not be an issue.
Can you please let the hosting’s support team look into the PHP error and access logs? That should give a better view of what is causing the error as error 500 is a generic error and there are a lot of reasons why it is triggered and the logs should help isolate the issue.
As much as we would want to help on this, there really isn’t much we can do as error 500 is triggered from the server. It is most likely caused by the theme or by a plugin and the errors logs on the server will be able to help isolate the issue.”
Any suggestions?May 27, 2016 at 12:08 pm #6000
I just got this back from the tech on the server:
“I’ve enabled logging for all errors, and even turned on the feature to display PHP errors. I had also added that line from the buddypress developers to your index page, and still no errors are shown or logged on the server.”
Any suggestions? Please?May 27, 2016 at 12:32 pm #6001
Sounds confusing! Either there is an error, in which case the server folks should be able to tell you what it is from the server’s PHP error log… or there isn’t an error, in which case your site should run as you expect it to. Beyond that, I’m a bit lost as to what to suggest. It has to be one or the other!
Cheers, ChristianMay 28, 2016 at 1:18 pm #6002
I am confused.
Ok. We finally getting some error logs.
On the main public folder I get the following:
[28-May-2016 14:38:13 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/simonsen/public_html/wp-content/themes/you/theme-setup.php on line 551
[28-May-2016 16:23:32 UTC] PHP Warning: file(): http:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/simonsen/public_html/wp-content/themes/you/theme-setup.php on line 545
[28-May-2016 16:23:32 UTC] PHP Warning: file(http://www.institutechiro.com/wp-content/themes/you/fonts.json): failed to open stream: no suitable wrapper could be found in /home/simonsen/public_html/wp-content/themes/you/theme-setup.php on line 545
[28-May-2016 16:23:32 UTC] PHP Warning: implode(): Invalid arguments passed in /home/simonsen/public_html/wp-content/themes/you/theme-setup.php on line 546
[28-May-2016 16:23:32 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/simonsen/public_html/wp-content/themes/you/theme-setup.php on line 551
On the subdomain where the issue is happening I found another log that reads:
[28-May-2016 06:28:30 UTC] PHP Fatal error: Out of memory (allocated 786432) (tried to allocate 3072 bytes) in /home/simonsen/public_html/members/wp-includes/functions.php on line 1522
[28-May-2016 06:28:30 UTC] PHP Fatal error: Out of memory (allocated 1048576) (tried to allocate 12288 bytes) in /home/simonsen/public_html/members/wp-includes/functions.php on line 3852May 31, 2016 at 6:00 am #6003
You can ignore the PHP warnings for the time-being – they should be investigated but they aren’t critical. The “out of memory” errors, however, are critical and are what you’ll need to focus on. Have you tried a different theme (for example TwentySixteen) on the sub-sites? If the problem does not occur with a different theme, you have a few options:
- use a different theme
- contact the theme developers for support
- switch off plugins on the sub-site to see if one of them is a memory hog
- contact you server admins and have them allocate more memory to PHP
Cheers, ChristianJune 1, 2016 at 10:38 am #6010
Thanks Christian. The theme developer looked at these logs and suggested the problem is with the WP core and not the theme. Frustrating.
Any other thoughts?
Thank you for your reply. I have gone through the php_error_logs that are inside of your account. Only two of them had errors from today and I am including those below.
Inside of public_html/wp-admin/php_error_log the recent errors are: [31-May-2016 02:20:16 UTC] PHP Warning: Error while sending QUERY packet. PID=945400 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811 [31-May-2016 02:20:49 UTC] PHP Warning: Error while sending QUERY packet. PID=945400 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811 [31-May-2016 02:21:36 UTC] PHP Warning: Error while sending QUERY packet. PID=945400 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811 [31-May-2016 02:22:10 UTC] PHP Warning: Error while sending QUERY packet. PID=945400 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811
Inside of public_html/php_error_log the recent errors are: [31-May-2016 02:27:13 UTC] PHP Warning: Error while sending QUERY packet. PID=945351 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811 [31-May-2016 05:26:08 UTC] PHP Warning: Error while sending QUERY packet. PID=582331 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811 [31-May-2016 05:29:30 UTC] PHP Warning: Error while sending QUERY packet. PID=582331 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811 [31-May-2016 05:33:27 UTC] PHP Warning: Error while sending QUERY packet. PID=582331 in /home/simonsen/public_html/wp-includes/wp-db.php on line 1811
Those errors all reference a line in wp-db.php which says: $this->result = mysqli_query( $this->dbh, $query );
It seems like the error is related to it not being able to do the particular query that it references on line 1811. I do not know if that is the main error that you have been seeing but that is what is reference in the php_error_log files. As always, please feel free to let me know if you have any questions or concerns and I will be able to assist.June 1, 2016 at 10:41 am #6011
I tried shutting each plugin and that did not help. Switching themes did help although I am pretty invested in this theme with the amount of hours I put in for design and how good it looks.
I just switched servers hoping siteground techs could help.June 1, 2016 at 11:59 am #6012
Hi Simon, you should ask the server admins to increase the value for
max_allowed_packet. A server admin could also look into the
max_connectionssettings to see if tweaking them helps your situation.June 4, 2016 at 8:54 am #6017
I have moved to a larger package with the host. It is a cloud business plan.
- 2x 3.0GHz CPU
- 2GB DDR3 RAM
- 40GB Disk Space
- 5TB Bandwidth
The issue is still not resolved.
The theme developer wrote the following below. It is not PHP 7 and still a problem. I had disabled all of the plugins but not every buddypress plugin yet to look for the issue. Any suggestions would be helpful.
I did a check on the regular page and saw that the memory usage stays the same no matter which theme I used, which means the issue is not with the theme but on the plugins or possibly the database.
The current memory usage of your site’s homepage is 76MB. I ran WP Optimize and I was able to get this down to 72MB. A ‘healthy’ WordPress installation actually only has around 20MB. This means that your site/server will bog down with only a few concurrent connections.
With all the plugins disabled, memory usage goes down to 26MB. With all ACODA plugins enabled plus Visual Composer, memory usage goes to 32MB. This means the remaining 40MB++ are from the other plugins you are using. You will need to trim down the number of plugins you are using by removing non-essential plugins.
One great first step you can consider is to ask your hosting team to update the PHP version you are using. PHP 5.6 and PHP7 are known to consume lesser memory compared to PHP 5.4. This should help lower the site’s memory usage and ho
Again, from how it looks, this is not a theme issue but an issue with a bloat on your installation and your server not being able to take that load. Hopefully what I mentioned above should help you get started in cleaning up the site.
- You must be logged in to reply to this topic.