• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk 17.8 issue: pleskbackup fails from cron

madadam

Basic Pleskian
TITLE:
pleskbackup fails from cron
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Product Plesk Onyx
Version 17.8.11 Update #7, last updated on May 10, 2018 12:31 AM
OS ‪CentOS 6.9 (Final)
PROBLEM DESCRIPTION:
Running pleskbackup as a scheduled task (as root) fails, same command completes fine from the command line:

/usr/local/psa/bin/pleskbackup server -c --output-file="/home/backup/plesk_all_conf_sch.tgz" -vvvvv

The error given: <description>Unable to create dump</description>

This was working in an older version of Plesk (not sure which upgrade broke it).​
STEPS TO REPRODUCE:
Crontab contains:

10 * * * * /usr/local/psa/bin/pleskbackup server -c --output-file="/home/backup/plesk_all_conf_sch.tgz" -vvvvv

(configured via Plesk Scheduled Task)​
ACTUAL RESULT:
.-------------- Start print backup log hire -------------- <?xml version="1.0" encoding="UTF-8"?>
<execution-result status="error" log-location="/usr/local/psa/PMM/sessions/2018-05-17-161001.943/migration.result">
<object name="server" type="server">
<message id="27ba9a5c-61a3-44f3-8e15-4d4fe853380a" severity="error" code="fatal">
<description>Unable to create dump</description>
</message>
</object>
</execution-result>
-------------- End print backup log hire --------------

You can view additional information in the log file located in /usr/local/psa/PMM/sessions/2018-05-17-161001.943 directory. This directory will be removed automatically after 30 days

Runtime error: The backup failed with errors!

psadump.log contains:

[8056]: 2018-05-17 17:18:12.818 DEBUG Execute: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/sbin/backup_restore_helper --get-extensions-hooks
[8056]: 2018-05-17 17:18:13.655 TRACE SQL: SELECT id, host, port, type, admin_login, admin_password, server_version FROM DatabaseServers: Params:
[8056]: 2018-05-17 17:18:13.657 DEBUG Set backup owner guid '00000000-0000-0000-0000-000000000000', type 'server'

[8056]: 2018-05-17 17:18:13.657 DEBUG Select to backup Administrator info
[8056]: 2018-05-17 17:18:13.657 DEBUG Select to backup server settings
[8056]: 2018-05-17 17:18:13.657 DEBUG Select to backup server settings
[8056]: 2018-05-17 17:18:13.659 DEBUG The dump of content is switched off
[8056]: 2018-05-17 17:18:13.659 DEBUG Execute: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/sbin/backup_restore_helper --backup-server-info
[8056]: 2018-05-17 17:18:14.531 TRACE SQL: SELECT e.name, e.value FROM ServiceNodeEnvironment AS e INNER JOIN ServiceNodes AS n ON e.serviceNodeId = n.id WHERE n.ipAddress = 'local' AND e.section = 'componentsPackages' AND e.value IS NOT NULL AND e.value <> '': Params:
[8056]: 2018-05-17 17:18:14.539 DEBUG Wait termination of child processes
[8056]: 2018-05-17 17:18:14.539 DEBUG Execute: pkill -P 8056
[8056]: 2018-05-17 17:18:14.561 DEBUG Delete dump files
[8056]: 2018-05-17 17:18:14.561 DEBUG Exec: /usr/local/psa/admin/sbin/pmm-ras --delete-dump-files --dump-storage /home/backup --dump-file-specification plesk_all_conf_sch.tgz --session-path /usr/local/psa/PMM/sessions/2018-05-17-171809.336 --debug --verbose
[8056]: 2018-05-17 17:18:14.620 DEBUG Unable to delete dump files: Repository error: file plesk_all_conf_sch.tgz not exists
[8056]: 2018-05-17 17:18:14.620 DEBUG Unable to create dump: Can't locate object method "setMarkers" via package "Packer" at /usr/local/psa/PMM/agents/PleskX/PleskX.pm line 611.

