Skip to main content

[CPANEL-31773] RoundCube DATABASE ERROR: CONNECTION FAILED after cPanel update to 86.0.8

Comments

4 comments

  • cPanelLauren
    Hello, This issue is related to an internal case in which Roundcube using MySQL as opposed to SQLite fails after the update to v86. The internal case ID is CPANEL-31773 and the current workaround for it is one of the following: Known workaround(s) Alter roundcube tables to use InnoDB storage
    mysql roundcube -e "drop table carddav_migrations"; unalias ls; for each in `ls -1 /var/lib/mysql/roundcube/ |cut -d"." -f1 |uniq |grep -v db`; do mysql roundcube -e "alter table $each ENGINE=INNODB;";done
    OR Edit File below to remove ENGINE=INNODB lines from each table creation query.
    /usr/local/cpanel/base/3rdparty/roundcube/plugins/carddav/dbmigrations/0000-dbinit/mysql.sql
    Then, create a new login session for Roundcube to observe the tables get created as expected. Alternatively you could also convert to SQLite which is the preferred storage format:
    0
  • GuntherR
    Thanks Lauren, Changed RoundCube tables to INNODB after troubleshooting with cPanel Tony and all is working fine again. Might consider changing to SQLite at a later time. Unfortunately the impact of this automatic update (86.0.8) was a full day without RoundCube for 100+ users. Would have been nice to find a INNODB comment in one of the update log files. Glad it's back online again.
    0
  • cPanelLauren
    Hi @GuntherR I'm glad you got it resolved.
    Would have been nice to find a INNODB comment in one of the update log files.

    I think, more to that, it would have been nice if it wouldn't have happened at all, the internal case that's open for this should resolve that though.
    0
  • cPanelLauren
    As of v86.0.13, this issue is noted as being resolved. This can be confirmed by checking the changelogs here: 86 Change Log | cPanel & WHM Documentation If you're on this version of cPanel & WHM and you're still experiencing an issue please open a ticket so that we can investigate further.
    0

Please sign in to leave a comment.