In Progress [CPANEL-25619] The system could not prune backups

[Luis Mota]

Hello guys, my problem is simple.
Everything works but I still get an error saying that "The system could not prune the "amazingfolder" (yesterday folder), but actually that folder don't exist anymore after the backup routine.

The first time I tried there was an error on some site (cpanel account) permissions and the system was unable to delete that folder but now everything is fixed and I still get the same error dispite the fact that everything goes fine, at least it seems to go.

 

[GOT]

Strange, could we see the logs? Not the entire thing, just that one part.

 

[Luis Mota]

I think I found the problem "The system could not prune the “[_1]” directory due to an error."

Now I need to find "[_1]" directory -.-'

edit:

 

[Luis Mota]

I can't find this dir.
What is strange is that the error is displayed after the .master.meta sync

[2019-05-20 02:40:30 +0100] info [cpbackup_transporter] Upload attempt #1 starting for /backup/2019-05-20/accounts/.master.meta to backup_s3/2019-05-20/accounts/.master.meta for destination:  Nameofmybackupdestination
[2019-05-20 02:40:30 +0100] info [cpbackup_transporter] Successful incremental transfer of /backup/2019-05-20/accounts/.master.meta to backup_s3/2019-05-20/accounts/.master.meta for destination Nameofmybackupdestination
[2019-05-20 02:40:30 +0100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2019-05-20 02:40:30 +0100] info [cpbackup_transporter] cpbackup_transporter - Waiting up to 299s for new tasks
[2019-05-20 02:40:31 +0100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2019-05-20 02:40:31 +0100] info [cpbackup_transporter] cpbackup_transporter - Waiting up to 298s for new tasks
[2019-05-20 02:40:32 +0100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2019-05-20 02:40:32 +0100] info [cpbackup_transporter] cpbackup_transporter - Waiting up to 297s for new tasks

( ... )

[2019-05-20 02:45:30 +0100] info [cpbackup_transporter] cpbackup_transporter - Waiting up to 0s for new tasks
[2019-05-20 02:45:31 +0100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2019-05-20 02:45:31 +0100] info [cpbackup_transporter] cpbackup_transporter - Exiting - the queue has been emptied; no more work to do after waiting for 300s
[2019-05-20 02:45:31 +0100] info [cpbackup_transporter] cPanel Backup Transporter Queue Daemon is being stopped.
[2019-05-20 02:47:46 +0100] info [cpbackup_transporter] Initializing log file
[2019-05-20 02:47:46 +0100] info [cpbackup_transporter] cpbackup_transporter - parent starting
[2019-05-20 02:47:46 +0100] info [cpbackup_transporter] cpbackup_transporter - child starting
[2019-05-20 02:47:46 +0100] info [cpbackup_transporter] cPanel Backup Transporter Queue Daemon started.
[2019-05-20 02:47:46 +0100] info [cpbackup_transporter] cpbackup_transporter - started
[2019-05-20 02:47:46 +0100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2019-05-20 02:47:46 +0100] info [cpbackup_transporter] cpbackup_transporter - Processing next task
[2019-05-20 02:47:47 +0100] info [cpbackup_transporter] Instantiating Object
[2019-05-20 02:47:47 +0100] info [cpbackup_transporter] Starting a "prune" operation on the "Nameofmybackupdestination" destination ID "usi2ESkroDPNCGkcqDUkoTvT".
[2019-05-20 02:47:47 +0100] info [cpbackup_transporter] Base path for destination is backup_s3/
[2019-05-20 02:47:47 +0100] info [cpbackup_transporter] Performing prune operation, retaining 1 items on:  Metodo Rsync - para incremental
[2019-05-20 02:47:48 +0100] info [cpbackup_transporter] Pruning backup directory:  backup_s3/2019-05-19, from Nameofmybackupdestination
[2019-05-20 02:54:46 +0100] info [cpbackup_transporter] ERROR: Pruning backup_s3/2019-05-19 from Nameofmybackupdestination:  ssh slave failed: timed out
[2019-05-20 02:54:46 +0100] info [cpbackup_transporter] The system could not prune the “[_1]” directory due to an error.
[2019-05-20 02:54:46 +0100] info [cpbackup_transporter] Read the go.cpanel.net/directorypruning documentation for solutions to successfully prune the directory.
[2019-05-20 02:54:46 +0100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks

 

[cPanelMichael]

Hello @Luis Mota,

Can you open a support ticket so we can take a closer look at your system to see why this occurred? You can post the ticket number here and we'll link this thread to it.

Thank you.

 

[Luis Mota]

Good Morning Michael, here it goes 12356745

 

[cPanelMichael]

Hello,

To update, internal case CPANEL-25619 is open to address an issue where false backup pruning failures are reported when the rm command times out on the remote backup destination. The pruning itself should continue to succeed despite the errors reported in /usr/local/cpanel/logs/cpbackup_transporter.log.

I'll monitor the status of this case and update this thread for more information as it becomes available.

Thank you.

 

[Luis Mota]

I'll apreciate that.
Thanks

 

[cheke]

I Have the same issue, any update of this?

thanks

 

[cPanelMichael]

I Have the same issue, any update of this?

Hello

There's no update to report at this time. I'll continue to monitor the case and update this thread with more information as it becomes available. Note the pruning itself should continue to succeed despite the errors reported in /usr/local/cpanel/logs/cpbackup_transporter.log.

Thank you.

 

[vf-hostmaster]

I believe I am also experiencing this issue. We get an alert about backup transport errors

The log states
[2023-06-21 02:32:36 -0500] info [cpbackup_transporter] ERROR: Pruning ******* from *******: ssh slave failed: timed out
[2023-06-21 02:32:36 -0500] info [cpbackup_transporter] The system could not prune the “*******” directory due to an error.


But the folder it was trying to prune looks like it was removed as desired.

 

[FrancXPT]

Aug 2023 Problem still exist without anything to fix it, any update of this?

Thanks

 

[cPRex]

@FrancXPT - can you post the specific error you're seeing from the log?

 

[FrancXPT]

@FrancXPT - can you post the specific error you're seeing from the log?

All Backups are marked complete, but the Transport Always has an error:

Unable to prune transport “XXX.XXXX.com”
Error pruning “2023-08-18” from “XXX.XXXX.com”: ssh slave failed: timed out
The system could not prune the “2023-08-18” directory due to an error.
Read the go.cpanel.net/directorypruning documentation for solutions to successfully prune the directory.

On inspection, Remote Backups seems fine.
I'm using incremental backups and rsync for remote server.

 

[cPRex]

Thanks for the additional details. That is definitely the same error. Let me see if the team wants to pick up this case, I know it's a few years old at this point. I'll reply with more details once I have them!

 

[cPRex]

I've let the backup team know about the issue, but there isn't any type of ETA for getting this resolved. Since there's only been a few reports of this issue over the last several years, it isn't something critical, and since you know things are working well it's safe to ignore that error.

 

[FrancXPT]

I've let the backup team know about the issue, but there isn't any type of ETA for getting this resolved. Since there's only been a few reports of this issue over the last several years, it isn't something critical, and since you know things are working well it's safe to ignore that error.

Thanks, I hope it gets fixed soon, I'm suggestion to let us specify a bigger timeout than 300sec for big servers this problem is happening on multiple servers when choosing incremental backups.
Thanks again for your response and have a good day.