[8056]: 2018-05-17 17:18:14.620 ERROR d4c3ebbb-6373-4dff-8508-5a537e8f1ed1 Unable to create dump:
at /usr/local/psa/PMM/agents/shared/Logging.pm line 128
Logging::error('Unable to create dump', 'fatal') called at /usr/local/psa/admin/bin/plesk_agent_manager line 780
main::__ANON__('Error::Simple=HASH(0x3c7fa40)', 'SCALAR(0x2945130)') called at /usr/local/psa/PMM/agents/shared/Error.pm line 330
eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 321
Error::subs::run_clauses('HASH(0x3cf95e8)', 'Can\'t locate object method "setMarkers" via package "Packer"...', undef, 'ARRAY(0x3cff448)') called at /usr/local/psa/PMM/agents/shared/Error.pm line 417
Error::subs::try('CODE(0x3cfeb90)', 'HASH(0x3cf95e8)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 782
main::perform('verbose', 4, 'owner-type', 'server', 'include-increments', 0, 'split-size', undef, 'session-path', ...) called at /usr/local/psa/admin/bin/plesk_agent_manager line 1410
main::__ANON__() called at /usr/local/psa/PMM/agents/shared/Error.pm line 406
eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 398
Error::subs::try('CODE(0x268aac0)', 'HASH(0x38b5fd8)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1418
main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1422
EXPECTED RESULT:
Successful backup with no errors.​
ANY ADDITIONAL INFORMATION:
Working in an older version of Plesk
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Unable to create dump: Can't locate object method "setMarkers" via package "Packer" at /usr/local/psa/PMM/agents/PleskX/PleskX.pm line 611.

I suppose that previously you applied patch from Unable to upload the backup to the FTP storage: boost::filesystem::file_size: No such file or directory and as result, there is incorrect PleskX.pm version of the file now.
The corresponding bug was fixed in 17.8 so you could just remove cron task which overwrites Plesk's Packer.pm to the custom version of this file. Because it is not compatible with Plesk 17.8. When the task will be removed Packer.pm should be restored to original file for Plesk 17.8
 
While I did try that patched version, that was after I discovered the issue, and I do not have any cron job to keep replacing it. How can I check if I have the correct version? Is there a link to the latest version?
 
This file is a part of plesk-core package:

# rpm -qf /usr/local/psa/PMM/agents/PleskX/PleskX.pm
plesk-core-17.8.11-cos7.build1708180301.19.x86_64

So, you can check that you have the solid package with something like

# rpm -V plesk-core
 
Thanks for the info @IgorG.

I have verified the file and no issues reported. I have even tried reinstalling plesk-core from a freshly downloaded RPM - I still see the same issue.

If I run the backup command from the command line it works fine - if I schedule it via cron, I see the error:


[2018-06-12 14:17:05.123|30733] INFO: Repository '/home/backup': Initialized

[2018-06-12 14:17:05.124|30733] INFO: Repository '/home/backup': Delete packed backup plesk_all_conf_sch.tgz

[2018-06-12 14:17:05.124|30733] INFO: RepositoryError[76931fac-9dab-42b3-86c2-48b87d6ae33f]: Repository error: file plesk_all_conf_sch.tgz not exists [common/plesk-utils/PMM/repository-transport/repository.cpp:582]

virtual void plesk::tRepository::DeletePackedBackup(const string&)

[2018-06-12 14:17:05.124|30733] INFO: pmm-ras finished. Exit code: 151

[30712]: 2018-06-12 14:17:05.126 DEBUG Unable to delete dump files: Repository error: file plesk_all_conf_sch.tgz not exists

[30712]: 2018-06-12 14:17:05.126 DEBUG Unable to create dump: Can't locate object method "setMarkers" via package "Packer" at /usr/local/psa/PMM/agents/PleskX/PleskX.pm line 611.



[30712]: 2018-06-12 14:17:05.127 ERROR 253dbdbd-2305-4d74-830b-3f998f6c9f13 Unable to create dump:

at /usr/local/psa/PMM/agents/shared/Logging.pm line 128

Logging::error('Unable to create dump', 'fatal') called at /usr/local/psa/admin/bin/plesk_agent_manager line 780

main::__ANON__('Error::Simple=HASH(0x24d6a18)', 'SCALAR(0x119c130)') called at /usr/local/psa/PMM/agents/shared/Error.pm line 330

eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 321

Error::subs::run_clauses('HASH(0x226fe18)', 'Can\'t locate object method "setMarkers" via package "Packer"...', undef, 'ARRAY(0x2556390)') called at /usr/local/psa/PMM/agents/shared/Error.pm line 417

Error::subs::try('CODE(0x2555ad8)', 'HASH(0x226fe18)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 782

main::perform('verbose', 4, 'owner-type', 'server', 'include-increments', 0, 'split-size', undef, 'session-path', ...) called at /usr/local/psa/admin/bin/plesk_agent_manager line 1410

main::__ANON__() called at /usr/local/psa/PMM/agents/shared/Error.pm line 406

eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 398

Error::subs::try('CODE(0xee1ac0)', 'HASH(0x210cfd8)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1418

main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1422



[30712]: 2018-06-12 14:17:05.134 DEBUG Free reserved disk space at /var/lib/psa/dumps/.fs_NaN_0
 
[root@advic ~]# rpm -qf /usr/local/psa/PMM/agents/PleskX/PleskX.pm
plesk-core-17.8.11-cos6.build1708180301.19.x86_64

[root@advic ~]# rpm -Vfv /usr/local/psa/PMM/agents/PleskX/PleskX.pm | grep /usr/local/psa/PMM/agents/PleskX
......... /usr/local/psa/PMM/agents/PleskX
......... /usr/local/psa/PMM/agents/PleskX/ArchiveContent
......... /usr/local/psa/PMM/agents/PleskX/ArchiveContent/ArchiveContent.pm
......... /usr/local/psa/PMM/agents/PleskX/ArchiveContent/UnixArchiveContent.pm
......... /usr/local/psa/PMM/agents/PleskX/BackupDumpStatus.pm
......... /usr/local/psa/PMM/agents/PleskX/BackupSizeCalculator.pm
......... /usr/local/psa/PMM/agents/PleskX/DAL.pm
......... /usr/local/psa/PMM/agents/PleskX/ErrorReportSender.pm
......... /usr/local/psa/PMM/agents/PleskX/HostingDumper.pm
......... /usr/local/psa/PMM/agents/PleskX/MiscConfigParser.pm
......... /usr/local/psa/PMM/agents/PleskX/ObjectsFilter.pm
......... /usr/local/psa/PMM/agents/PleskX/Packer.pm
......... /usr/local/psa/PMM/agents/PleskX/PleskMaxVersion.pm
......... /usr/local/psa/PMM/agents/PleskX/PleskStructure.pm
......... /usr/local/psa/PMM/agents/PleskX/PleskVersion.pm
......... /usr/local/psa/PMM/agents/PleskX/PleskX.pm
......... /usr/local/psa/PMM/agents/PleskX/PmmCli.pm
......... /usr/local/psa/PMM/agents/PleskX/SiteApp
......... /usr/local/psa/PMM/agents/PleskX/SiteApp.pm
......... /usr/local/psa/PMM/agents/PleskX/SiteApp/SiteApp10.pm
......... /usr/local/psa/PMM/agents/PleskX/SiteApp/SiteAppGlobalSettings.pm
......... /usr/local/psa/PMM/agents/PleskX/SmbApsBackup.php
......... /usr/local/psa/PMM/agents/PleskX/SpecificConfig.pm
......... /usr/local/psa/PMM/agents/PleskX/StopWatchPacker.pm
......... /usr/local/psa/PMM/agents/PleskX/Suspend.pm
 
I'd suggest you contact Plesk Support Team in nothing helps.
 
@IgorG Are you sure this isn't a bug?? The fact that the command does not work from cron, but does from command line would surely indicate some kind of path / environmental issue.... has this been tested and known working with the latest release? This used to work fine on the server and was only broken after an update (without changing any settings)! Either there is a bug in one of the update patches (which has since not been corrected) or there is a bug in the current release. Either way, this was broken by a Plesk update!
 
I just want to say, that detailed investigation directly on your server is required for this issue. This can be done only by Support Team. And if they decide that it is really bug - they will submit it through their channels and with full detailed results of the investigation.
 
Back
Top