Problem with backup process

Hi guys. I've a problem with the backup schedule backup process on one of my cPanel servers.... It's the same problem if with the schedule backup or with the script ( /usr/local/cpanel/bin/backup --force) Here some lines of the logs files... Any idea about what is going on? Thanks....


From /usr/local/cpanel/logs/cpbackup/1499108412.log
-------------------------------------------------

[2017-07-03 22:24:57 +0100] info [backup] Queuing transport of file: /backup/2017-07-03/backup_incomplete
[2017-07-03 22:25:14 +0100] warn [backup] Pruning of backup files skipped due to errors. at /usr/local/cpanel/bin/backup line 398.
bin::backup::run("bin::backup", "--force") called at /usr/local/cpanel/bin/backup line 104
[2017-07-03 22:25:14 +0100] info [backup] Queuing transport reporter
[2017-07-03 22:25:14 +0100] info [backup] Completed at Mon Jul 3 22:25:14 2017
[2017-07-03 22:25:14 +0100] info [backup] Final state is Backup::PartialFailure (0)
[2017-07-03 22:25:14 +0100] info [backup] Sent Backup::PartialFailure notification.

-------------------------------------------

From /usr/local/cpanel/logs/error_log -- cat error_log | grep -i "2017-07-03" | grep -i "dump"

[root@en2 logs]# cat error_log | grep -i "2017-07-03" | grep -i "dump"
[2017-07-03 02:56:10 +0100] warn [pkgacct] cdadmin_wpdb: mysqldump: Got error: 1932: "Table 'cdadmin_wpdb.wp_wfNet404s' doesn't exist in engine" when using LOCK TABLES at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:56:10 +0100] warn [pkgacct] cdadmin_wpdb: mysqldump: Couldn't execute 'show create table `wp_wfNet404s`': Table 'cdadmin_wpdb.wp_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:56:11 +0100] warn [pkgacct] cdadmin_wpdb: mysqldump: Couldn't execute 'show create table `wp_wfNet404s`': Table 'cdadmin_wpdb.wp_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:56:11 +0100] warn [pkgacct] cdadmin_wpdb: mysqldump failed -- database may be corrupt at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 392.
[2017-07-03 02:56:11 +0100] warn [pkgacct] Failed to dump database cdadmin_wpdb: The subprocess reported error number 2 when it ended. at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 218.
[2017-07-03 02:56:54 +0100] warn [pkgacct] hcadmin_wpdb: mysqldump: Got error: 1932: "Table 'hcadmin_wpdb.a2v99d5j2_wfNet404s' doesn't exist in engine" when using LOCK TABLES at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:56:54 +0100] warn [pkgacct] hcadmin_wpdb: mysqldump: Couldn't execute 'show create table `a2v99d5j2_wfNet404s`': Table 'hcadmin_wpdb.a2v99d5j2_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:56:54 +0100] warn [pkgacct] hcadmin_wpdb: mysqldump: Couldn't execute 'show create table `a2v99d5j2_wfNet404s`': Table 'hcadmin_wpdb.a2v99d5j2_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:56:54 +0100] warn [pkgacct] hcadmin_wpdb: mysqldump failed -- database may be corrupt at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 392.
[2017-07-03 02:56:54 +0100] warn [pkgacct] Failed to dump database hcadmin_wpdb: The subprocess reported error number 2 when it ended. at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 218.
[2017-07-03 02:57:59 +0100] warn [pkgacct] tosap_wpdb: mysqldump: Got error: 1932: "Table 'tosap_wpdb.hrn9sogm_wfNet404s' doesn't exist in engine" when using LOCK TABLES at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:57:59 +0100] warn [pkgacct] tosap_wpdb: mysqldump: Couldn't execute 'show create table `hrn9sogm_wfNet404s`': Table 'tosap_wpdb.hrn9sogm_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:57:59 +0100] warn [pkgacct] tosap_wpdb: mysqldump: Couldn't execute 'show create table `hrn9sogm_wfNet404s`': Table 'tosap_wpdb.hrn9sogm_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:57:59 +0100] warn [pkgacct] tosap_wpdb: mysqldump failed -- database may be corrupt at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 392.
[2017-07-03 02:57:59 +0100] warn [pkgacct] Failed to dump database tosap_wpdb: The subprocess reported error number 2 when it ended. at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 218.
[2017-07-03 02:58:33 +0100] warn [pkgacct] mulladmin_wpdb: mysqldump: Got error: 1932: "Table 'mulladmin_wpdb.wp_wfNet404s' doesn't exist in engine" when using LOCK TABLES at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:58:33 +0100] warn [pkgacct] mulladmin_wpdb: mysqldump: Couldn't execute 'show create table `wp_wfNet404s`': Table 'mulladmin_wpdb.wp_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:58:33 +0100] warn [pkgacct] mulladmin_wpdb: mysqldump: Couldn't execute 'show create table `wp_wfNet404s`': Table 'mulladmin_wpdb.wp_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:58:33 +0100] warn [pkgacct] mulladmin_wpdb: mysqldump failed -- database may be corrupt at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 392.
[2017-07-03 02:58:33 +0100] warn [pkgacct] Failed to dump database mulladmin_wpdb: The subprocess reported error number 2 when it ended. at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 218.
[2017-07-03 02:59:01 +0100] warn [pkgacct] wcadmin_wpdb: mysqldump: Got error: 1932: "Table 'wcadmin_wpdb.wp_wfHoover' doesn't exist in engine" when using LOCK TABLES at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:59:01 +0100] warn [pkgacct] wcadmin_wpdb: mysqldump: Couldn't execute 'show create table `wp_wfHoover`': Table 'wcadmin_wpdb.wp_wfHoover' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:59:01 +0100] warn [pkgacct] wcadmin_wpdb: mysqldump: Couldn't execute 'show create table `wp_wfHoover`': Table 'wcadmin_wpdb.wp_wfHoover' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:59:01 +0100] warn [pkgacct] wcadmin_wpdb: mysqldump failed -- database may be corrupt at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 392.
[2017-07-03 02:59:01 +0100] warn [pkgacct] Failed to dump database wcadmin_wpdb: The subprocess reported error number 2 when it ended. at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 218.
[2017-07-03 02:59:27 +0100] warn [pkgacct] muladmin_wpdb: mysqldump: Got error: 1932: "Table 'muladmin_wpdb.y47mhiq1wv_wfNet404s' doesn't exist in engine" when using LOCK TABLES at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:59:27 +0100] warn [pkgacct] muladmin_wpdb: mysqldump: Couldn't execute 'show create table `y47mhiq1wv_wfNet404s`': Table 'muladmin_wpdb.y47mhiq1wv_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:59:28 +0100] warn [pkgacct] muladmin_wpdb: mysqldump: Couldn't execute 'show create table `y47mhiq1wv_wfNet404s`': Table 'muladmin_wpdb.y47mhiq1wv_wfNet404s' doesn't exist in engine (1932) at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 424, <$fh> line 1.
[2017-07-03 02:59:28 +0100] warn [pkgacct] muladmin_wpdb: mysqldump failed -- database may be corrupt at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 392.
[2017-07-03 02:59:28 +0100] warn [pkgacct] Failed to dump database muladmin_wpdb: The subprocess reported error number 2 when it ended. at /usr/local/cpanel/Cpanel/Pkgacct/Components/Mysql.pm line 218.

