Issue File dump-header not found on first position in archive.

[massin]

Server operating system version

AlmaLinux 9.1

Plesk version and microupdate number

18.0.51 Update #1

Recently I am getting an error report after a Scheduled Backup runs using an S3 repository.

<?xml version="1.0"?>
<execution-result log-location="/usr/local/psa/PMM/sessions/2023-04-13-020202.335/migration.result" local-dump-created="true" export-dump-created="true" local-dump-name="backup_info_2304130202.xml" export-dump-name="backup_2304130202.tar" status="warnings">
  <message severity="warning">
    <description>Unable to validate the remote backup. It may not be restored. Error: Unable to extract dump header</description>
  </message>
</execution-result>

If I re-schedule it to run with verbose logging I see that the utility complains that the dump header was not in the first position:

[2023-04-13 05:17:57.191| 4421] INFO: RepositoryTransportExternal::OpenFile: backup_2304130517.tar, rb, 0
[2023-04-13 05:17:57.191| 4421] INFO: Executing utility: /usr/local/psa/admin/bin/backup_restore_helper --extension-transport ext://s3-backup/server -operation open-read -path backup_2
304130517.tar -offset 0
[2023-04-13 05:17:57.192| 4421] INFO: Created temp file: /tmp/pmm-rte-rffb-buf-Z1kNhn
[2023-04-13 05:17:57.192| 4421] INFO: The utility input: read,/tmp/pmm-rte-rffb-buf-Z1kNhn,104857600
[2023-04-13 05:18:10.929| 4421] INFO: The utility output: {"size":104857600}
[2023-04-13 05:18:10.929| 4421] INFO: GetNextTarEntry. szRead 512
[2023-04-13 05:18:10.929| 4421] INFO: GetNextTarEntry. Entry name clients/example/domains/example.com/backup_user-data_2304130517.tar
[2023-04-13 05:18:10.929| 4421] INFO: GetNextTarEntry. Entry size 243599360
[2023-04-13 05:18:10.929| 4421] INFO: File dump-header not found on first position in archive. First entry is "clients/example/domains/example.com/backup_user-data_2304130517.
tar".
[2023-04-13 05:18:10.929| 4421] INFO: RepositoryTransportExternal::CloseFile
[2023-04-13 05:18:10.954| 4421] INFO: The utility input: close
[2023-04-13 05:18:10.965| 4421] INFO: The utility executed with exit code: 0, stdout:
[2023-04-13 05:18:10.965| 4421] INFO: Repository 'ext://s3-backup/server': Get backup info from file backup_2304130517.tar
[2023-04-13 05:18:10.966| 4421] INFO: pmm-ras finished. Exit code: 0
[2023-04-13 05:18:10.967|3769] DEBUG [panel] STDOUT of pmm-ras: <?xml version="1.0" encoding="UTF-8"?>
<dump name="backup_2304130517.tar" fullname="backup_2304130517.tar" creation-date="2304130517" size="658840704">
 <dump-status dump-status="OK" backup-process-status=""/>
</dump>

[2023-04-13 05:18:10.968|3769] WARN [panel] Unable to validate the remote backup. It may not be restored.
[2023-04-13 05:18:10.968|3769] WARN [panel] PleskFatalException: Unable to extract dump header
file: /usr/local/psa/admin/plib/backup/Agent/Repository.php
line: 226
code: 0
trace: #0 /usr/local/psa/admin/plib/backup/Agent/Agent.php(420): Plesk\backup\Agent\Repository->checkExportedDump()
#1 /usr/local/psa/admin/plib/backup/Agent/Agent.php(226): Plesk\backup\Agent\Agent->checkExportedDump()
#2 /usr/local/psa/admin/plib/backup/Agent/Agent.php(117): Plesk\backup\Agent\Agent->finishExporter()
#3 /usr/local/psa/admin/plib/api-common/cuBackupAgent.php(300): Plesk\backup\Agent\Agent->dump()
#4 /usr/local/psa/admin/plib/api-common/cuApp.php(79): cuBackupAgent->_dumpCommand(string '/usr/local/psa/PMM/sessions/2023-04-13-051702.213', string '2fa4f478-63de-439d-94de-6646195dec7c', string 'server', string '', NULL null, string '', string 'no-compression', NULL null, string '/usr/local/psa/PMM/sessions/2023-04-13-051702.213/exclude', string '', NULL null, string 'backup', string 'script', NULL null, NULL null, string 'ext://s3-backup/server/', NULL null, string '', string '', NULL null, string '/usr/local/psa/PMM/sessions/2023-04-13-051702.213/dump_description', string '')
#5 /usr/local/psa/admin/plib/api-common/cuApp.php(73): cuApp->_callCommandMethod(array)
#6 /usr/local/psa/admin/plib/api-common/cuApp.php(53): cuApp->_executeCommand()
#7 /usr/local/psa/admin/plib/api-common/CuExecutor.php(69): cuApp->runFromCliGate()
#8 /usr/local/psa/admin/plib/api-common/CuExecutor.php(131): CuExecutor->execUtil(string 'cuBackupAgent', string 'runFromCliGate')
#9 /usr/local/psa/admin/plib/api-cli/CliUtilityRunner.php(28): CuExecutor->run()
#10 /usr/local/psa/admin/plib/api-cli/CliUtilityRunner.php(37): CliUtilityRunner->run()
#11 /usr/local/psa/admin/sbin/backup_agent(3): require_once(string '/usr/local/psa/admin/plib/api-cli/CliUtilityRunner.php')

[2023-04-13 05:18:10.971|3769] DEBUG [panel] Execute: '/usr/local/psa/admin/bin/send-error-report' 'pmm'

The backup seems to be uploaded properly. If I use s3cmd to download the tar ball, the tar looks ok, it extracts fine, and the check-backup tool says it is ok:

# plesk bin pleskrestore --check-backup backup_2304130517.tar
The backup file was extracted to "/var/lib/psa/dumps".
The backup file is valid.

And the dump-header file is present in the tar ball. So is there something different about how the 'checkExportedDump()' extracts the tar? A missing sort option?

Thanks for your help!