Skip to main content

Backup restoration page fatal error or timeout

Comments

4 comments

  • cPanelLauren
    Hello @zlygis This issue is part of the internal case CPANEL-24505 If the transport database(/backup/transports.db), is corrupted or present but empty, the database is not automatically rebuilt. The current workaround is to move/rename the database entirely by doing the following for example : I made a directory for the sqlite db to go into: mkdir /root/backup_transportdb
    Then moved the db to the newly created directory mv /backup/transports.db /root/backup_transportdb/transports.db
    Then run the backup with the force flag (or wait for it to run again) /usr/local/cpanel/bin/backup --force
    If you are running an unsupported backup mount type such as CIFS it may be possible that this workaround will not function correctly. We'll also update this thread when the issue has been resolved or if there are any further updates.
    0
  • cPanelLauren
    This issue is marked as resolved in current versions of cPanel/WHM. Please let us know if you experience any further issues.
    0
  • zlygis
    Suggested solution did not worked. Waited for update. Updated to latest cPamel/WHM. Still get the same error: (XID wy4784) The system received an error from the "SQLite" database "/backup/transports.db": SQLITE_BUSY (database is locked) at /usr/local/cpanel/Cpanel/DBI.pm line 188. Cpanel::DBI::_error_handler("DBD::SQLite::db do failed: database is locked", Cpanel::DBI::SQLite::db=HASH(0x32ed630), undef) called at /usr/local/cpanel/Cpanel/SQLite/AutoRebuildSchemaBase.pm line 304 Cpanel::SQLite::AutoRebuildSchemaBase::_setup_schema("Cpanel::Backup::Transport::DB", Cpanel::DBI::SQLite::db=HASH(0x32ed630)) called at /usr/local/cpanel/Cpanel/Backup/Transport/DB.pm line 64 Cpanel::Backup::Transport::DB::dbconnect("Cpanel::Backup::Transport::DB") called at /usr/local/cpanel/Cpanel/Backup/Transport/History.pm line 58 Cpanel::Backup::Transport::History::new("Cpanel::Backup::Transport::History") called at /usr/local/cpanel/Whostmgr/API/1/Backup.pm line 572 Whostmgr::API::1::Backup::backup_set_list_combined() called at whostmgr/bin/whostmgr5.pl line 1263 main::restoremenu("restoremenu") called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 259 Whostmgr::Dispatch::_do_call("restoremenu", HASH(0x2cc0050), HASH(0x2cd1240)) called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 157 Whostmgr::Dispatch::dispatch("restoremenu", 17, ARRAY(0x2cd05e0)) called at whostmgr/bin/whostmgr5.pl line 280
    BTW What do you mean "unsupported backup mount type such as CIFS"? We used CIFS as a backup point for more then 4 years and it was working flawlesly.
    0
  • cPanelLauren
    BTW What do you mean "unsupported backup mount type such as CIFS"? We used CIFS as a backup point for more then 4 years and it was working flawlesly.

    CIFS has never been supported, whether or not it worked without issue. This is clearly noted in our documentation here: How to Resolve CIFS-mounted Backup Drive Permissions Errors - cPanel Knowledge Base - cPanel Documentation but this is something you'd need to work with your system administrator on and we do not guarantee this will resolve the issue.
    0

Please sign in to leave a comment.