---------------------------------------------------------------------------

24x7server

July 04, 2017 05:46

Hi, It appears that the MySQL is failing to dump the database. You will have to first fix the MySQL issue and make sure that the database dump is taken properly first, then you have to manually take the backup of the account to check whether its taken properly or not and then you have to forcefully execute the backup and monitor it again..

Federico Barcelo

July 04, 2017 11:32

Hi, thanks for your response. I tried to repare the corrupted databses yesterday, but i've not succes with that... I tried to use commands like mysqlcheck "all-databases -r | mysqlcheck "all-databases -a |mysqlcheck "all-databases -o, but all of them results in errors Here some results of mysqlcheck "all-databases -a

zigzaghb_wpdb.wp_wfNet404s
Warning  : Tablespace is missing for table 'zigzaghb_wpdb/wp_wfNet404s'
Error    : Table 'zigzaghb_wpdb.wp_wfNet404s' doesn't exist in engine
status   : Operation failed
zigzaghb_wpdb.wp_wfNotifications                   OK
zigzaghb_wpdb.wp_wfPendingIssues                   OK
zigzaghb_wpdb.wp_wfReverseCache                    OK
zigzaghb_wpdb.wp_wfSNIPCache                       OK
zigzaghb_wpdb.wp_wfScanners                        OK
zigzaghb_wpdb.wp_wfStatus                          OK
zigzaghb_wpdb.wp_wfThrottleLog                     OK
zigzaghb_wpdb.wp_wfVulnScanners
Warning  : Tablespace is missing for table 'zigzaghb_wpdb/wp_wfVulnScanners'
Error    : Table 'zigzaghb_wpdb.wp_wfVulnScanners' doesn't exist in engine
status   : Operation failed

Also we use the repair option on WHM interface, with the same result...

Repairing zigzaghb_wpdb

