Not sure where to post this one. Apparently in a site we have developed for a customer, someone attempted to backup the site improperly. Having completed only a partial backup, he then attempted to back up the MySql database directly, and then at the same time tried to login multiple times into the CMS.
At least that is the story we are getting. Also, it is quite likely that other administrators were attempting to update the site as this person did not notify any other users that he was backing up the site. BAD IDEA I know.

So now we are getting the following error when trying to access the site:

Fatal error: Duplicate entry 'a49ef584a2d735691e7bdf023f6a1ea0' for key 1 query: INSERT INTO sessions (sid, uid, hostname, timestamp) VALUES ('a49ef584a2d735691e7bdf023f6a1ea0', 0, '68.14.4.84', 1140569082) in /home/stmicha/public_html/includes/database.mysql.inc on line 66

Can anyone out there direct me in trouble shooting this. I'm not sure where to begin. As I said we don't have a reliable backup to go back to at this point.

The URL for the site is http://www.stmichaelscountryday.org/

Thanks.

M

Comments

gonzocoder’s picture

Although the error isn't identical, this post may help as the problem seems to be with the sessions table.

http://drupal.org/node/25418

idrawcoolstuff’s picture

But, where do I put this command?
REPAIR TABLE sessions QUICK;

I'm incredibly new to MySql and PHP Admin. Thnx

MB

helsinki’s picture

You need to open up phpMyAdmin in your MySQL Databases screen (via Cpanel if you're using it). Then select the database with the _drpl1 suffix and then select the 'sql' tab at the top of the page. A small text box will appear where you can paste in your sql command. Press 'go' and it should report whether it has successfully executed the command. Then try reloading your site.
_____________________
http://www.wilba.org

idrawcoolstuff’s picture

Ran the command properly, but it didn't fix the problem. Bummer!
Hmmm... what to do next?

MB

idrawcoolstuff’s picture

Thanks for all your help. Used REPAIR TABLE sessions QUICK;
and it worked finally.:)

MB