Can not log into site anymore
Permalink
I am getting the following error when trying to log into one of my clients sites (this just started happending):
mysql error: [1030: Got error -1 from storage engine] in EXECUTE("update Users set uLastLogin = 1343764934, uPreviousLogin = '1336142601', uNumLogins = uNumLogins + 1 where uID = '1'")
No one seems to be able to login anymore...
mysql error: [1030: Got error -1 from storage engine] in EXECUTE("update Users set uLastLogin = 1343764934, uPreviousLogin = '1336142601', uNumLogins = uNumLogins + 1 where uID = '1'")
No one seems to be able to login anymore...
Has anyone else run into this issue?
Can't say I've run into this, but from cPanel, check and repair you database, clear your cache and try again.
Is it a MySQL or a InnoDB error?
If its InnoDB a quick google revealed the following:http://stackoverflow.com/questions/9595852/mysql-got-error-1-from-s...
See if that helps you :-)
Job.
If its InnoDB a quick google revealed the following:http://stackoverflow.com/questions/9595852/mysql-got-error-1-from-s...
See if that helps you :-)
Job.
It's a InnoDB error... but, I have no experience with working with InnoDB (never even heard of it before now). This issue is also hard to deal with since the client setup their own DB and won't allow my access, even though I built the site... Anyways, here is a snippet of the mySQL error log that they ran:
120809 16:43:17 [Note] Plugin 'FEDERATED' is disabled. 120809 16:43:17 InnoDB: The InnoDB memory heap is disabled 120809 16:43:17 InnoDB: Mutexes and rw_locks use Windows interlocked functions 120809 16:43:17 InnoDB: Compressed tables use zlib 1.2.3 120809 16:43:17 InnoDB: Initializing buffer pool, size = 339.0M 120809 16:43:17 InnoDB: Completed initialization of buffer pool 120809 16:43:17 InnoDB: highest supported file format is Barracuda. 120809 16:43:17 InnoDB: Error: page 2 log sequence number 19189931 InnoDB: is in the future! Current system log sequence number 17911278. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information. 120809 16:43:17 InnoDB: Error: page 11 log sequence number 19189931 InnoDB: is in the future! Current system log sequence number 17911278.
Viewing 15 lines of 25 lines. View entire code block.
I found some info on that type of InnoDB table corruption:
http://advikasingh.hubpages.com/hub/Resolving-Your-database-may-be-...
To fix it I think you will need full root access to the MySQL server to either reload the damaged log table from backup, or clear and reinitialize it. I would be suscpicious of a hardware (memory or bad hard drive) issue also. NOT FUN!
http://advikasingh.hubpages.com/hub/Resolving-Your-database-may-be-...
To fix it I think you will need full root access to the MySQL server to either reload the damaged log table from backup, or clear and reinitialize it. I would be suscpicious of a hardware (memory or bad hard drive) issue also. NOT FUN!
Hi!
I get this error which started happening after I upgraded to 5.6.0.
mysql error: [1264: Out of range value for column 'uLastIP' at row 1] in EXECUTE("update Users set uLastIP = -1062723327, uLastLogin = 1346314592, uPreviousLogin = '0', uNumLogins = uNumLogins + 1 where uID = '1'")
Any ideas how to fix this?
I get this error which started happening after I upgraded to 5.6.0.
mysql error: [1264: Out of range value for column 'uLastIP' at row 1] in EXECUTE("update Users set uLastIP = -1062723327, uLastLogin = 1346314592, uPreviousLogin = '0', uNumLogins = uNumLogins + 1 where uID = '1'")
Any ideas how to fix this?
I got it to work by changing field type for uLastIP from INT(10) to VARCHAR(20). Not sure if this is a "good" solution but it works so far.
