Skip to main content

Horde upgrade totally failed, all settings gone

Comments

2 comments

  • lorio
    There seem to be many converting problems with horde from MySQL to sqlite. Unusual for the stable branch. I got only empty sqlite databases on all accounts on all servers. Trying to convert every acount via console didn't worked either. /usr/local/cpanel/3rdparty/bin/perl -MCpanel::Horde::MySQLToSQLite -e 'Cpanel::Horde::MySQLToSQLite->new->convert_user("cpanelaccountname")'
    ends with a "Recieved SIGPIPE while converting data for " The first error in the logfile of the first mysql->sqlite converting via upcp was this ### BEGIN ERROR: Failed the next statement with error: #DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(forward_owner))' at line 1 # at /usr/local/cpanel/Cpanel/Exception.pm line 151. # Cpanel::Exception::new("Cpanel::Exception::Database::Error", Cpanel::ExceptionMessage::Raw=SCALAR(0x2368470), HASH(0x3d9b7e8)) called at /usr/local/cpanel/Cpanel/Exception.pm line 57 # Cpanel::Exception::create("Database::Error", Cpanel::ExceptionMessage::Raw=SCALAR(0x2368470), HASH(0x3d9b7e8)) called at /usr/local/cpanel/Cpanel/Exception.pm line 72 # Cpanel::Exception::create_raw("Database::Error", "DBD::mysql::db do failed: You have an error in your SQL synta"..., HASH(0x3d9b7e8)) called at /usr/local/cpanel/Cpanel/DBI.pm line 105 # Cpanel::DBI::_create_exception(Cpanel::DBI::Mysql::db=HASH(0x3d98f80), "DBD::mysql::db do failed: You have an error in your SQL synta"..., undef) called at /usr/local/cpanel/Cpanel/DBI.pm line 93 # Cpanel::DBI::_error_handler("DBD::mysql::db do failed: You have an error in your SQL synta"..., Cpanel::DBI::Mysql::db=HASH(0x3d98f80), undef) called at /usr/local/cpanel/Cpanel/Horde/RepairSchema.pm line 280 # eval {...} called at /usr/local/cpanel/Cpanel/Horde/RepairSchema.pm line 280 # Cpanel::Horde::RepairSchema::_write_patch(Cpanel::Horde::RepairSchema=HASH(0x3d7b0c0), "## mysqldiff 0.43\x{a}## \x{a}## Run on Fri Jul 24 23:07:32 2015\x{a}##\x{a}#"..., "PATCH 1") called at /usr/local/cpanel/Cpanel/Horde/RepairSchema.pm line 110 # Cpanel::Horde::RepairSchema::repair_horde_1148_mysql(Cpanel::Horde::RepairSchema=HASH(0x3d7b0c0)) called at /usr/local/cpanel/scripts/horde_mysqltosqlite line 223 # main::check_and_fix_1148_schema(HASH(0x2300d90)) called at /usr/local/cpanel/scripts/horde_mysqltosqlite line 128 # main::run("main", "--replace-dest-db") called at /usr/local/cpanel/scripts/horde_mysqltosqlite line 34 # main::try {...} () called at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/Try/Tiny.pm line 81 # eval {...} called at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/Try/Tiny.pm line 72 # Try::Tiny::try(CODE(0x3cf9a58), Try::Tiny::Catch=REF(0x247f6e8)) called at /usr/local/cpanel/scripts/horde_mysqltosqlite line 41 # main::_run("--replace-dest-db") called at /usr/local/cpanel/scripts/horde_mysqltosqlite line 45 ALTER TABLE ingo_forwards ADD INDEX ((forward_owner)) ### END ERROR
    Trying to to the complete converting via console /scripts/horde_mysqltosqlite
    didn't worked either. When the first conversion via ucpcp was applied the logfile shows [horde_mysqltosqlite] Backing up the pre-11.50 MySQL Horde database. [horde_mysqltosqlite] Backup of the pre-11.50 MySQL Horde database. The backup is available at: /var/cpanel/horde/horde.backup.sql.final [horde_mysqltosqlite] The horde database schema does not match the pristine 11.48 horde schema. Attempting to repair it. [horde_mysqltosqlite] The conversion of Horde MySQL data to SQLite failed: Failed to run the patch, PATCH 1, to horde with with the following errors:
    The "The horde database schema does not match the pristine 11.48 horde schema. Attempting to repair it. " looks suspicious to me.
    0
  • cPanelMichael
    Hello :) Could you let us know if the issue was addressed with internal case CPANEL-411? It's included as of cPanel version 11.50.0.29: Fixed case CPANEL-411: Horde conversion "Failed to run patch" error. Thank you.
    0

Please sign in to leave a comment.