jared555

Member
Jun 6, 2003
5
0
151
On every account on my server I am getting something along the lines of the following:

Determining mysql dbs......mysql version: 5.5......mysqldump version: 5.5...Saving mysql privs...Done
...Done
Storing mysql dbs............
horde.turba_objectshorde.turba_objects
note : The storage engine for the table doesn't support repair
(1131 bytes) horde.turba_shareshorde.turba_shares
note : The storage engine for the table doesn't support repair
(1080 bytes) horde.horde_prefshorde.horde_prefs
note : The storage engine for the table doesn't support repair
(1123 bytes) horde.kronolith_shareshorde.kronolith_shares
note : The storage engine for the table doesn't support repair
(1149 bytes) horde.kronolith_storagehorde.kronolith_storage
note : The storage engine for the table doesn't support repair
(1149 bytes) horde.mnemo_memoshorde.mnemo_memos
note : The storage engine for the table doesn't support repair
(1127 bytes) horde.nag_taskshorde.nag_tasks
note : The storage engine for the table doesn't support repair
(1119 bytes)
ERROR: Failed to dump one or more databases
...Done

Every innodb table complains about doesn't support repair and then it says failed to dump. Is there an actual issue with the backup or is cPanel just misinterpreting the innodb notices as errors? I am running the new backup system with a remote mariadb 5.5 server.
 

24x7server

Well-Known Member
Apr 17, 2013
1,907
95
78
India
cPanel Access Level
Root Administrator
Hello,

I can see there is an issues with the horde MySQL database and due to that you are getting this issues with the backup so I will suggest you take backup of your horde database and try reinstall horde on your server with the following command

Code:
mysqldump --add-drop-table horde > horde.sql

Reinstall Horde


Code:
/scripts/fullhordereset
 

jared555

Member
Jun 6, 2003
5
0
151
Hello,

I can see there is an issues with the horde MySQL database and due to that you are getting this issues with the backup so I will suggest you take backup of your horde database and try reinstall horde on your server with the following command

Code:
mysqldump --add-drop-table horde > horde.sql

Reinstall Horde


Code:
/scripts/fullhordereset
I used that user as an example because there was no account information with it so it was easy to post without redacting.

USERA:
Code:
Storing mysql dbs............
USERA_wpUSERA_wp.wp_commentmeta
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_comments
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_forum_forums
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_forum_groups
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_forum_posts                         OK
USERA_wp.wp_forum_threads
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_forum_usergroup2user
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_forum_usergroups
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_links
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_options
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_postmeta
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_posts
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_term_relationships
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_term_taxonomy
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_terms
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_usermeta
note     : The storage engine for the table doesn't support repair
USERA_wp.wp_users
note     : The storage engine for the table doesn't support repair
(659237 bytes) horde.turba_objectshorde.turba_objects
note     : The storage engine for the table doesn't support repair
(1147 bytes) horde.turba_shareshorde.turba_shares
note     : The storage engine for the table doesn't support repair
(1082 bytes) horde.horde_prefshorde.horde_prefs
note     : The storage engine for the table doesn't support repair
(1139 bytes) horde.kronolith_shareshorde.kronolith_shares
note     : The storage engine for the table doesn't support repair
(1165 bytes) horde.kronolith_storagehorde.kronolith_storage
note     : The storage engine for the table doesn't support repair
(1165 bytes) horde.mnemo_memoshorde.mnemo_memos
note     : The storage engine for the table doesn't support repair
(1143 bytes) horde.nag_taskshorde.nag_tasks
note     : The storage engine for the table doesn't support repair
(1135 bytes) 
ERROR: Failed to dump one or more databases
...Done
##############################
##############################
##############################
USERB:

One of my development accounts:

