• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

The dump rotation is failed with code 151

ChrisK

New Pleskian
Hi all,

I provide FTP backupspace and one of my users has problems performing the automatic backup. Th backupspace runs on Windows Server 2012 R2 with IIS 8.5 FTP service. The FTP server itself works fine. I can login, create directories, upload files, delete files and folders.

The user uploads his backups since December 30th. Before, we used FileZille Server but the same user experienced similar issues while other users (including me) have no problems to perform data operations.

Since other users have no problems and everything works fine, I don't know where to search for the source of the problem.

The user gave me this error message:
Code:
Unable to rotate dump: The dump rotation is failed with code '151' at /opt/psa/admin/bin/plesk_agent_manager line 1224.
; Unable to upload dump to FTP, it remains in server repository and you can manually download and upload it to FTP. Upload diagnostic message: Can not create temporary dir with the template '/var/backp_tmp/repo_transport_tmp_ngoaxa': No such file or directory.

I also attached my FTP logfile.

I googled and used the KB but I could not finde the code "151" in combination with upload/backup problems. I also double checked the permissions for creating and deleting files and folders on my server. The user has full access.

Here i have some additional informations i got from the user:
Code:
01-10-2016 11:40AM <DIR> check0 01-10-2016 03:35AM <DIR> <ULR> Repository error: Check that you have permissions to create/delete files in the repository. Transport error: unable to write file /check0/test: Can not create temporary file with the template '/var/backp_tmp/repo_transport_tmp_Kf3jYG': No such file or directory.

Code:
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 'ftps://ftp.server.tld:2021//' does not exist

