Recent content by DenisG

Thanks for the clarification and pieces of advice!

It looks strange. Where did you get that information? The man pzstd command says the following: Parallel ZSTD options: -p, --processes # : number of threads to use for (de)compression (default:<numcpus>) This means Plesk uses as many threads as there are CPU cores...

Try to use the custom fix from the attached archive unzip -B -d /usr/local/psa PPS-17748-custom-fix.zip

The issue can be related to validation of remote backups that was introduced in Plesk 18.0.68. Since Plesk 18.0.69 there is panel.ini option that allows to tune validation period (once a week is default). [pmm] ; in days, 0 means no validation backupsValidationPeriod = 7

Make sure SELinux is turned off or is tuned properly.

Is it acceptable to switch PHP handling from Apache to nginx? It can resolve the issue.

Could you switch on verbose logging in /usr/local/psa/admin/conf/panel.ini and check or provide the results of execution of the commands passenger-config-proxy and passenger-status-proxy in /var/log/plesk/panel.log?

I have created the PPPM-13553 request. 'Incorrect reparse stream' is only a warning. The backup itself and unpacked data are valid.

The warning 'There are data after the end of archive' is normal for Plesk backups. They actually contain additional info after the end of archive. Do you have other errors with 7zip?

Yes, it is. I have created the PPPM-13411 request.

The bug is confirmed and the request PPPM-13411 is created.

I have reproduced the issue with hanging of backup processes. It is caused by inaccessible FTP storage. Also hung processes can block run of other scheduled backups.

Check whether scheduled backups are active in the 'BackupsScheduled' table of the 'psa' database ('active' column). It looks like inaccessible FTP storage causes hanging backup processes. Also pay attention the 'muster01' customer (not the 'test.tld' subscription) is backed up in the first case.

Use the Backup Telemetry extension to get more info about a running backup. Also the 'strace -p <process number>' can help to understand the reason for the process hanging.

Plesk since 18.0.35 gathers telemetry of backup processes. The telemetry can be displayed via using the extension Backup Telemetry. Currently the extension can be installed only from command line plesk bin extension --install backup-telemetry After the installation you can go to backups list and...