Discussion of general topics related to the new version and its place in the world. Don't discuss new features, report bugs, ask for support, et cetera. Don't use this to spam for other boards or attack those boards!
Forum rules
Discussion of general topics related to the new release and its place in the world. Don't discuss new features, report bugs, ask for support, et cetera. Don't use this to spam for other boards or attack those boards!
We have had this error a couple of times since we updated to phpBB3 and I am wondering if anybody on here has a solution for us.
1040 SQL Error.jpg (42.12 KiB) Viewed 24350 times
We are aware, from a topic on the phpBB forums, that other people are having the problem. In addition, the phpBB main board seems to have had this problem at some stage.
The main support board at phpbb.com is the place to ask.
But....
It's purely a hosting issue. You're on a shared server and the total number of connections for all the sites on it is going over a preset value. Ask your hosts to move you to a quieter server or up the limit.
Although the general reply from you guys is its a server problem,
I also disagree,
We are using a dedicated server, serving about 5000 users, only 30 or so are online at any one time
We have reduced the timeout for the SQL down to 40 seconds, however, PHPBB3 seems to open connections so fast, the server sometimes cant close them fast enough
I agree this is a bug, and when reported as such, we are all getting the same response,
Generally, the email MX and blackhole list check can consume a lot of time if the connection can't be established, resulting in the connection "waiting" and then closing before phpBB gets to close the connection.
We tried to disable the two "blacklists", on the two differents (physical) servers we're getting the problem (one has two phpbb3 boards, the other one only). Actually the IP list was already disabled and we disabled the MX one.
We did this sunday afternoon.
The problem arrised again on the server with the single board.
Next try (just set it up) is to lower mysql timeout.
We limited the SQL timeout to 20 seconds on one server (the one with one forum only), it's ok.
OTOH, we did not limit the timeout on the second one (the one with two fora) and we got three "too many connections" during the week-end 8-(
This also occurs with forum. It seems overload at mysql database. This occurs mainly after updating the index of searching through the fulltext native. Sometimes solves re-synchronizing.
See it, for example:
