Are you getting a message from cPanel saying something like ?
check_mysql has determined that there are corrupted database tables .
cPanel & WHM has determined that the following database tables are corrupt:
Error : Table 'roundcube.contacts' doesn't exist
roundcube.identities.
Error : Table 'roundcube.identities' doesn't exist
roundcube.messages
Error : Table 'roundcube.messages' doesn't exist
roundcube.session
Error : Table 'roundcube.session' doesn't exist
The roundcube database on the server might have got corrupt. You can re-generate the database by stopping the MySQL service, moving away the corrupt ones, restarting the service and then moving ahead with updating roundcube :
# /etc/init.d/mysql stop
# mv /var/lib/mysql/roundcube/ var/lib/mysql/roundcube_bk
# /scripts/restartsrv_mysql
# /usr/local/cpanel/bin/update-roundcube --force
Once this is done, you will be able to access roundcube and the databases will be fixed !
This is a horrible idea seeing as how the Roundcube database usually contains InnoDB tables. Moving InnoDB data around, will likely result in InnoDB corruption for most, and ultimately an instability in MySQL for ALL users.
At most:
mysqladmin drop roundcube
/usr/local/cpanel/bin/update-roundcube –force
If you want to restore previous Roundcube backups, look in /var/cpanel/roundcube.
Note cPanel’s pushed Roundcube/Horde to sqlite so this will also be deprecated for all 11.50+ users.
Hey Andrei,
Thanks for the heads up !!
Just to be clear, we are not moving the db here, we are just moving it away by renaming it ( same as dropping it ) , so that when the roundcube update is forced, it creates a new db with all new tables !
Hey Andrei,
Thanks for the heads up !!
Just to be clear, we are not moving the db here, we are just moving it away by renaming it ( same as dropping it ) , so that when the roundcube update is forced, it creates a new db with all new tables !