My invision board stopped working

[panzerkw]

Click here (http://ifdg.fsmagazine.nl/forum/) to see the problem. Any idea what might be causing this? I have no idea :confused:

[Mancabus]

Your link doesn't work.

Been meaning to tell you this panzer, your fedex banner wants to give me a cookie. Why is it trying to give me a cookie?

Edit: Oops wasn't paying attention to where I was. I know no coding

[Shorty]

IVB uses session data to store last visits. It is trying to access the session table to find an entry, then delete row and insert a new row listing the latest visit.

You have a problem with IVB connecting to the SQL database.

Either the db has got corrupted, the db server is offline, the db authorisation has changed (and your haven't updated your config to reflect the change) or the whole db has died a death.

Id place my bet on the db server being offline or the db is corrupted :(

Check with your host :)

[Park_7677]

My friend's IPB did this all the time.. Corrupted database it was..

Never found out how to stop it from doing it..

[Shorty]

Check with the host and see what version of MySQL they are running. If it is 4.0.12.. then read this..

http://www.vbulletin.com/forum/showthread.php?t=69803

Please note that although the above advisory is for VBulletin customers, this can affect ALL PHP/MySQL applications using 4.0.12..

Especially as Panz's error is specifying 'ibf_sessions.MYI' which is part of the MyISAM table type, I would agree with Park's thoughts on corrupt database/table.

[Park_7677]

cd "/path/to/mysql/bin"
mysqlcheck -uUSER -pPASSWORD -r DATABASE_NAME

If you have access the the server, running the above will repair the error.. loss of data is questionable.

Good luck :thumbsup:

[panzerkw]

Alright I'll try that, hopefully nothing gets lost (crosses fingers)

[AuthorityAction]

I'm parks friend that had the DB error just like that.

I got that error when i ran it on windows. i just switched to linux and got the same error today after having it run for a couple days. I stopped mySQL and started it back and and it seems to be fine. I'd try doing that and repairing the DB.

[panzerkw]

edit: nvm