My server was accidentally rebooted while doing module updates and now this is what I’m left with:
FATAL ERROR
SELECT data FROM module_xml WHERE id = ‘mod_serialized’ [nativecode=1030 ** Got error 134 from storage engine]SQL -
SELECT data FROM module_xml WHERE id = ‘mod_serialized’
Trace Back
/var/www/html/admin/libraries/sql.functions.php:25 die_freepbx()
[0]: SELECT data FROM module_xml WHERE id = ‘mod_serialized’ [nativecode=1030 ** Got error 134 from storage engine]SQL - SELECT data FROM module_xml WHERE id = ‘mod_serialized’
/var/www/html/admin/libraries/modulelist.class.php:17 sql()
[0]: SELECT data FROM module_xml WHERE id = ‘mod_serialized’
[1]: getOne
The pbx system is still working. I’m able to place/receive calls. It appears only the web interface is borked so I can’t use the freepbx web interface.
How would I go about doing this repair?–should I make a php page to execute the sql code? Any advice?
When someone gives you an answer that you don’t know what it is go to Google.
If you put in “linux mysql command line database repair” you would be shocked. It’s a miracle, the answer is right before your eyes.
If you Google “fix mysql database” you will be lost. Learning to construct useful searches is imperative if you are trying to self support yourself on complex IT tasks without experience.
And, for the love of God, make a backup of the hosed DB (from said command line not FreePBX) before you start repairing your DB.