Problem in Restore Full Backup

xpeyman

Registered
May 25, 2016
1
0
1
Singapore
cPanel Access Level
Root Administrator
Hi
I transfer to new server and transfer my accounts but I give error for some of them
the error is :
Code:
RESTORE: 1 completed, 1 had warnings, and 0 failed.

RESTORE: Account “xxxxx”: Warnings
CLAMAVSCANS: The key “CLAMAVSCANS” is unknown, so the system will not restore this key.
The “BandwidthData” restore module failed because of an error: (XID t5tu3u) DBD::SQLite::db do failed: unable to open database file
my old server have mysql 5.5 and new server that i install is mysql 5.6
Can i resolve it ?
I repeat install cpanel for 5 times but the error is given
and my MySQL error log :

Code:
160526 05:13:49 mysqld_safe mysqld from pid file /var/lib/mysql/xx.xxxx.com.pid ended
160526 05:14:45 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2016-05-26 05:14:45 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-05-26 05:14:45 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30) starting as process 1991 ...
2016-05-26 05:14:46 1991 [Note] Plugin 'FEDERATED' is disabled.
2016-05-26 05:14:46 1991 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-05-26 05:14:46 1991 [Note] InnoDB: The InnoDB memory heap is disabled
2016-05-26 05:14:46 1991 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-05-26 05:14:46 1991 [Note] InnoDB: Memory barrier is not used
2016-05-26 05:14:46 1991 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-05-26 05:14:46 1991 [Note] InnoDB: Using Linux native AIO
2016-05-26 05:14:46 1991 [Note] InnoDB: Using CPU crc32 instructions
2016-05-26 05:14:46 1991 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-05-26 05:14:46 1991 [Note] InnoDB: Completed initialization of buffer pool
2016-05-26 05:14:46 1991 [Note] InnoDB: Highest supported file format is Barracuda.
2016-05-26 05:14:46 1991 [Note] InnoDB: 128 rollback segment(s) are active.
2016-05-26 05:14:46 1991 [Note] InnoDB: Waiting for purge to start
2016-05-26 05:14:46 1991 [Note] InnoDB: 5.6.30 started; log sequence number 1940791
2016-05-26 05:14:46 1991 [Note] Server hostname (bind-address): '*'; port: 3306
2016-05-26 05:14:46 1991 [Note] IPv6 is available.
2016-05-26 05:14:46 1991 [Note]   - '::' resolves to '::';
2016-05-26 05:14:46 1991 [Note] Server socket created on IP: '::'.
2016-05-26 05:14:46 1991 [Note] Event Scheduler: Loaded 0 events
2016-05-26 05:14:46 1991 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.30'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,909
2,227
463
The “BandwidthData” restore module failed because of an error: (XID t5tu3u) DBD::SQLite::db do failed: unable to open database file
Hello,

Are you using any third-party monitoring applications? A recent instance of this error message stemmed from the use of the "yunsuo" application. You can check this with a command such as:

Code:
ps aux | grep yunsuo
Thank you.