Seems things have returned. Anyone still have problems try PMing someone.
Well THIS is just weird!
Started by Urtheart, Jul 13 2009 08:27 AM
4 replies to this topic
#1
Posted 13 July 2009 - 08:27 AM
#2
Posted 13 July 2009 - 01:06 PM
Just for the record. That's usually what the IPS Driver Error page means.The database tables are automatically repaired every three hours - I can't repair it from my end. It looks as though our posts database is corrupted however, so it'll have to be restored by either Dreadknux or Bmn in the morning.
#3
Posted 13 July 2009 - 01:52 PM
Chris, assuming that the MySQL server itself isn't broked, and the server isn't clogged, you should be able to do the repair job through the details I sent a while back.
FTR, the "IPS Driver" (rather, an IPS driver) in question is a class (a framework that you use in the code to do tasks relating to a particular thing) used to translate generic database instructions into code and run them in the appropriate database. To illustrate, imagine IPB using a function such as DB::fetchLatestPosts(). This doesn't distinguish between MySQL, pgSQL, MSSQL etc. Each particular database will have its own "driver" for IPB to make these generic functions work despite the differences in each database server, and in this case it's the MySQL driver that's being used.
As for the error itself, it just means that the driver reported an unrecoverable problem in using the database. The actual error is logged for admin use only, for security reasons, but in the current situation it usually means either the server application is down (which takes out everything on the server that uses a database), or one or more of the tables is corrupted and needs to be repaired. Normally it's the sessions table (which keeps track of who's logged in, this takes out the whole forum); occasionally it's the posts table (and sometimes one or two posts are lost repairing it), sometimes topics, though that's rare.
FTR, the "IPS Driver" (rather, an IPS driver) in question is a class (a framework that you use in the code to do tasks relating to a particular thing) used to translate generic database instructions into code and run them in the appropriate database. To illustrate, imagine IPB using a function such as DB::fetchLatestPosts(). This doesn't distinguish between MySQL, pgSQL, MSSQL etc. Each particular database will have its own "driver" for IPB to make these generic functions work despite the differences in each database server, and in this case it's the MySQL driver that's being used.
As for the error itself, it just means that the driver reported an unrecoverable problem in using the database. The actual error is logged for admin use only, for security reasons, but in the current situation it usually means either the server application is down (which takes out everything on the server that uses a database), or one or more of the tables is corrupted and needs to be repaired. Normally it's the sessions table (which keeps track of who's logged in, this takes out the whole forum); occasionally it's the posts table (and sometimes one or two posts are lost repairing it), sometimes topics, though that's rare.
#4
Posted 13 July 2009 - 02:40 PM
So that's why my Topic didn't get posted!
#5
Posted 13 July 2009 - 06:06 PM
Oh, good, things are back to normal. For a while there I was thinking "Oh noes, Epic sabotage!!1!" *Phew*
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users














