I would expect to see an error as well, but something was triggered to cause the email to be sent so I have to assume there was a problem.
In conjuction with all the different timeouts they are seeing on the different domains and different apps from the same servers I would have to also assume there is a real problem.
I trust them and believe they are not just making things up. They don’t have time for that and neither do I.
Perhaps I am misunderstanding you, because it sounds like I am being told there isn’t any issue.
Can you monitor it for next few hours from here and let me know if you see the issue again?
Disabled a script searching in more than 17 million rows and can easily return 8 million rows.
Well… it all depends on the client… she updates and examines the sites during certain periods. I don’t know if she will be doing anything with it over the next few hours.
As said earlier, i disabled a script, to be specific on web4. But there still havent been no other report related to MySQL3. Maybe this just helps with your problem.
Ok… well she isn’t on WEB4 so I assume you think there is a possiblity of the script on WEB4 causing an issue on MYSQL3 that we are seeing on her site.
yes, you are correct with your assumption. I cant find anything more going wrong on MySQL3. Even with this going, MySQL3 wasnt doing bad(no issue reported on our per min check or any other customer in problem), but your issue will confirm if it really had more effect.
We may need to look in other directions if this doesn helps.
Ok… we have another timeout error. She confirmed it took around 30 seconds on the www.sleepyblogger.com site and all she was doing was loading the home page of www.sleepyblogger.com . No posting… just pulling up the site.
The error specifically said “Error establishing a database connection”.
This either means that the username and password information in your wp-config.php file is incorrect or we can’t contact the database server at 204.14.104.150. This could mean your host’s database server is down…
Guys this is continuing to happen. She said it took about 20 to 30 seconds to get this error (but she wasn’t using a stop watch).
I need to know if there is a way to move her to a different mySQL server???
She is getting quite fed up with this as all of the errors seem to indicated timeout’s or problems with the database. Occasionaly she gets the 404, but the 404 is the rare one.
In ALL cases she simply hits the refresh or the go button again in the browser and then it works as it should right away.
Well… actually I want to the problem found and a resolution, but if a resolution could not be found I was asking what would it take to move it… I wasn’t quite yet asking to move it. I wanted to know the options first.
This client has a lot of stuff and also has some DNN sites so it would be pretty complex to move everything they have SO… at this point I need someone to focus on this and find a resolution.
Obviously there has been timeouts taking place that make no sense. Is there a way to put some sort of monitoring on the mySQL server to report when it timesout?
I just need to find a fix… I cannot have the customer contact me everyday saying it did it again.
Deepak said he maid some changes in my ticket… not sure what those were, but we shall see.
Deepak isnt on shift. He will update your ticket about changes when back. I have also added a per-min check for “http://problogwriters.com/administrator/” and will look back at results in next 14 hours. Sorry i wasnt around for a few days to help on this issue and meanwhile the reseller again enabled the script i disabled on web4 without notifying us.
Not sure what script you are talking about… but just wanted to give an update that we have another mySQL timeout. I can’t say which page, but just one of the normal pages on that site. Nothing should be taking that long…plus there is very little data on this particular one.
My client is starting to hear things from her client. She is starting to lose patience.
