and it you run the wp debug bar plugin (assumes you have wp admin bar stil running), all the wp debug stuff is hidden and not show on the site..
I have never disabled error logging before, but lets try this… in file sp-site-support-functions.php, around line 161 find and comment out this code:
$wpdb->hide_errors();
set_error_handler(‘sp_construct_php_error’);
comment out both lines…
and lets see what that does… you may just get a php or db error that halts execution, but maybe we can know the true error then…
Mr Papa said
I have never disabled error logging before, but lets try this… in file sp-site-support-functions.php, around line 161 find and comment out this code:$wpdb->hide_errors();
set_error_handler(‘sp_construct_php_error’);comment out both lines…
and lets see what that does… you may just get a php or db error that halts execution, but maybe we can know the true error then…
Commenting these 2 lines fixed my problem and forum is back, I can also mention I don’t have “SHOW TABLES LIKE ‘wp_sferrorlog'” in my mysql processlist anymore.
I’ll keep monitoring my site but so far it looks fine. That’s a few hours downtime and my forum members won’t like it, so I’d wait a better until things cool down to try patches if you have some you want me to try.
Thanks for your help, I guess in the future, I shouldn’t deploy new versions the day they are released and wait for other users feedback.
Cheers.
well, there are already many hundreds of updates to this version already with no issue… and we do dozens of test site installs before release.. but of course we cannot replicate every server set up out there… just need to understand what is going on locally for you…
currently, barring any more data as to what is causing the error logging to kick in, I have no patches for you to try… maybe Andy will have some more suggestions since he is the error logging guy…
at some point, it would be interesting to uncomment those two lines out and see if the problem returns… would tell if it was an update/upgrade issue vs general issue…
I guess a good starting point would be to know if the host can see anything the matter with the SHOW query. If that itself were causing an error then that could loop. But that doesn’t make any sense of the error log entries which are frankly bizarre…
I just logged in mysql command line tool using the same db account that is configured on WP and ran:
mysql> SHOW TABLES LIKE ‘wp_sferrorlog’;
+—————————————+
| Tables_in_xxxxxxx (wp_sferrorlog) |
+—————————————+
| wp_sferrorlog |
+—————————————+
1 row in set (0.00 sec)
It seems the problem is somewhere else 
just need to know the error that started it… as mentioned, should be in the php error log… 
did you try uncommenting those two lines? curious to see if it was just an upgrade issue…
I just tried removing the comments on the 2 lines, my forum gets locked in the next second.
I’m adding again the comments and leave it like this for the moment, will later try to get more details about a php error when there is less traffic on my forum.
Cheers.
okay, thanks for the test. still a unique issue so would love to know what is causing the initial error to get the log spinning away – as I am sure you would too…
well, good news and bad news… good news, another user is having what appears to be same user… so two now (out of thousands of upgrades) but means its non unique… bad news, we still have no idea what’s going on…
So at this point, to troubleshoot further, we really need to be able to debug on the actual server where its occurring… if this is a live server, that may not be possible without some disruption (have to turn error logging back on)… is that possible here? or do you have a staging server with the same issue?
Well that’s good news for me, sort of I really feel less alone with that issue.
I’ve already brought you some pointers on the problem, that should help you to backtrack the cause checking the changed source code between current SP update and previous version.
I currently don’t have a staging server, but a few members not happy about my forum being inaccessible half a day yesterday so I’ll give some time to check again on the issue, I just can’t take my forum down too often.
Cheers.
understand… the other user has provided credentials so will be able to debug over there… unfortunately, none of the provided info has been useful in understanding the problem…. just need to get access to the problem and chase it down which we should be able to do now…
just an update, but the other user’s issue is solved… he disabled the error logging to get site back… but re-enabling the error logging worked just fine with no repeat of errors… we tried that on yours but the errors came back… so we are still back at square zero as we have no real leads as to the initial problem…
of course, still investigating…