The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Amazon S3 fails due to server time issue

Discussion in 'Data Protection' started by WorkinOnIt, Jan 14, 2017.

Tags:
  1. WorkinOnIt

    WorkinOnIt Well-Known Member

    Joined:
    Aug 3, 2016
    Messages:
    94
    Likes Received:
    5
    Trophy Points:
    8
    Location:
    UK
    cPanel Access Level:
    Root Administrator
    Hi

    I have an issue where the server time keeps slipping (by approx 40 minutes per month) and unless I log in to WHM and manually synchronise the server time, it stuffs up the Amazon s3 backup transport process.

    This means I am left with all the backups on the server, but they don't get pushed up to Amazon.

    My question is thus:

    1) How to ensure server time does not keep slipping.

    2) How to manually force the "/usr/local/cpanel/bin/cpbackup_transporter" script to run without creating a whole new backup.


    Here is the error message from the log


    Code:
    
    [2017-01-14 02:05:11 +1300] info [cpbackup_transporter] Initializing log file
    [2017-01-14 02:05:11 +1300] info [cpbackup_transporter] cPanel Backup Transporter Queue Daemon started.
    [2017-01-14 02:05:11 +1300] info [cpbackup_transporter] cpbackup_transporter - started
    [2017-01-14 02:05:11 +1300] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
    [2017-01-14 02:05:11 +1300] info [cpbackup_transporter] cpbackup_transporter - Processing next task
    [2017-01-14 02:05:11 +1300] info [cpbackup_transporter] Instantiating Object
    [2017-01-14 02:05:12 +1300] info [cpbackup_transporter] Starting a "copy_system_backup" operation on the "s3backups" destination ID "redacted".
    [2017-01-14 02:05:12 +1300] info [cpbackup_transporter] Uploading system backup file /backup/weekly/2017-01-14/system_files.tar to s3backups
    [2017-01-14 02:05:12 +1300] info [cpbackup_transporter] Validating destination path /SSD123/weekly/2017-01-14
    [2017-01-14 02:05:13 +1300] info [cpbackup_transporter] Making Path /SSD123/weekly/2017-01-14
    [2017-01-14 02:05:13 +1300] warn [cpbackup_transporter] Path creation failed:  RequestTimeTooSkewed: The difference between the request time and the current time is too large. at /usr/local/cpanel/Cpanel/LoggerAdapter.pm line 27.
    [2017-01-14 02:05:13 +1300] info [cpbackup_transporter] Error is not a reference RequestTimeTooSkewed: The difference between the request time and the current time is too large.
    
    
     
    #1 WorkinOnIt, Jan 14, 2017
    Last edited by a moderator: Jan 14, 2017
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    37,064
    Likes Received:
    1,287
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    You could ensure ntpd is running to have the server time automatically synced. There's a third-party URL on this topic at:

    CentOS Linux Install and Configure NTP to Synchronize The System Clock

    Manually running that script won't resume a failed transfer to the remote destination. You could manually transfer the archives to the remote destination, or force a new backup generation via the "/usr/local/cpanel/bin/backup --force" command.

    Thank you.
     
Loading...

Share This Page