I recently switched from using mySQL 4.1.21-standard on my system to using mySQL 5.0.27-standard; selected version 5 in the 'tweak settings' dialog in WHM, ran 'Software/Update Server Software' in WHM *and* ran /scripts/mysqlup. Also ran easyapache and rebuilt Apache. Rebooted the system.
I am now getting a very weird bug. I can run mysql's client when the system first boots up, and my old databases and tables all seem to be there. However, apart from the tables in the 'mysql' DB, all the others seem to be 'corrupted'. When I try to select them, i get one of three errors:
- ERROR 1017 (HY000): Can't find file: '(table name)' (errno: 2)
- ERROR 1146 (42S02): Table '(table name)' doesn't exist
- ERROR 1033 (HY000): Incorrect information in file: ./(whatever).frm
So, catastrophic database corruption, I thought. I was getting ready to jettison the whole lot and restore from backup when I restarted the mySQL daemon via WHM, and suddenly everything worked. I've repeated this process a few times (reboot, access, restart daemon, access) and it keeps happening. The errors occur until I restart the mySQL daemon and then it works fine. These errors only seem to apply to tables that were created before I switched to mySQL 5 - tables that I create now are accessible the first time the daemon loads up and don't cause errors.
Does anyone have any idea what might be causing this? It sure has baffled me. The data from the 'old' tables is clearly there, and working fine, but I'd rather not have to restart the mySQL daemon every time after I reboot for it to work!!
I am now getting a very weird bug. I can run mysql's client when the system first boots up, and my old databases and tables all seem to be there. However, apart from the tables in the 'mysql' DB, all the others seem to be 'corrupted'. When I try to select them, i get one of three errors:
- ERROR 1017 (HY000): Can't find file: '(table name)' (errno: 2)
- ERROR 1146 (42S02): Table '(table name)' doesn't exist
- ERROR 1033 (HY000): Incorrect information in file: ./(whatever).frm
So, catastrophic database corruption, I thought. I was getting ready to jettison the whole lot and restore from backup when I restarted the mySQL daemon via WHM, and suddenly everything worked. I've repeated this process a few times (reboot, access, restart daemon, access) and it keeps happening. The errors occur until I restart the mySQL daemon and then it works fine. These errors only seem to apply to tables that were created before I switched to mySQL 5 - tables that I create now are accessible the first time the daemon loads up and don't cause errors.
Does anyone have any idea what might be causing this? It sure has baffled me. The data from the 'old' tables is clearly there, and working fine, but I'd rather not have to restart the mySQL daemon every time after I reboot for it to work!!
Last edited:
