• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Backup Manager doesn't work after updating to 17.8.11 MU3

Joost de Bruijn

New Pleskian
Yesterday my Plesk 17.8.11 installation was updated to MU3. This night I received the following error by mail:

The following error occurred during the scheduled backup process:

Runtime error: Dump validation utility returned empty result at /opt/psa/admin/bin/plesk_agent_manager line 1297.
; Dump validation utility returned empty result

In the UI I cannot open the Backup Manager: I receive an empty error message: also the panel logging does not contain any additional information:

[2018-04-01 11:25:49.139] ERR [panel]
[2018-04-01 11:25:58.034] ERR [panel]
[2018-04-01 11:26:22.187] ERR [panel]
[2018-04-01 13:07:38.817] ERR [panel]
[2018-04-01 13:10:30.791] ERR [panel]

I ensured the backup FTP-server is up and running and the credentials haven't changed. Also, the FTP-server software is not updated recently. The FTP-logging does not identicate something worth to mention. Is this an issue with MU3? How can I resolve it?
 
to nearror down the issue,
which OS are you running and is it a scheduled Backup of a Domain or a Server Backup.
is there something helpfull error message in the PMM log files, usually under /var/log/plesk/PMM/
 
Last edited:
I'm running Ubuntu 16.04.4. Thanks for the other logfile location, I was not aware of that one. Maybe this can be interesting:

[31395]: 2018-04-01 03:37:57.745 ERROR e2f249fa-71ac-42fd-8777-79af0226c968 Dump validation utility returned empty result
[31395]: 2018-04-01 03:37:57.807 ERROR 0df67fa2-4ffe-4d19-80ad-46d79b0bada7 Runtime error: Dump validation utility returned empty result at /opt/psa/admin/bin/plesk_agent_manager line 1297.
:
at /opt/psa/PMM/agents/shared/Logging.pm line 129.
Logging::error("Runtime error: Dump validation utility returned empty result "..., "fatal") called at /opt/psa/admin/bin/plesk_agent_manager line 1416
main::__ANON__(Error::Simple=HASH(0x2a8f898), SCALAR(0x173e4d8)) called at /usr/share/perl5/Error.pm line 340
eval {...} called at /usr/share/perl5/Error.pm line 330
Error::subs::run_clauses(HASH(0x298caa8), "Dump validation utility returned empty result at /opt/psa/adm"..., undef, ARRAY(0x173e910)) called at /usr/share/perl5/Error.pm line 427
Error::subs::try(CODE(0xee25b8), HASH(0x298caa8)) called at /opt/psa/admin/bin/plesk_agent_manager line 1418
main::main() called at /opt/psa/admin/bin/plesk_agent_manager line 1422

This error did not occured before the upgrade to MU3.
 
Hello. Unfortunately, we cannot reproduce the issue. Could you please do the following steps:
1. Set FORCE_DEBUG_LOG to 1 in /usr/local/psa/admin/share/pmmcli/pmmcli-rc
2. Run the backup
3. Find the latest log file /var/log/plesk/PMM/backup..../backup.log. And post their parts from the line with 'Check dump' till the end of the log file
 
Back
Top