Support Forum
Support Forum
Offline
Yellow Swordfish said
It is probably best to just ask you to do a search on the term...
But some questions....
Thanks Andy, I have been frantically researching this, and been in close contact with our server manager. We have been running the latest version of MySQL that is compatible with cPanel, and have been for some time.
The only recent changes on our site and the server were my updates last week of both SimplePress and WordPress, on the same day that we started noticing the crippling MySQL issues.
With SimplePress deactivated, all is fine. I'm hoping someone here might be able to provide some direction for further troubleshooting, or recommendations for appropriate MySQL / Apache / server config settings.
Steve? Anyone?
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Offline
After further discussion with our server manager, I've confirmed that nothing has changed on the server side.
He says...
I looked at the mysql log file and didn't see anything that stands out in recent records. My understanding is we have done all this tweaking of the conf files and, up until you did the plugin upgrade everything was running fine. And disabling the plugin made everything run fine again. So, we could futz around forever trying to find some setting that the new version of the plugin in relationship to your database might require, but given there are so many variables, I am hoping someone who has tread these waters before might give us some clues.
So with that in mind, I asked for our current my.conf file. Perhaps someone could review these settings and/or recommend any suggested changes...
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Offline
Steve made some changes to ours about a year back when we saw some of the 'gone away' messages on our server so he may recognise something perhaps. he will be back tomorrow.
I did check the last couple of updates and I see no real changes to the general mysql queries. Minor updates is all. Perhaps Steve will recognise something or have an idea.
 |
YELLOW
SWORDFISH
|
Offline
Thanks again, I'm just going crazy trying to get somewhere on this...
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Offline
As I understand things you usually in the past have updated a test rig first. Did that biot hapen this time? And if it did does that show the same issues?
Perhaps you could also conform the version you were using prior to the latest update. I can check code changes again although truth is we have no other reports at the moment of this behaviour.
|
YELLOW
SWORDFISH
|
Offline
Yellow Swordfish said
...you usually in the past have updated a test rig first. Did that biot hapen this time? And if it did does that show the same issues?
It appears that the "database has gone away" error is indeed happening on all our domains, and has been for some time. Yet it has no real adverse symptoms. I did update the test install, and it did not have issues, likely since it is not an exact mirror of the live db which is much larger.
Perhaps you could also conform the version you were using prior to the latest update.
Are you suggesting a roll-back to the previous SimplePress version? Steve recently mentioned that reverting is a bad idea.
So...
While those db errors are troubling, I don't believe they are the primary cause of spiraling loads upon SimplePress activation since they occur with the plugin off and have no apparent adverse affects on performance.
Can we please focus on addressing the following errors that I get after activating the plugin:
[03-Nov-2013 13:11:23 UTC] PHP Notice: Undefined index: forumname
[03-Nov-2013 13:11:24 UTC] PHP Notice: Undefined variable: tipSubmitButton
[03-Nov-2013 13:11:24 UTC] PHP Notice: Undefined variable: tipCancelButton
[03-Nov-2013 13:12:23 UTC] PHP Notice: Undefined index: sfnotify
Which tables should I check for these missing indexes "forumname" and "sfnotify" and what should their structure look like? Another screenshot would be very helpful if I need to recreate them. I'm also unsure what to do about those undefined variables.
Thank you!
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Offline
- Of course the 'database gone away' has adverse effects. It can stop updates mid-stream and leave the database potentially inaccurate and in conflict. Ity really does need to be dealt with to maintain a healthy system.
- No - I am not suggesting a roll back. I wanted to know the last version you were using before the last update and would still like to know.
- I see little point on focusing on unimportant and inconsequential php notices when you have more important issues to resolve. I think we have explained before - notices are just that - something that does not effect processing and are just - well - a notice. They are a nuisance. Although they can sometimes suggest unexpected data being returned form the database.
|
YELLOW
SWORDFISH
|
Offline
also, lets be sure we are not confusing php undefined indexes with mysql indexes (mentioned earlier)... they are totally unrelated and completely different... you wont find the php notices by looking at mysql tables...
as Andy says, a php notice is a nuisance - a super minor code issue that 99.9% of the time has no impact on results...
take the forumname for example... cause by something like
$test = $forumname; // (over simplified but hopefully explains;
the php notice is thrown because $forumname does not exist or has not been initialized... so $test becomes empty... in this super simple case, $forumname should have been initialized with say an empty string
$forumname = '';
well, guess what... php takes care of anyways... and in my example, $test would get set to the empty string or other empty condition anyways... so no harm no foul...
php throws the notice to let you know that $forumname was not defined... useful in the case that the variable name should have $forumnames (or other)... lol, in order to make php happy, you end up with an awful lot of code that does nothing but make php quit complaining...
but again... php notices have NOTHING to do with mysql and table indexes...
Visit Cruise Talk Central and Mr Papa's World
Offline
Yellow Swordfish said
- Of course the 'database gone away' has adverse effects....It really does need to be dealt with
Yup, we're researching and working frantically to do just that.
- No - I am not suggesting a roll back. I wanted to know the last version you were using before the last update and would still like to know.
Thanks for the clarification. All was working well with SimplePress v5.3.3. Immediately after updating to v5.3.4 MySQL processes and server loads increase rapidly upon plugin activation.
- I see little point on focusing on unimportant and inconsequential php notices
Sorry, I realized after that last post that those were the same notices I posted earlier.
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Offline
Mr Papa said
again... php notices have NOTHING to do with mysql and table indexes...
Understood, thank you.
Steve, could you please review our my.conf settings I posted above to see if anything looks out of order for a site running forums of our size? I'd love to hear if you have any recommendations for configuring MySQL and/or Apache. Please feel free to PM me if you're willing and able to take this troubleshooting on under paid contract.
I have involved our host's server/db tech but am not getting anywhere so far. Since the site-crippling symptoms only occur when activating the plugin, the suggestion is to disable the plugin which we need to get reactivated successfully, and soon.
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
All RSS1 Guest(s)