By intexile@iww.org@drupal.org on

How do I fix the following error using trustix Linux:

Fatal error: Can't open file: 'sessions.MYI'. (errno: 145) query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid = s.uid WHERE s.sid = '75185a7ef66c9ff13b8d8b4f50dd7e4b' AND u.status < 3 LIMIT 0, 1 in /home/httpd/html/includes/database.mysql.inc on line 66

Comments

pnelson’s picture

pnelson commented

Fatal error: Can't open file: 'sessions.MYI'. (errno: 145) query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid = s.uid WHERE s.sid = '9cfc9952904233d7b9ba8f8b98273d6e' AND u.status < 3 LIMIT 0, 1 in /home/pnelson/public_html/k12edcom/includes/database.mysql.inc on line 66

This is what I'm getting from three different drupal sites served from my host. Any clues?

qolspony’s picture

qolspony commented

Fatal error: Table 'qolspon_bmarkf.users' doesn't exist query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid = s.uid WHERE s.sid = '27ccc4cf0dda3220ae7a00105218c1db' AND u.status < 3 LIMIT 0, 1 in /hsphere/local/home2/qolspony/brunsonmarketingforce.com/Drupa/includes/database.mysql.inc on line 66

utna’s picture

utna commented

my webpage went down, with no html response or timeout.

there were sever SQL process running the same query:

SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid = s.uid WHERE s.sid = '7bf64b151265f1453

i tried to kill them, but they persisted. Is this perhaps a cron related issue?

I deleted the database user, and recreated, and the site came back up fine.

utna’s picture

utna commented

the logs function in drupal reported that the cron user had an error:

Lost connection to MySQL server during query query: SELECT DISTINCT(p.perm) FROM role r INNER JOIN permission p ON p.rid = r.rid INNER JOIN users_roles ur ON ur.rid = r.rid WHERE ur.uid = 0 in

/home/... .../includes/database.mysql.inc on line 66.

rwreed’s picture

rwreed commented

I got this answer from another thread (thanks cyberchucktx!)

Using PhpMyAdmin I rebuilt the sessions table with the following command:

REPAIR TABLE sessions QUICK;

Rebuilt the table in less than a second and all was well afterward.

Good Luck