The User is on Plesk 12.5 Linux hosting (but I don't know the patchlevel).
 

Attachments

  • ftplog.txt
    21.3 KB · Views: 5
hi,

i have the same problem since 3 days. did you find a resolution?did you have try to edit the ftp-account informationen? i become following error:

"Transport error: unable to list directory: Curl error: Transferred a partial file. Server response code: 450"

kind regards,

andreas
 
I have spend some days for investigating this issue. One step was to provide new credentials on a new storage cluster. Didn't work. A few days later my customer emailed me, that his hosting provider has changed some settings on his hosts and after that, everything worked fine again. Maybe this are some Plesk settings? But I have absolutly no idea what they have done. I try to get an answer from this hoster and will provide it here.
 
... thx for your feedback! i connect manually to the external ftp-repository via command-line - no problem and all files are listed. but in plesk, there are only not uploaded files are listed. i want to wait for a statement from my hoster and give feedback here!
 
Same problem here, are there any resolutions out there?
In my old DEBIAN PLESK installation it will work whiteout problems..
 
tanks for reply, i try to split the backup in 2GB parts and look what happens whit dump rotation..
 
Hi all,

I have the same problem on an ovh dedicated server :
Unable to rotate dump: The dump rotation is failed with code '151' at /opt/psa/admin/bin/plesk_agent_manager line 1224.

From my webserver, I can login to ftp server and delete files.
I am using ftp passive mode and FTPS.

Backup is working but dump rotation is not working, so I guess that server can't delete files from ftp, I manually tried to delete and it works so I don't understand what is not working on plesk.

Does anyone have a solution ?
 
Hi Christo,


not really, still got that error.. i try to split the backup in multivolume but it won´t work at all time.

Now i do thesting FTP passive mode.

[Solution] for not so mutch sikness set a high "keep" level and wait for FTP storage goes empty

then kill all old backupfiles and let it fill again.

Im sure that this error basend on a script handling error whit large files over FTP.


Greetings
 
Same error here after upgrading panel from 11.5 to 12.5

The following error occurred during the scheduled backup process:
Unable to rotate dump: The dump rotation is failed with code '151' at /usr/local/psa/admin/bin/plesk_agent_manager line 1224.

The strange thing is that if i check the backup space it's ok... the backup files are stored in the ftp space and not locally as said by someone.
How to solve?
 
Hello.
Could you please try to find error details in /var/log/plesk/PMM/backup-2016-10-xx-xx-xx-xx-xxx/backup.log. If this log does not contain any usefull information you could set '1' to FORCE_DEBUG_LOG in /usr/local/psa/admin/share/pmmcli/pmmcli-rc and re-run backup. This flag adds debug message to the log.
 
I found the log... i took one of the domains involved... this is the first part of the log. Can't find any error a part the red line below.


[29943]: 2016-10-26 01:00:07.711 DEBUG Get backup size for selected objects
[29943]: 2016-10-26 01:00:07.711 DEBUG Get backup size for domain 'MYDOMAIN.COM'
[29943]: 2016-10-26 01:00:07.711 DEBUG Domain 'MYDOMAIN.COM': BackupSizeCalculator::getDomainCustomButtonsSize started.
[29943]: 2016-10-26 01:00:07.712 DEBUG Domain 'MYDOMAIN.COM': BackupSizeCalculator::getDomainCustomButtonsSize finished. Size is 0 bytes.
[29943]: 2016-10-26 01:00:07.712 DEBUG Get backup size for domain 'MYDOMAIN.COM' finished. Size is 178487296 bytes.
[29943]: 2016-10-26 01:00:07.712 DEBUG Get backup size finished. Backup size of selected objects is 178487296 bytes
[2016-10-26 01:00:09.066|30046] INFO: pmm-ras started : /usr/local/psa/admin/sbin/pmm-ras --get-diff --listing-file /tmp/incUserDatadcIuaL --backup-file /var/lib/psa/dumps/domains/MYDOMAIN.COM/backup_user-data_1610260100.tgz --changes-file /tmp/chnjVbIbrGi --index-file /tmp/idxUYt8gifM --dependencies-file /tmp/depwXxUiHIS
[2016-10-26 01:00:09.066|30046] INFO: Repository '/var/lib/psa/dumps/': Initializing...
[2016-10-26 01:00:09.066|30046] INFO: Repository '/var/lib/psa/dumps/': Initialized
[2016-10-26 01:00:09.066|30046] INFO: Unable to find last incremental backup, because of current backup has no version mark in the file name backup_user-data_1610260100.tgz
[2016-10-26 01:00:09.066|30046] INFO: Calculate list of files to pack
[2016-10-26 01:00:09.090|30046] INFO: pmm-ras finished. Exit code: 0
[2016-10-26 01:00:10.050|30063] INFO: pmm-ras started : /usr/local/psa/admin/sbin/pmm-ras --get-diff --listing-file /tmp/incApacheFilesyLr6QQ --backup-file /var/lib/psa/dumps/domains/MYDOMAIN.COM/backup_apache-files_1610260100.tgz --changes-file /tmp/chnb914ADa5 --index-file /tmp/idxmX2dZaXG --dependencies-file /tmp/depEsbdeb60
[2016-10-26 01:00:10.050|30063] INFO: Repository '/var/lib/psa/dumps/': Initializing...
[2016-10-26 01:00:10.050|30063] INFO: Repository '/var/lib/psa/dumps/': Initialized
[2016-10-26 01:00:10.050|30063] INFO: Unable to find last incremental backup, because of current backup has no version mark in the file name backup_apache-files_1610260100.tgz
[2016-10-26 01:00:10.051|30063] INFO: Calculate list of files to pack
[2016-10-26 01:00:10.052|30063] INFO: pmm-ras finished. Exit code: 0
[2016-10-26 01:00:11.891|30135] INFO: pmm-ras started : /usr/local/psa/admin/sbin/pmm-ras --get-dump-info --dump-file-specification=domains/MYDOMAIN.COM/backup_info_1610260100.xml --with-feedback --session-path=/usr/local/psa/PMM/sessions/2016-10-26-010007.900 --verbose
............................................................

We are used to backup all domain from server1 to server2 and viceversa.
Any idea?
 
I also have this issue on one (of many) plesk servers. The server is running CentOS 5 so will be gone soon, but I thought I would add my tuppence worth. The FTP space it backs up to is fine (all the other Plesk servers manage to back up to the same FTP space), most of the backups on the box work fine, but every day some of the backups don't work and produce error code 151. Other days the same backups work fine. Other backups on the box seem to work fine. Any thoughts?
 
Here is still the same... Backups are done but many 151 errors. I have disabled notifications but Plesk should find a solution for this issue...
 
I've been having this same issue on my CentOS 6 server for years. Now I've noticed a bunch of numbered checknn files (check0, check1, check2, etc.) in my FTP directory. What the hell??
 
I've been having this same issue on my CentOS 6 server for years. Now I've noticed a bunch of numbered checknn files (check0, check1, check2, etc.) in my FTP directory. What the hell??
These are temporary directories that were created by calling pmm-ras --check-repository
The question is, why are they not being deleted?
Possible research path is to enable the debug mode, run the call pmm-ras --check-repository and examine the backup logs.
 
Great suggestion. It took me a little while to figure out the option for sending the password for pmm-ras. However, I was eventually able to get the command to work. I think the problem, more that anything, was that I didn't have passive mode turned on. Once I did that, the warning messages have ceased. It's been only a day so I'll withhold judgement that all is well just yet. But I'm hopeful.
 
Back
Top