Skip to main content

Amazon S3 backup service not running

Comments

5 comments

  • cPanelMichael
    Hello :) Please try leaving the "Folder" field blank and let us know if the issue persists. You can force a backup generation via: /usr/local/cpanel/bin/backup --force
    The backup logs are stored in: /usr/local/cpanel/logs/cpbackup/ /usr/local/cpanel/logs/cpbackup_transporter.log
    Thank you.
    0
  • thefund4
    Hello, thank you for your response. I checked our logs after leaving the folder field blank and am getting the following in cpbackup_transporter: [2014-10-01 07:05:41 -0400] info [cpbackup_transporter] Starting a "copy" operation on the "thefundingportal" destination ID "o0RxtTNGciTIlXHQEYbNXVJE". [2014-10-01 07:05:41 -0400] info [cpbackup_transporter] Validating destination path /2014-10-01 [2014-10-01 07:05:42 -0400] info [cpbackup_transporter] Path exists [2014-10-01 07:05:42 -0400] info [cpbackup_transporter] Uploading /backup/2014-10-01/accounts/thefund4.tar.gz to /2014-10-01/thefund4.tar.gz [2014-10-01 07:05:42 -0400] info [cpbackup_transporter] Attempting to upload /backup/2014-10-01/accounts/thefund4.tar.gz to /2014-10-01/thefund4.tar.gz for destination: the$ [2014-10-01 07:05:42 -0400] info [cpbackup_transporter] Upload attempt #1 starting for /backup/2014-10-01/accounts/thefund4.tar.gz to /2014-10-01/thefund4.tar.gz for destina$ [2014-10-01 07:06:55 -0400] warn [cpbackup_transporter] Upload attempt failed: RequestTimeout: Your socket connection to the server was not read from or written to within th$ Cpanel::LoggerAdapter::warn(Cpanel::LoggerAdapter=HASH(0x1bafe20), 'Upload attempt failed: RequestTimeout: Your socket connection to the server was not read from or $ Cpanel::Backup::Queue::transport_backup::attempt_to_upload_file(Cpanel::Backup::Queue::transport_backup=HASH(0x24f93b8), Cpanel::Transport::Files::AmazonS3=HASH(0x25$ Cpanel::Backup::Queue::transport_backup::process_task(Cpanel::Backup::Queue::transport_backup=HASH(0x24f93b8), cPanel::TaskQueue::Task=HASH(0x1a7d138), Cpanel::Logge$ eval {...} called at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/cPanel/TaskQueue.pm line 583 cPanel::TaskQueue::__ANON__() called at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/cPanel/StateFile.pm line 247 eval {...} called at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/cPanel/StateFile.pm line 247 cPanel::StateFile::Guard::call_unlocked(cPanel::StateFile::Guard=HASH(0x245dc60), CODE(0x25a25a8)) called at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_l$ cPanel::TaskQueue::process_next_task(cPanel::TaskQueue=HASH(0x2507b78)) called at /usr/local/cpanel/bin/cpbackup_transporter line 150 eval {...} called at /usr/local/cpanel/bin/cpbackup_transporter line 148
    I already adjusted the timeout value to the maximum amount available: 300
    0
  • cPanelMichael
    Have you checked to make sure there are no firewall or router rules resulting in the connection failure to that remote server? Thank you.
    0
  • thefund4
    [quote="cPanelMichael, post: 1741301">Have you checked to make sure there are no firewall or router rules resulting in the connection failure to that remote server? Thank you.
    I changed to a new bucket location and was able to get one file over before the timeout issue occurred again, so a connection was established long enough to get 100 MB of data across. I was able to establish an outside connection to s3.amazonaws.com from the server on both 80 and 443 so I don't think it is being blocked internally.
    0
  • cPanelMichael
    [quote="thefund4, post: 1741691">I changed to a new bucket location and was able to get one file over before the timeout issue occurred again, so a connection was established long enough to get 100 MB of data across. I was able to establish an outside connection to s3.amazonaws.com from the server on both 80 and 443 so I don't think it is being blocked internally.
    Are you able to temporarily disable the firewall to rule it out as the cause of the problem? It seems more likely a connection issue between the two servers rather than an issue with the backup script itself. Thank you.
    0

Please sign in to leave a comment.