Issue Unable to upload dump to FTP

[martinoL]

Hello since update plesk version ‪CentOS 6.4 , 12.5.30 Update #39 my backup to FTP don't works...
I have error : Unable to upload dump to FTP, it remains in server repository and you can manually download and upload it to FTP. Upload diagnostic message: Repository error: Unable to save data to an archive. Check whether the target directory is accessible for writing. I have change to local server and reconfigure FTP don't work... When i test connection manuely to ftp server no problem...
I have check the permission and it 's ok.
see migration.log in join file.


Thanks a lot !

 

[ero]

I was have the same problem with Ubuntu, but I just wait some days and now is work

 

[IgorG]

[2016-07-12 04:16:22.470|23080] INFO: Ftp init url ftp://cd1075.backuplws.com/jupiter/quotidien/backup_iteipmai.fr_1607120406.tar
[2016-07-12 04:16:37.541|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:16:42.541|23080] INFO: Trying to resume upload...
[2016-07-12 04:16:58.431|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:17:03.431|23080] INFO: Trying to resume upload...
[2016-07-12 04:17:18.717|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:17:23.718|23080] INFO: Trying to resume upload...
[2016-07-12 04:17:39.324|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:17:44.325|23080] INFO: Trying to resume upload...
[2016-07-12 04:17:59.631|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:18:04.632|23080] INFO: Trying to resume upload...
[2016-07-12 04:18:20.140|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:18:25.143|23080] INFO: Trying to resume upload...
[2016-07-12 04:18:40.966|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:18:45.966|23080] INFO: Trying to resume upload...
[2016-07-12 04:19:01.159|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:19:06.161|23080] INFO: Trying to resume upload...
[2016-07-12 04:19:23.334|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:19:28.335|23080] INFO: Trying to resume upload...
[2016-07-12 04:19:43.441|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:19:48.442|23080] INFO: Trying to resume upload...
[2016-07-12 04:20:04.168|23080] INFO: Error 28 Timeout was reached
[2016-07-12 04:20:04.235|23080] INFO: The utility executed with the return code: -1
[2016-07-12 04:20:04.296|23080] INFO: RepositoryError[3221245d-76b8-4dc6-8f03-3bd0d5bd92b4]: Repository error: Unable to save data to an archive. Check whether the target directory is accessible for writing. For more information, see the log file (/usr/local/psa/PMM/sessions/2016-07-12-040632.444/migration.log) [:11975344]

Please check FTP server logs for the noted timeframe to clarify why connection dropped off with a timeout. Most probably that you need to increase the timeout on you FTP repository according to your backup size.

 

[martinoL]

Hello,

see in file attachment the log.


Thanks a lot.

 

[IgorG]

And?
I see nothing suspicious in this log.

 

[martinoL]

In plesk interface i have tihs error :

Error:
Unable to rotate dump: The dump rotation is failed with code '151' at /usr/local/psa/admin/bin/plesk_agent_manager line 1224.
Error:
Unable to upload dump to FTP, it remains in server repository and you can manually download and upload it to FTP. Upload diagnostic message: Repository error: Destination directory 'ftp://cd1075.backuplws.com/jupiter/quotidien/' does not exist


In migration.log :

<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="error" log-location="/usr/local/psa/PMM/sessions/2016-07-19-032101.310/migration.result">
<message id="9a77c847-6f19-4289-88ec-d83f76edab1d" severity="error" code="UtilityError">
<description>Unable to rotate dump: The dump rotation is failed with code &#39;151&#39; at /usr/local/psa/admin/bin/plesk_agent_manager line 1224.
</description>
</message>
<message id="5cc3b85f-c2f1-4016-8ffc-3afd4ff83281" severity="error" code="msgtext">
<description>Unable to upload dump to FTP, it remains in server repository and you can manually download and upload it to FTP. Upload diagnostic message: Repository error: Destination directory &#39;ftp://cd1075.backuplws.com/jupiter/quotidien/&#39; does not exist
</description>
</message>
</execution-result>

 

[IgorG]

Unable to rotate dump: The dump rotation is failed with code '151' at /usr/local/psa/admin/bin/plesk_agent_manager line 1224.

https://talk.plesk.com/threads/dump-error-151.338315/

 

[mikcanavan]

Hi Igor,

I've been having this issue for quite a time now (since Jan 16 at least) and now that there seems to be more people experiencing it - and therefore more appearing in search, it would be great to get this issue fixed.

I know that the backup is created (the files are on the FTP and are useable), and I know that the backup rotation is working (I set to 7 backups and can see 7 backups), but what I think is happening is that it is trying to rotate or delete the oldest backup twice.

Here is the error (one of, I receive multiple random domains despite all being on daily backup) I receive every morning :

Backup task finished on host plesk8.fivenines.co.uk.

Creation date is: 2016-Jul-25 03:17:03
Created by: Plesk administrator (type=server, guid=e32519dd-fada-4b2e-ae58-aa703cb4cd7f)
Created for: domain.co.uk (type=domain, id=73)
Task status is: error (see details in the attached file)

Dump full name is: backup_domain.co.uk_1607250317.tar

The attachment contents :

<?xml version="1.0" encoding="UTF-8"?>
  <execution-result status="error" log-location="/usr/local/psa/PMM/sessions/2016-07-25-031702.759/migration.result">
    <message id="9d5d509e-a5fe-4bfe-8958-0f0a950c31e8" severity="error" code="UtilityError">
      <description>Unable to rotate dump: The dump rotation is failed with code &#39;151&#39; at /usr/local/psa/admin/bin/plesk_agent_manager line 1224.
</description>
    </message>
  </execution-result>

The migration.log file for this particular backup error above is attached - please let me know if other logs would be useful. This example error is listed as 'domain.co.uk' and other domains on the server changed to abc123.co.uk for privacy.

Here is my freespace output as I have seen this as peoples suggestion on previous threads :

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md1              4.0G 1016M  3.0G  25% /
/dev/mapper/vg00-usr  9.8G  3.0G  6.3G  33% /usr
/dev/mapper/vg00-var  211G   63G  140G  31% /var
/dev/mapper/vg00-home
                      3.9G  8.0M  3.6G   1% /home
none                  5.9G  195M  5.8G   4% /tmp

Any ideas?

 

[ThomasV1]

hey guys!

i think i have the same probleme...

nothing changed on the target ftp server side...

i think it's only a timeout problem on plesk side, how can i tell the backup ftps routine, that the timeout should be much longer then at the moment?

hope to find help here!

thank you und much greetings from germany, bavaria!
Thomas

plesk: 12.5.30 Update #41
os: debian 7.11

 

[ThomasV1]

hey hey!

so, i found the solution for my problem...

the ftp server which was not reachable fom plesk because a "timeout" is one in my own network...
it's a synology nas system reachable from extern via a dyndns...
my internetconnection here is from a cable provider (kabel deutschland), and they have done a update on my cable router... since this update this router (firtz box) has got not only a external ipv4 adress, also an ipv6 adress...
my synology nas now has also got assigned an ipv6 adress from the fritzbox

i now deactivated ipv6 in my network for the nas, and every thing is working again without any problems

maybe the problem is related to the ftp setting "report external IP in PASV mode" on the synology nas ftp server, because without this setting plesk backup can't connect to the nas ftp
and in this setting only a ipv4 adress is shown in the configuration dialog...

i don't exactly understand why now everything is working fine again...
maybe someone can explain me

 

[mikcanavan]

Still an issue for me, still occurring daily. Hosting provider is 1&1 - backing up to their FTP servers. We also have other servers with Plesk - but these do not have this same issue...

...any ideas?