Support Forum
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...
Visit Cruise Talk Central and Mr Papa's World
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...
Visit Cruise Talk Central and Mr Papa's World
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?
Visit Cruise Talk Central and Mr Papa's World
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...
Visit Cruise Talk Central and Mr Papa's World
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...
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)