
Originally Posted by
RodG
You must have given your hosting company different information than you have given us. Either that, or they are feeding you BS, because the log entry provided doesn't indicate which table is being accessed, therefore they can't possibly say its the only one.
I've given them several things - I started with the connect-fail entry and have through several email tried to explain things I've tried - to help find the problem.
Besides that, the error log provided clearly show that it is an issue connecting to the *database* and until it an do this it has no way of accessing ANY of the *tables*.
Who is "I" in this case? You or someone from the hosting company?
I = me
Nothing particularly unusual here. There are many possible causes. eg: Client gone away, code not correctly closing the tables after use, Server overloaded.
Well one thing - one of the tables (pizza) complains that a table wasn't closed. But "pizza" is a test DB and is only used by me from the command line and the last time .... was ... 6 months ago???
Do you have a reason for thinking this? What?
See the above comment
Nothing unusual here.
It does mean that if the server doesn't allow remote access, and MANY don't. Thanks to a Nasty Miscrosoft bug *many* years a ago many hosts consider this as too much of a security risk (something that I don't agree with, its more secure than FTP, which all hosts seem to allow without a seconf thought).
I have remote access. echo "select...." | mysql -u me ..... -h remoteserver.com
Or perhaps even a search engine (if the host isn't up to handling the traffic).
Hmmmm hmmmmmmmmm have to look in to that
Sound to me like the MySQL server can't handle what is being asked of it.
My thoughs. I can't see the logs (if any) - though I could write a script, mysqlcheck, log not-closed. Then check against Apache logs. I've got a bot scan and a error at the same time???
It isn't for you (or me) to give a hosting company any direction or argument. They will have logs to indicate these server errors and it is really up to them to find the cause and solution. All you can really do is try to keep track of when it occurs and keep submitting fault reports.
Hmmm I hear you but... I spent 12 years as 4th level support, 1st level had a 3 ring binder and got paid $12/hr. 2d level had training and were pretty smart $x2. 3d didn't exist. Then there was my group, had acccess to code & programmers and were expected to track and solve everything right down to telling the programmers what the code error was. I remember one of the last problems "2d: Box E47 won't process, we've tried everything - even reboot." me: "hmmm, click, type, click, check Do a 'df'" 2d: "S***!!" One of the disks had filled, 1st missed it, 2d missed it. I'm not sure where my hosting support falls, really sharp on some things, had never heard of COPS. And DB problems they had off.
Cheers
RodG