Hello.
I am new to all this web stuff so forgive my ignorance.
Every time I access the site a message comes up written 'Critical SQL problem!' I dont know what is it. It looks like it is everiting fine with MySQL and with the config. what should I do?
Thanks.
Chaves.
It pretty much means everything isn't fine with MySQL and the config. Go back and test some more.
I'm getting the Critical SQL problem! error on one of my boards now too.. out of nowhere.
What else could cause this other than a messed up config? My config is all in order so I don't know what it could be.
>>5
What would cause messed up SQL? Do you mean SQL data or messed up mySQL install? SQL SQL SQL SQL SQL SQL SQL SQL? SQL SQL SQL SQL.
Now all of my boards are giving me the critical SQL problem error when trying to login to the management panel. That is the only time I get the error. Halp pls.
>>7 Have you tried posting? SQL meltdowns should effect all parts of the board.
>>8
Posting works just fine. I think some syntax has subtly changed when they updated DBI on our server (we're on dreamhost.) All of the moderation things work except for the management panel. ie we can check the ban list/proxy list etc etc etc
>>9
This is very strange. I have a Wakaba 3.0.7 board set up on Dreamhost and the management panel works fine.
Not sure if you've changed anything in Wakaba itself, but for what it's worth, Dreamhost's DBI configuration doesn't seem to accept quoted integers as part of a LIMIT clause anymore. If you've added any LIMIT clauses to the SQL queries Wakaba makes, don't use "LIMIT ?, ?" to insert the values. Verify the values you want and insert them directly into the SQL string.
>>10
Yeah, it had everything to do with the modifications we made to wakaba. In particular, it was something we changed in trim_database.
In connection with this problem, an extended error message appears in the Administration Area, when entering it on the right time:
Critical SQL problem! database table is locked(1) at dbdimp.c line 401
It seems, that the database table is beeing "locked" after the first post. The second poster already gets the 'Critical SQL problem' error.
Additionally, a new file appears in the wakaba directory, named 'wakaba.sql-journal', it contains no useful data.
Sounds like the database is not getting properly closed. No idea why, though.