• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

AgentBackup error

N

nibb@

Guest
Hi i always get an error when i run the agent backup when it comes to 4 GB or so

/usr/local/psa/bin/pleskbackup all pleskdump



Same when i split it
/usr/local/psa/bin/pleskbackup -s 1024M -v all pleskdump

The latest and most common error after 4 GB:

Phase 2/2: packing data
/bin/tar: ./access_log: file changed as we read it
/bin/tar: Error exit delayed from previous errors
 
Following error message:

bin/tar: ./access_log: file changed as we read it
/bin/tar: Error exit delayed from previous errors

say that while tar archived the file it was changed; access_log is apache log file for every domain, the file is located in HTTPD_VHOSTS_D/<domain>/statistics/logs/access_log;. Probably the file was changed during backup procedure.

At the end, did you get backup file which could be used for restoration?

It is better to split files during backup:

# /usr/bin/perl /usr/local/psa/bin/pleskbackup -s 1024M -v all pleskdump
 
I am getting following error:




[root@sml101 backup]# /usr/local/psa/bin/pleskbackup all /home2/backup/04may07plesk8-1-1-sml101
/bin/tar: Substituting `.' for empty member name
/bin/tar: : Cannot stat: No such file or directory
/bin/tar: Error exit delayed from previous errors
/bin/tar: ./error_log: file changed as we read it



But after long it creates the files, but i afraid if it will genrate problem at the time of restore or after restore.

Please advice or how can i fix it.
 
No reply eh...

I get this also, on a fresh Plesk 8.6.0 installation at (mt) Media Temple.

Any takers? Parallels?
 
Back
Top