My site seems to be dead

By venkat-rk on 15 Jan 2006 at 15:58 UTC

Just tried to log in to my site and the first strange thing I noticed was an 'Access denied' message when going to the admin page. Then I couldn't login and when I finally logged in with uid1, I still got the access denied message when visiting the admin page.

I emptied the sessions (wrong thing to do?), user_permissions and cache tables, all of which had quite a bit of overhead. Still no result. When I tried to reach the admin page after doing this, I got the following error:

Fatal error: Duplicate entry 'fcfffb08cf7831fd970f8e81737811d6' for key 1 query: INSERT INTO sessions (sid, uid, hostname, timestamp) VALUES ('fcfffb08cf7831fd970f8e81737811d6', 0, '59.144.28.109', 1137339653) in /home/domain/public_html/beta/includes/database.mysql.inc on line 66

Additionally, clean urls seem to have stopped working and I get the typical drupal urls with ?q

It was working perfectly until about 24 hours ago and the only change I added was the 'Who's new' block, which is wildly fluctuating between 2 guests, 24 guests and so on. I am using 4.6.5.

The drupal install is on a directory called 'beta'. I just confirmed that two other drupal installs at the root of my domain and in another directory work perfectly, so the problem is definitely limited to this install.

Any suggestions as to what could be wrong? This is a production site that is less than a week away from being launched. Gives me the jitters.

Comments

I did a quick search for

sepeck commented 15 January 2006 at 18:19

I did a quick search for you.
http://drupal.org/search/node/Fatal+error%3A+Duplicate+entry+

It seems a sequence order issue. Some mildly different solutions and posibilities in there.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

Thanks, Sepeck. I will look

venkat-rk commented 16 January 2006 at 01:53

Thanks, Sepeck. I will look at those solutions.

Strange

Dries commented 15 January 2006 at 18:52

Try to empty your sessions table if that problem persists.

Thanks, Dries. I did empty

venkat-rk commented 16 January 2006 at 01:59

Thanks, Dries. I did empty the sessions table. Strangely, the error started showing up only after that.

Fortunately, I had set up cron to do a database backup (with dba module) every six hours. Can I restore the site by using one of the backup files?

Try using reapir tables

sangamreddi commented 16 January 2006 at 08:34

I have deleted the sessions table and re created it, still the error shows up. I have reapired the all the tables using repair option in phpmyadmin. after that the error didn't appear again. from them onwards i am optimizing tables daily and rapairing table onc in every week. So far these errors didn't turn up again.

I think this might be useful to you.

Sunny
www.gleez.com

Yes, thanks for reminding

venkat-rk commented 16 January 2006 at 08:54

Yes, thanks for reminding me. I was thinking just a while ago that instead of emptying the sessions table, I should have repaired it. It's too late now and I am really stuck.

And, I don't seem to be alone either.
http://drupal.org/node/44919