Forwarded to devs RESOLVED /logs/*.webstat backed up despite backup setting "Exclude log files" is checked

[Bitpalast]

Username: Peter Debik

TITLE

/logs/*.webstat backed up despite backup setting "Exclude log files" is checked

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Obsidian with latest MU, CentOS 7.9

PROBLEM DESCRIPTION

the /logs/*.webstat files sometimes have permissions 0400, e.g.

-r-------- 1 root root 0 Jan 21 04:46 access_log.webstat
-r-------- 1 root root 0 Jan 21 04:46 access_ssl_log.webstat

so that the full server backup cannot access them to back them up. It throws an error like:

backup.log:[2021-01-22 00:53:47.223|19243] INFO: <subscription name>/logs/access_log.webstat: Cannot open: Permission denied
backup.log:<subscription name>/logs/access_ssl_log.webstat: Cannot open: Permission denied

This results in daily "failed backup" notices. However, in the backup schedule, the checkbox "Exclude log files" is checked, so these files should not be backed up at all.

To mitigate the issue we have tried to create a cron job that resets the permissions 0644, but for unknown reason this did not help. It seems that the permissions are always set to 0400 shortly before the backup takes place. This does not happen in all subscriptions. It occurs only occasionally in some across many servers.

STEPS TO REPRODUCE

This does not happen in all subscriptions. It occurs only occasionally in some across many servers.

ACTUAL RESULT

Server full backup tries to back-up /var/www/vhosts/<subscription name>/logs/*.webstat files, although in the backup schedule the "Exclude log files" option is checked.

EXPECTED RESULT

Server full backup should exclude /var/www/vhosts/<subsription name>/logs/*.webstat files when the option "Exclude log files" is checked.

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Bitpalast]

This can be considered resolved.

After detailed analysis we found that the customer has been copying and modifying files, so that it interfered with Plesk's own algorithms. For that reason it looked as if Plesk backup is making the mistake, but it was indeed interference from third party scripts.

 

[DenisG]

Pay attention Backup manager never backs up /var/www/vhosts/<subscription name>/logs, it archives the logs from /var/www/vhosts/system/<subscription name>/logs under root account.