There errors were emailed to me today, but when I went to the site everything seemed fine. I had the same error come through a few minutes later, and haven't had a problem since. I was able to login, which requires a session. I was expecting that the session table would be corrupt or something, and that I wasn't going to be able to log in. Weird, yes?
Code:
2016-06-15 06:56:15
Error Number: 145
Table './abc/ci_sessions' is marked as crashed and should be repaired
SELECT `data`
FROM `ci_sessions`
WHERE `id` = '253a4c0e419de9100b8e881eeee504b91f106c0d'
AND `ip_address` = '51.255.65.4'
Filename: libraries/Session/drivers/Session_database_driver.php
Line Number: 166
Request URI: /abc
2016-06-15 06:56:15
Error Number: 145
Table './abc/ci_sessions' is marked as crashed and should be repaired
INSERT INTO `ci_sessions` (`id`, `ip_address`, `timestamp`, `data`) VALUES ('253a4c0e419de9100b8e881eeee504b91f106c0d', '51.255.65.4', 1466042175, '')
Filename: libraries/Session/drivers/Session_database_driver.php
Line Number: 233
Request URI: /abc
Table is standard issue:
Code:
--
-- Table structure for table `ci_sessions`
--
CREATE TABLE IF NOT EXISTS `ci_sessions` (
`id` varchar(40) COLLATE utf8_unicode_ci NOT NULL,
`ip_address` varchar(45) COLLATE utf8_unicode_ci NOT NULL,
`timestamp` int(10) unsigned NOT NULL DEFAULT '0',
`data` blob NOT NULL,
PRIMARY KEY (`id`,`ip_address`),
KEY `ci_sessions_timestamp` (`timestamp`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
Even though I wasn't personally experiencing any problems, I went into phpMyAdmin and repaired the table.
I've never seen such an error, have you? Any reason why it would happen?