zigzaghb_wpdb.wp_commentmeta
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_comments
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_itsec_lockouts
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_itsec_log
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_itsec_temp
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_layerslider
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_links
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_options
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_postmeta
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_posts
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_term_relationships
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_term_taxonomy
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_termmeta
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_terms
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_usermeta
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_users
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfBadLeechers
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfBlockedIPLog                    OK
zigzaghb_wpdb.wp_wfBlocks
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfBlocksAdv
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfConfig
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfCrawlers
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfFileMods
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfHits
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfHoover
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfIssues
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfKnownFileList
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfLeechers
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfLockedOut
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfLocs
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfLogins
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfNet404s
Warning  : Tablespace is missing for table 'zigzaghb_wpdb/wp_wfNet404s'
Error    : Table 'zigzaghb_wpdb.wp_wfNet404s' doesn't exist in engine
status   : Operation failed
zigzaghb_wpdb.wp_wfNotifications
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfPendingIssues
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfReverseCache
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfSNIPCache
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfScanners
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfStatus
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfThrottleLog
note     : The storage engine for the table doesn't support repair
zigzaghb_wpdb.wp_wfVulnScanners
Warning  : Tablespace is missing for table 'zigzaghb_wpdb/wp_wfVulnScanners'
Error    : Table 'zigzaghb_wpdb.wp_wfVulnScanners' doesn't exist in engine
status   : Operation failed

Infopro

July 04, 2017 11:39

Are these active databases in use, or old ones never properly removed from your account?

July 04, 2017 11:41

All of them are actives accounts on the cPanel server, of course they are in use... I checked the tables of one database using phmyadmin interface on cPanel page. Here the result, I don't know if this would help... When I tried to check some table with error, the php interface shows this message... 47631

zigzaghb_wpdb.wp_commentmeta     check     status     OK
zigzaghb_wpdb.wp_comments     check     status     OK
zigzaghb_wpdb.wp_itsec_lockouts     check     status     OK
zigzaghb_wpdb.wp_itsec_log     check     status     OK
zigzaghb_wpdb.wp_itsec_temp     check     status     OK
zigzaghb_wpdb.wp_layerslider     check     status     OK
zigzaghb_wpdb.wp_links     check     status     OK
zigzaghb_wpdb.wp_options     check     status     OK
zigzaghb_wpdb.wp_postmeta     check     status     OK
zigzaghb_wpdb.wp_posts     check     status     OK
zigzaghb_wpdb.wp_termmeta     check     status     OK
zigzaghb_wpdb.wp_terms     check     status     OK
zigzaghb_wpdb.wp_term_relationships     check     status     OK
zigzaghb_wpdb.wp_term_taxonomy     check     status     OK
zigzaghb_wpdb.wp_usermeta     check     status     OK
zigzaghb_wpdb.wp_users     check     status     OK
zigzaghb_wpdb.wp_wfBadLeechers     check     status     OK
zigzaghb_wpdb.wp_wfBlockedIPLog     check     status     OK
zigzaghb_wpdb.wp_wfBlocks     check     status     OK
zigzaghb_wpdb.wp_wfBlocksAdv     check     status     OK
zigzaghb_wpdb.wp_wfConfig     check     status     OK
zigzaghb_wpdb.wp_wfCrawlers     check     status     OK
zigzaghb_wpdb.wp_wfFileMods     check     status     OK
zigzaghb_wpdb.wp_wfHits     check     status     OK
zigzaghb_wpdb.wp_wfHoover     check     status     OK
zigzaghb_wpdb.wp_wfIssues     check     status     OK
zigzaghb_wpdb.wp_wfKnownFileList     check     status     OK
zigzaghb_wpdb.wp_wfLeechers     check     status     OK
zigzaghb_wpdb.wp_wfLockedOut     check     status     OK
zigzaghb_wpdb.wp_wfLocs     check     status     OK
zigzaghb_wpdb.wp_wfLogins     check     status     OK
zigzaghb_wpdb.wp_wfNet404s     check     Warning     Tablespace is missing for table 'zigzaghb_wpdb/wp_...
zigzaghb_wpdb.wp_wfNet404s     check     Error     Table 'zigzaghb_wpdb.wp_wfNet404s' doesn't exist i...
zigzaghb_wpdb.wp_wfNet404s     check     status     Operation failed
zigzaghb_wpdb.wp_wfNotifications     check     status     OK
zigzaghb_wpdb.wp_wfPendingIssues     check     status     OK
zigzaghb_wpdb.wp_wfReverseCache     check     status     OK
zigzaghb_wpdb.wp_wfScanners     check     status     OK
zigzaghb_wpdb.wp_wfSNIPCache     check     status     OK
zigzaghb_wpdb.wp_wfStatus     check     status     OK
zigzaghb_wpdb.wp_wfThrottleLog     check     status     OK
zigzaghb_wpdb.wp_wfVulnScanners     check     Warning     Tablespace is missing for table 'zigzaghb_wpdb/wp_...
zigzaghb_wpdb.wp_wfVulnScanners     check     Error     Table 'zigzaghb_wpdb.wp_wfVulnScanners' doesn't ex...
zigzaghb_wpdb.wp_wfVulnScanners     check     status     Operation failed

July 04, 2017 13:48

This thread may be of some use: InnoDB Corruption Repair Guide

July 07, 2017 13:11

Hi guys, Problem resolved, we repaired the tables on the databases using phpmyadmin. After that, the backup process starts to run again without problems. Thanks to all :)

Problem with backup process

Comments

Didn't find what you were looking for?