Welcome to Geeklog, Anonymous Thursday, April 18 2024 @ 11:04 am EDT
Geeklog Forums
SQL Error with gl_sessions (with resolution).
Status: offline
kingsley
Forum User
Junior
Registered: 03/17/05
Posts: 29
This morning I went to my clubs site and there was an SQL error preventing entry to the site.
I checked the error.log file and found the following errors starting about 12 hours ago...
Tue Oct 2 20:28:05 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191370985
Tue Oct 2 20:28:57 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191371037
Tue Oct 2 20:30:26 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191371126
Tue Oct 2 20:30:50 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191371150
Tue Oct 2 20:30:55 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE remote_ip = '66.249.70.108' AND uid = 1
Tue Oct 2 20:31:00 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE remote_ip = '66.249.70.108' AND uid = 1
There were pages and pages and pages of the same incorrect key errors.
I went to phpMyAdmin to check on gl_sessions and noticed a warning that the field sess_id was set as both the Primary key and an Index key. Otherwise I could not see anything else.
I went and checked the other sites that I manage and gl_sessions was setup the same for all, all my sites are Geeklog 1.4.1. Then I went to one of my test sites and deleted the index key for sess_id and tested the site a bit with no issues. Finally I went to the site presenting the errors and deleted the index key and the site came right back up.
With all that said I would not recommend deleteing your index key on sess_id for gl_sessions without more research being done by more accomplished developers but for now, for my site this cleared up the error. I have never seen this before and have no idea how/why it started.
I would be happy to provide more information if someone has a specific question that I can answer.
-Eric
I checked the error.log file and found the following errors starting about 12 hours ago...
Text Formatted Code
07 - 1030: Got error 127 from storage engine. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191370968 Tue Oct 2 20:28:05 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191370985
Tue Oct 2 20:28:57 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191371037
Tue Oct 2 20:30:26 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191371126
Tue Oct 2 20:30:50 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE uid = 1 AND start_time < 1191371150
Tue Oct 2 20:30:55 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE remote_ip = '66.249.70.108' AND uid = 1
Tue Oct 2 20:31:00 2007 - 1034: Incorrect key file for table 'gl_sessions'; try to repair it. SQL in question: DELETE FROM gl_sessions WHERE remote_ip = '66.249.70.108' AND uid = 1
There were pages and pages and pages of the same incorrect key errors.
I went to phpMyAdmin to check on gl_sessions and noticed a warning that the field sess_id was set as both the Primary key and an Index key. Otherwise I could not see anything else.
I went and checked the other sites that I manage and gl_sessions was setup the same for all, all my sites are Geeklog 1.4.1. Then I went to one of my test sites and deleted the index key for sess_id and tested the site a bit with no issues. Finally I went to the site presenting the errors and deleted the index key and the site came right back up.
With all that said I would not recommend deleteing your index key on sess_id for gl_sessions without more research being done by more accomplished developers but for now, for my site this cleared up the error. I have never seen this before and have no idea how/why it started.
I would be happy to provide more information if someone has a specific question that I can answer.
-Eric
5
7
Quote
All times are EDT. The time is now 11:04 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content