As Ken points out, the error was actually on the line number before the line number it mentions. That is typical with error messages. The error happens trying to get past line 131, so is marked as being at line 132. But the actual problem occured while trying to complete line 131.
I have had similar MySQL delays and errors on shared servers. Again, as Ken points out, the database server is often a seperate server and is also shared by a lot of sites. Any one of them could cause a problem. Growing log files in the database can also start to bog a database server down.
I had a forum that had similar slowdowns every few months and I had to call the host and have the MySQL server restarted each time. I finally gave up and moved to a different host and the problem went away.
If there are delays in doing FTP, that points away from the database server, and points more to the web server itself or a router in the system. A router problem can also cause the database errors. And if it's a router problem, the server could test out fine in-house, but have a problem getting to it from the web. |