Forwarded to devs Cowardly refusing to create an empty archive

[hugendubel]

TITLE:

Cowardly refusing to create an empty archive​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk Onyx 17.8.11, Linux 9 (Stretch; latest, stable) 64-bit OS​

PROBLEM DESCRIPTION:

Setted up a new Server under Debian 9 (lastest, stable) with Plesk Onyx 17.8.11.

Server is a 64-bit OS Intel Atom D425 with 2GB RAM and 1x500GB HDD with 3 partitions

1 primary ext3 / 20000 MB
2 primary ext4 /var (rest of space)
3 primary swap swap 512 MB


Also submitted an issue here Issue - Cowardly refusing to create an empty archive. Plesk Onyx Backup on Debian 9

Just tested around but it seems this is a bug, because it appears also on clean installations without any Domains on the System.

This error occurs NOT, if only a full DOMAIN CONFIGURATION backup is started.​

STEPS TO REPRODUCE:

Set up a new System and run a full Server backup with all configurations.​

ACTUAL RESULT:

Backup Task May 24, 2018 07:13 AM Details
Warning: server "server"
Not all the data was backed up into /var/lib/psa/dumps successfully. Total space: 438.00 GB; Available space: 415.00 GB; Mounted on: /var. /bin/tar: Cowardly refusing to create an empty archive Try '/bin/tar --help' or '/bin/tar --usage' for more information.​

EXPECTED RESULT:

Normally Backup without errors​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

Developers can't reproduce this issue. Please provide more detail for reproducing or ask the assistance of Plesk Support Team. They will check and fix this issue directly on your server.

 

[SGISoft]

Hello IgorG,
I have the same problem. And in my case the installation is from scratch, both the Debian 9 and plesk Onyx 17.8.x were installed on a new machine.
Use to store backup copies "sfk ftpserver" locally
The copies seem to do them correctly but I get errors like these:


Not all the data was backed up into / var / lib / psa / dumps successfully. Total space: 893.00 GB; Available space: 775.00 GB; Mounted on: / var. / bin / tar: Cowardly rejection to create an empty file Try '/ bin / tar --help' or '/ bin / tar --usage' for more information.

Part of logs:

<?xml version="1.0" ?><response>
<errcode>0</errcode>
<data>
<task-list>
<task backup-profile-name="" creation-date="2018-Jun-26 01:27:36" fullname="backup_1806260127.tar" mail-to="" name="backup_1806260127.tar" owner-guid="2b1e39a4-93b0-483e-9462-28301dad6741" owner-type="server" task-id="101" task-pid="" task-type="Backup">
<task-status task-id="101">
<finished log-location="/opt/psa/PMM/sessions/2018-06-26-012734.148/migration.result" status="warnings">
</finished>
</task-status>
<dumps-storage-credentials storage-type="foreign-ftp" use-ftps="false" use-passive-ftp-mode="false">
<login>XXXXX</login>
<password>*****</password>
<hostname>XXXX.com:xxxx</hostname>
<root-dir>/</root-dir>
</dumps-storage-credentials>
</task>
<task backup-profile-name="" creation-date="2018-Jun-25 01:27:32" fullname="backup_1806250127.tar" mail-to="" name="backup_1806250127.tar" owner-guid="2b1e39a4-93b0-483e-9462-28301dad6741" owner-type="server" task-id="100" task-pid="" task-type="Backup">
<task-status task-id="100">
<finished log-location="/opt/psa/PMM/sessions/2018-06-25-012729.331/migration.result" status="warnings">
</finished>
</task-status>
<dumps-storage-credentials storage-type="foreign-ftp" use-ftps="false" use-passive-ftp-mode="false">
<login>XXXXX</login>
<password>*****</password>
<hostname>xxxx.com:xxxxx</hostname>
<root-dir>/</root-dir>
</dumps-storage-credentials>
</task>
<task backup-profile-name="" creation-date="2018-Jun-24 01:27:09" fullname="backup_1806240127.tar" mail-to="" name="backup_1806240127.tar" owner-guid="2b1e39a4-93b0-483e-9462-28301dad6741" owner-type="server" task-id="99" task-pid="" task-type="Backup">
<task-status task-id="99">
<finished log-location="/opt/psa/PMM/sessions/2018-06-24-012706.953/migration.result" status="warnings">
</finished>
</task-status>
<dumps-storage-credentials storage-type="foreign-ftp" use-ftps="false" use-passive-ftp-mode="false">
<login>XXXXX</login>
<password>*****</password>
<hostname>XXXX.com:xxxx</hostname>
<root-dir>/</root-dir>
</dumps-storage-credentials>
</task>
</task-list>
</data>
</response>
[2018-06-26 08:12:24.827|7907] DEBUG: --> <pmmcli.GetTasksListAction object at 0x7f9acd84bf90>
[2018-06-26 08:12:24.846|7907] INFO: stdin: <?xml version="1.0" ?><tasks-list-query><type>Restore</type><type>Backup</type><top-object-type>server</top-object-type><top-object-id>1</top-object-id></tasks-list-query>
[2018-06-26 08:12:24.884|7907] INFO: Packet succesfully validated.
[2018-06-26 08:12:24.884|7907] DEBUG: <pmmcli.ActionRunner object at 0x7f9ad4474450>: doActivity
[2018-06-26 08:12:24.884|7907] DEBUG: Acquired session mutex: MainThread
[2018-06-26 08:12:24.885|7907] DEBUG: Load task id=99 type=Backup
[2018-06-26 08:12:24.886|7907] DEBUG: Load task id=100 type=Backup
[2018-06-26 08:12:24.886|7907] DEBUG: Load task id=101 type=Backup
[2018-06-26 08:12:24.886|7907] DEBUG: Released session mutex: MainThread
[2018-06-26 08:12:24.904|7907] DEBUG: Get task (101) status from migration.result...
[2018-06-26 08:12:24.905|7907] DEBUG: Session path (/opt/psa/PMM/sessions/2018-06-26-012734.148)
[2018-06-26 08:12:24.927|7907] DEBUG: Get task (100) status from migration.result...
[2018-06-26 08:12:24.927|7907] DEBUG: Session path (/opt/psa/PMM/sessions/2018-06-25-012729.331)
[2018-06-26 08:12:24.948|7907] DEBUG: Get task (99) status from migration.result...
[2018-06-26 08:12:24.948|7907] DEBUG: Session path (/opt/psa/PMM/sessions/2018-06-24-012706.953)
[2018-06-26 08:12:24.959|7907] DEBUG: <pmmcli.GetTasksListAction object at 0x7f9acd84bf90>: response
[2018-06-26 08:12:24.965|7907] INFO: Outgoing packet:

 

[SGISoft]

Part of migration.log