Storing mysql dbs............
hostdev_whmcsdev.........
hostdev_whmcsdev.tblaccounts
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblactivitylog
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbladdonmodules
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbladdons
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbladminlog
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbladminperms
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbladminroles
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbladmins
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbladminsecurityquestions
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblaffiliates
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblaffiliatesaccounts
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblaffiliateshistory
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblaffiliatespending
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblaffiliateswithdrawals
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblannouncements
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblbannedemails
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblbannedips
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblbillableitems
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblbrowserlinks
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblbundles
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblcalendar
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblcancelrequests
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblclientgroups
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblclients
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblclientsfiles
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblconfiguration
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblcontacts
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblcredit
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblcurrencies
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblcustomfields
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblcustomfieldsvalues
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbldomainpricing
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbldomains
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbldomainsadditionalfields
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbldownloadcats
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbldownloads
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblemailmarketer
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblemails
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblemailtemplates
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblfraud
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblgatewaylog
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblhosting
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblhostingaddons
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblhostingconfigoptions
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblinvoiceitems
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblinvoices
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblknowledgebase
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblknowledgebasecats
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblknowledgebaselinks
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbllinks
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblmodulelog
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblnetworkissues
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblnotes
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblorders
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblorderstatuses
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblpaymentgateways
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblpricing
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblproductconfiggroups
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblproductconfiglinks
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblproductconfigoptions
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblproductconfigoptionssub
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblproductgroups
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblproducts
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblpromotions
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblquoteitems
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblquotes
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblregistrars
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblservergroups
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblservergroupsrel
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblservers
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblsslorders
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbltax
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketbreaklines
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketdepartments
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketescalations
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketfeedback
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketlog
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketmaillog
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketnotes
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketpredefinedcats
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketpredefinedreplies
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketreplies
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbltickets
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketspamfilters
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblticketstatuses
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbltickettags
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tbltodolist
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblupgrades
note     : The storage engine for the table doesn't support repair
hostdev_whmcsdev.tblwhoislog
note     : The storage engine for the table doesn't support repair
(137451 bytes) horde.turba_objectshorde.turba_objects
note     : The storage engine for the table doesn't support repair
(1126 bytes) horde.turba_shareshorde.turba_shares
note     : The storage engine for the table doesn't support repair
(1081 bytes) horde.horde_prefshorde.horde_prefs
note     : The storage engine for the table doesn't support repair
(1118 bytes) horde.kronolith_shares.........
horde.kronolith_shares
note     : The storage engine for the table doesn't support repair
(1144 bytes) horde.kronolith_storagehorde.kronolith_storage
note     : The storage engine for the table doesn't support repair
(1144 bytes) horde.mnemo_memoshorde.mnemo_memos
note     : The storage engine for the table doesn't support repair
(1122 bytes) horde.nag_taskshorde.nag_tasks
note     : The storage engine for the table doesn't support repair
(1114 bytes) 
ERROR: Failed to dump one or more databases
...Done
##############################
##############################
##############################
The second account was created relatively recently and I don't think mysql has even gone through a clean restart let alone a crash/power failure.
 
Last edited by a moderator:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,201
363
Hello :)

Please check the MySQL error log (/var/lib/mysql/$hostname.err) when you attempt to dump the databases, or when MySQL restarts. Do you notice any specific error messages? What are the contents of your /etc/my.cnf file? Also, please post the output from the following commands:

Code:
mysql --version
mysql
   mysql > show engines;
Thank you.
 

jared555

Member
Jun 6, 2003
5
0
151
Nothing from dumping the DB.

On last startup:

131204 17:03:59 [Note] /usr/sbin/mysqld: Normal shutdown

131204 17:03:59 [Note] Event Scheduler: Purging the queue. 0 events
131204 17:03:59 InnoDB: Starting shutdown...
131204 17:03:59 InnoDB: Waiting for 57 pages to be flushed
131204 17:04:00 InnoDB: Shutdown completed; log sequence number 106500245729
131204 17:04:00 [Note] /usr/sbin/mysqld: Shutdown complete

131204 17:04:01 mysqld_safe mysqld from pid file /var/lib/mysql/data/***.pid ended
131204 17:04:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/data
131204 17:04:02 InnoDB: The InnoDB memory heap is disabled
131204 17:04:02 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
131204 17:04:02 InnoDB: Compressed tables use zlib 1.2.3
131204 17:04:02 InnoDB: Using Linux native AIO
131204 17:04:02 InnoDB: Initializing buffer pool, size = 1.3G
131204 17:04:02 InnoDB: Completed initialization of buffer pool
131204 17:04:02 InnoDB: highest supported file format is Barracuda.
131204 17:04:04 InnoDB: Restoring buffer pool pages from ib_lru_dump
131204 17:04:04 InnoDB: Waiting for the background threads to start
131204 17:04:05 Percona XtraDB (MySQL Performance with Support, Remote DBA, and Consulting Services by Percona) 5.5.34-MariaDB-31.1 started; log sequence number 106500245729
131204 17:04:05 [Note] Plugin 'FEEDBACK' is disabled.
SSL error: Unable to get private key from '/***/***.pem'
131204 17:04:08 [Warning] Failed to setup SSL
131204 17:04:08 [Warning] SSL error: Unable to get private key
131204 17:04:08 [Note] Server socket created on IP: '::'.
131204 17:04:08 [Note] Event Scheduler: Loaded 0 events
131204 17:04:08 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.34-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
131204 17:05:12 InnoDB: Completed reading buffer pool pages (requested: 84645, read: 83133)

