Unable to rotate dump: The dump rotation is failed with code '121'

[Kaos1337]

Hi,
I have enabled the backup rotation of some websites to my "Personal FTP Repository", the problem is that Plesk is unable to do it due this error:

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

I read here http://kb.odin.com/en/122130 that it should be solved but I have the version 12.0.18 Update #33, why does it persist?
Thank you.

 

[abdi]

I see a same thread here:
http://talk.plesk.com/threads/error-backup-ftp.305151/

 

[Kaos1337]

yes but their error is different (126) and their situation doesn't allow to backup an .xml file, for me is different, the backup finish successfully and only the deletion of the oldest files doesn't happen.

 

[abdi]

Hello Kaos,
Dump rotation occurs on last step of backup -- after upload is done. However, if control channel is closed error 121 occurs which means 'remote I/O' error.

It is a general error representing issues with FTP connection. The problem can be reported in logs in /usr/local/psa/PMM/sessions that it is timeout on FTP communication.

Check it and try to modify configuration of remote FTP server and increase timeout to one hour.

 

[Kaos1337]

I found this:

[2015-02-09 03:03:21.330|32464] INFO: pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --rotate-dump --dump-rotation=14 --guid=e46f0feb-1b2b-4a6a-8fc0-05a48e498440 --dump-specification=/<**PATH**>/backup_<**WEBSITE NAME**>_1502090213.tar --dump-storage=ftp://<**USER**>@<**IP**> --session-path=/usr/local/psa/PMM/sessions/2015-02-09-021302.393 --verbose
[2015-02-09 03:03:21.390|32464] INFO: Repository 'ftp://<**IP**>': Initializing...
[2015-02-09 03:03:21.391|32464] INFO: Repository 'ftp://<**IP**>': Initialized
[2015-02-09 03:03:21.391|32464] INFO: Repository 'ftp://<**IP**>': Rotate file backups is started
[2015-02-09 03:03:21.392|32464] INFO: Ftp init url ftp://<**IP**>/<**PATH**>
[2015-02-09 03:03:22.472|32464] INFO: CurlError[76931fac-9dab-42b3-86c2-48b87d6ae33f]: Curl error: Access denied to remote resource [./ftp.cpp:559]
void plesk::tFtpConnection::ListEx(std::vector<plesk::FtpFileInfo, std::allocator<plesk::FtpFileInfo> >&)
[2015-02-09 03:03:22.473|32464] INFO: pmm-ras finished. Exit code: 121

I increased the connection timeout to 3600 seconds but it didn't solve the problem, the log in fact is showing another issue: "Curl error: Access denied to remote resource", this is strange, I tried to login and use the ftp user via filezilla and I can do what I want (delete some olds backups too).

 

[IgorG]

I think this problem is addressed in the following KB - http://kb.odin.com/en/124055

 

[wmgilligan27]

I am receiving this, and do not see any info via Google.
Following error occurred during scheduled backup process:
Unable to rotate dump: The dump rotation is failed with code '152' at..

Any info on the cause and fix?

 

[vlikhtanskiy]

Hi @wmgilligan27

I have several questions:
1. What's your Plesk version and OS? You put here output of command "plesk version"
2. Could you please post the full error message starting with "Unable to rotate dump: The dump rotation is failed with code '152' at..". I suppose the file and line in the file are specified there. It'll help with investigation of the issue.

 

[wmgilligan27]

1:
Product version: 12.5.30
Build date: 2015/08/26 19:00
OS version: CentOS 6.6
Revision: 344620
Architecture: 64-bit
Wrapper version: 1.2
============
2: (received via email with subject line: "<mydomain.COM> Error occurred during scheduled backup")

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

 

[IgorG]

Code '152' means following:

# perror 152
MySQL error code 152: Cannot delete a parent row

I would suggest you check mysql logs. Looks like there is some kind of inconsistency or corrupted tables.

 

[SyedTech]

I got code 151 instead 152.

OS: CentsOS 6.7 (Final) - 64 bits
Plesk: 12.5.30 Update #11, last updated at Nov 23, 2015 04:03 AM

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 1246.

Where should I look to solve this issue?

Regards

 

[abdi]

The above Igor's suggestion still applies as:

#  perror 151 
MySQL error code 151: Cannot add a child row

 

[SyedTech]

The above Igor's suggestion still applies as:

#  perror 151
MySQL error code 151: Cannot add a child row

I am surprise "MySQL error code 151: Cannot add a child row".
What is the purpose of adding a child row in MySQL? I think only database export operation is performed during backup.
Please correct me if I am wrong and where should I start to solve this issue?

Regards

 

[abdi]

The MySQL error code 151: Cannot add a child row comes from MySQL and NOT Plesk!

More here: https://major.io/2007/08/09/mysql-error-codes/

There many possible causes that could trigger that error, such as to say When MySQL can't create a table due to a foreign key constraint problem, it returns the same error..

You would need a deeper investigation to get the actual cause that triggered it...