Unable to prune transport S3

bbf

Member
Feb 21, 2008
9
0
51
WHM 60.0 (build 36)
CENTOS 7.3 x86_64 virtuozzo

Backing accounts to S3.
Files are successfully transferred to S3.

But getting this email error every time the backup runs:

Code:
SUBJECT: Backup transport errors.

BODY:
Transport errors encountered.
The system encountered errors during transport of the backup files. Below is a preview of the attached log file.

Preview of transport errors log:
Unable to prune transport “S3”
Unable to remove outdated backup: The server has stopped responding at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Amazon/S3/Bucket.pm line 333.
This notice is the result of a request from “cpbackup”.
The host sent me the log:

Code:
2017-02-04 01:22:56 -0500] info [cpbackup_transporter] Attempting to upload /backup/2017-02-04/accounts/tbgas.tar.gz to /2017-02-
04/tbgas.tar.gz for destination: S3
[2017-02-04 01:22:56 -0500] info [cpbackup_transporter] Upload attempt #1 starting for /backup/2017-02-04/accounts/tbgas.tar.gz to
/2017-02-04/tbgas.tar.gz for destination: S3
[2017-02-04 01:22:56 -0500] info [cpbackup_transporter] Successful transfer of /backup/2017-02-04/accounts/tbgas.tar.gz to /2017-0
2-04/tbgas.tar.gz for destination S3
[2017-02-04 01:22:56 -0500] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2017-02-04 01:22:56 -0500] info [cpbackup_transporter] cpbackup_transporter - Processing next task
[2017-02-04 01:22:56 -0500] info [cpbackup_transporter] Instantiating Object
[2017-02-04 01:22:56 -0500] info [cpbackup_transporter] Starting a "prune" operation on the "S3" destination ID "REDACTED".
[2017-02-04 01:22:56 -0500] info [cpbackup_transporter] Performing prune operation, retaining 5 items on: S3
[2017-02-04 01:22:56 -0500] warn [cpbackup_transporter] Unable to prune: The server has stopped responding at /usr/local/cpanel/3
rdparty/perl/522/lib64/perl5/cpanel_lib/Amazon/S3/Bucket.pm line 333.
at /usr/local/cpanel/Cpanel/LoggerAdapter.pm line 27.
Cpanel::LoggerAdapter::warn(Cpanel::LoggerAdapter=HASH(0xcc1298), "Unable to prune: The server has stopped responding at
/usr/l"...) called at /usr/local/cpanel/Cpanel/Backup/Queue.pm line 535
 
Last edited by a moderator:

SB-Nick

Well-Known Member
Aug 26, 2008
175
9
68
cPanel Access Level
Root Administrator
I would make sure that cPanel is able to validate the S3 destination. If its validated already, try increasing the timeouts.
 

bbf

Member
Feb 21, 2008
9
0
51
I would make sure that cPanel is able to validate the S3 destination. If its validated already, try increasing the timeouts.

"Files are successfully transferred to S3." so the destination is validated.
 

teo_

Member
Nov 21, 2008
13
1
53
Same issue here with S3.
I have another destination for the backup with SFTP and I have the unable to prune error there too.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,202
363
Hello,

Check to ensure you have setup a valid policy using the steps quoted below:

1. Log in to your AWS console.
2. Under Security, Identity, & Compliance, click IAM.
3. Click Policies in the left navigation bar.
4. Click Get Started.
Note: This option only displays the first time that you create a bucket. If this is not your first time to create a bucket, then this step will not display.
5. Click Create Policy near the top of the interface.
6. Click Select next to the Create your own policy option.
7. Enter a policy name.
8. Create a policy document that resembles the following example:

Code:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "CpFilePermission",
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": [
                "arn:aws:s3:::$BUCKET/*",
                "arn:aws:s3:::$BUCKET"
            ]
        }
    ]
}
Replace all references to $BUCKET with your policy name.
9. Click Validate Policy to confirm that your policy specifications function properly.
10. Click Create Policy.
Note that internal case CPANEL-10498 is included in cPanel version 62 to ensure the remote destination validation test fails when the necessary privileges are not in-place, and updated documentation on how to configure Amazon S3 destinations is scheduled for publication in the near future.

Thank you.
 
  • Like
Reactions: Daveyy