I have since fixed the SSL error but not sure why that would have any effect.

mysql --version on server: mysql Ver 15.1 Distrib 5.5.34-MariaDB, for Linux (i686) using readline 5.1

mysql --version on cpanel: mysql Ver 14.14 Distrib 5.5.32, for Linux (x86_64) using readline 5.1

Mysql Server: Server version: 5.5.34-MariaDB-log MariaDB Server

Code:
mysql> show engines;
+--------------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
| Engine             | Support | Comment                                                                    | Transactions | XA   | Savepoints |
+--------------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
| MRG_MYISAM         | YES     | Collection of identical MyISAM tables                                      | NO           | NO   | NO         |
| CSV                | YES     | CSV storage engine                                                         | NO           | NO   | NO         |
| MyISAM             | YES     | MyISAM storage engine                                                      | NO           | NO   | NO         |
| BLACKHOLE          | YES     | /dev/null storage engine (anything you write to it disappears)             | NO           | NO   | NO         |
| InnoDB             | DEFAULT | Percona-XtraDB, Supports transactions, row-level locking, and foreign keys | YES          | YES  | YES        |
| PERFORMANCE_SCHEMA | YES     | Performance Schema                                                         | NO           | NO   | NO         |
| ARCHIVE            | YES     | Archive storage engine                                                     | NO           | NO   | NO         |
| MEMORY             | YES     | Hash based, stored in memory, useful for temporary tables                  | NO           | NO   | NO         |
| FEDERATED          | YES     | FederatedX pluggable storage engine                                        | YES          | NO   | YES        |
| Aria               | YES     | Crash-safe tables with MyISAM heritage                                     | NO           | NO   | NO         |
+--------------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
10 rows in set (0.00 sec)
my.cnf - client:

Code:
[mysqld]
innodb_file_per_table=1
default-storage-engine=Innodb

[client]
host="***"
ssl-ca=/***/***.pem
ssl-cert=/***/***.pem
ssl-key=/***/***.pem
my.cnf - server:

Code:
#
# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d

[mysql]

# CLIENT #
port                           = 3306
socket                         = /var/lib/mysql/mysql.sock

ssl-ca=/***/***.pem
ssl-cert=/***/***.pem
ssl-key=/***/***.pem

[mysqld]

# GENERAL #
user                           = mysql
default_storage_engine         = InnoDB
socket                         = /var/lib/mysql/mysql.sock
pid_file                       = /var/lib/mysql/mysql.pid
character-set-server           = utf8
collation-server               = utf8_general_ci
server-id                      = 1

# MyISAM #
key_buffer_size                = 512M
myisam_recover                 = FORCE,BACKUP

# SAFETY #
max_allowed_packet             = 128M
max_connect_errors             = 1000000
#skip_name_resolve #Commented out by suggestion of cPanel support to fix #42000 error when accessing phpmyadmin
#sql_mode                       = STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY
sysdate_is_now                 = 1
innodb                         = FORCE
innodb_strict_mode             = 1

# DATA STORAGE #
datadir                        = /var/lib/mysql/data

# BINARY LOGGING #
log_bin                        = /var/lib/mysql/mysql-bin
expire_logs_days               = 1
sync_binlog                    = 1
max_binlog_size                = 128M
binlog_format                  = MIXED

# CACHES AND LIMITS #
tmp_table_size                 = 32M
max_heap_table_size            = 32M
#query_cache_type               = 0
query_cache_size               = 32M
max_connections                = 64
thread_cache_size              = 50
open_files_limit               = 65535
table_definition_cache         = 8192
table_open_cache               = 8192

# INNODB #
innodb_flush_method            = O_DIRECT
innodb_log_files_in_group      = 2
innodb_log_file_size           = 64M
innodb_flush_log_at_trx_commit = 1
innodb_file_per_table          = 1
innodb_buffer_pool_size        = 1328M
innodb_file_format             = Barracuda
innodb_stats_on_metadata       = OFF

# XTRADB #
innodb_buffer_pool_restore_at_startup = 600

# LOGGING #
log_error                      = /var/log/mysql/mysql-error.log
log_queries_not_using_indexes  = 0
long_query_time                = 5
slow_query_log                 = 1
slow_query_log_file            = /var/log/mysql/mysql-slow.log

# SSL #
ssl-ca=/***/***.pem
ssl-cert=/***/***.pem
ssl-key=/***/***.pem
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,201
363
The accounts are archived on the cPanel server, and those archives are stored on the remote destination. The database server on the backup machine is not involved with this process, so it's version and setup is irrelevant. Feel free to open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome.

Thank you.