Plesk Migration Manager - DEBUG Free reserved disk space

[Jens Johansson]

Hi there,

i want to 70 clients move to a new centos and plesk server, but i have a problem with the Plesk Migration Manager:

Source System:
Virtualization: Parallels Cloud Server 6.0.10 SP1 (build 6.0.10-3174)
OS: CentOS 6.7 (Final)
Plesk: 12.0.18 Update #63

[root@www ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/ploop21902p1 296G 121G 165G 43% /
none 5.0G 4.0K 5.0G 1% /dev
none 5.0G 12K 5.0G 1% /dev/shm

#############################

Target System
Virtualization: Parallels Cloud Server 6.0.10 SP1 (build 6.0.10-3178)
OS: ‪CentOS Linux 7.2.1511 (Core)‬
Plesk: 12.5.30 Update #28

[root@www ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/ploop46476p1 200G 14G 177G 7% /
devtmpfs 5.0G 0 5.0G 0% /dev
tmpfs 5.0G 0 5.0G 0% /dev/shm
tmpfs 5.0G 136K 5.0G 1% /run
tmpfs 5.0G 0 5.0G 0% /sys/fs/cgroup
tmpfs 1.0G 0 1.0G 0% /run/user/0

Output on target server: /usr/local/psa/var/modules/panel-migrator/sessions/20160420124852/pmm-agent_2016-04-20_KhXZ1F/dump.log

[16376]: 2016-04-20 13:10:13.536 ERROR 7372ec7c-a842-4112-82b2-073757a8ec1d Unable to create dump:
at Logging.pm line 108
Logging::error('Unable to create dump', 'fatal') called at PleskX.pl line 308
main::main() called at PleskX.pl line 322

[16376]: 2016-04-20 13:10:13.586 DEBUG Free reserved disk space at /tmp/panel_migrator/pmm_agent/.fs_NaN_0

Has anyone an idea? Which limit must to be raised?


Many Many thanks
Erik

 

[IgorG]

I would suggest you check this KB article https://kb.plesk.com/en/115646

 

[Jens Johansson]

Hi IgorG,

thanks, but i can´t see a error:

[root@www ~]# perl -Mbigint -e 'print 0'
0

 

[Jens Johansson]

Hi IgorG,

i have edit all files on the source server:

[root@www ]# find /usr/local/psa/PMM/ -name '*.pm' | xargs grep -i 'BigInt'
/usr/local/psa/PMM/agents/shared/Storage/FtpFileStorage.pm:use Math::BigInt;
/usr/local/psa/PMM/agents/shared/Storage/Storage.pm:use Math::BigInt;
/usr/local/psa/PMM/agents/shared/Storage/FileStorage.pm:use Math::BigInt;
/usr/local/psa/PMM/agents/shared/ContentTransport/Rsync.pm:use Math::BigInt;
/usr/local/psa/PMM/agents/PleskX/RsyncContent.pm:use Math::BigInt;
/usr/local/psa/PMM/agents/PleskX/BackupSizeCalculator.pm:use Math::BigInt;

service psa restart
Stopping sw-engine-fpm: [ OK ]
Starting sw-engine-fpm: [ OK ]
[root@www]# service sw-
sw-cp-server sw-engine
[root@www]# service sw-cp-server restart
Stopping sw-cp-serverd: [ OK ]
Starting sw-cp-serverd: [ OK ]

but the error is the same (i have renamed my customer domainname with "######"):


[28015]: 2016-04-20 14:40:33.653 DEBUG Unable to create dump: Can't call method "prepare" on an undefined value at Db/MysqlDbiBackend.pm line 62.
at Db/MysqlDbiBackend.pm line 62
Db::MysqlDbiBackend::execute('Db::MysqlDbiBackend=HASH(0x32da438)', 'SELECT id, cl_id, name FROM domains WHERE displayName = BINAR...', 0, '#####.#####.#####') called at Db/Connection.pm line 189
Db::Connection::_execute('Db::Connection=HASH(0x32d9f28)', 'SELECT id, cl_id, name FROM domains WHERE displayName = BINAR...', 0, '#####.#####.#####') called at Db/Connection.pm line 203
Db::Connection::execute('Db::Connection=HASH(0x32d9f28)', 'SELECT id, cl_id, name FROM domains WHERE displayName = BINAR...', '#####.#####.#####') called at PleskX.pm line 1188
PleskX::getDomainRootPath('PleskX=HASH(0x32e0160)', '#####.#####.#####') called at PleskX.pm line 1208
PleskX::createDomainsDump('PleskX=HASH(0x32e0160)') called at PleskX.pm line 655
PleskX::dump('PleskX=HASH(0x32e0160)') called at PleskX.pl line 302
eval {...} called at PleskX.pl line 160
main::main() called at PleskX.pl line 322

[28015]: 2016-04-20 14:40:33.653 ERROR d03bcd82-f5ba-4d40-84d9-7367e5a1a903 Unable to create dump:
at Logging.pm line 108
Logging::error('Unable to create dump', 'fatal') called at PleskX.pl line 308
main::main() called at PleskX.pl line 322

[28015]: 2016-04-20 14:40:33.704 DEBUG Free reserved disk space at /tmp/panel_migrator/pmm_agent/.fs_NaN_0

########

In the file /usr/local/psa/PMM/agents/PleskX/PleskX.pm is not a entry with "bigint".

Did you have another idea?