Project

General

Profile

Bug #63468

Fix AWS S3 Cloud Sync hostname resolving to s3.None.amazonaws.com

Added by Bug Clerk almost 3 years ago. Updated almost 3 years ago.

Status:
Done
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Recently updated to Freenas 11.2

FreeBSD freenas.localdomain 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+3a9793238ff(freenas/11.2-stable): Thu Nov 15 13:51:02 EST 2018 :/freenas-11.2-releng/freenas/_BE/objs/freenas-11.2-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64

I just noticed that my cloud sync task is now failing, which was previously working, prior to update. From the available log file I found:

2018/11/27 10:44:42 ERROR : : error reading destination directory: RequestError: send request failed
caused by: Get https://s3.None.amazonaws.com/xxxxxxxx?delimiter=%2F&max-keys=1000&prefix=xxxxxxx%2F: dial tcp: lookup s3.None.amazonaws.com on 8.8.8.8:53: no such host
2018/11/27 10:44:42 INFO : S3 bucket xxxxxxxx path xxxxxxxx/: Waiting for checks to finish
2018/11/27 10:44:42 INFO : S3 bucket xxxxxxxx path xxxxxxxx/: Waiting for transfers to finish
2018/11/27 10:44:42 ERROR : S3 bucket xxxxxxxx path xxxxxxxx/: not deleting files as there were IO errors
2018/11/27 10:44:42 ERROR : S3 bucket xxxxxxxx path xxxxxxxx/: not deleting directories as there were IO errors
2018/11/27 10:44:42 ERROR : Attempt 1/3 failed with 1 errors and: not deleting files as there were IO errors

I believe this has something to do with the hostname DNS is trying to resolve (s3.None.amazonaws.com). I've tried to workaround this by specifying valid Endpoint URLs (s3.amazonaws.com) and here are the results:

2018/11/27 11:00:52 ERROR : : error reading destination directory: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'None' is wrong; expecting 'us-east-1'


Related issues

Copied from FreeNAS - Bug #60135: Fix AWS S3 Cloud Sync hostname resolving to s3.None.amazonaws.comDone

History

#1 Updated by Bug Clerk almost 3 years ago

  • Copied from Bug #60135: Fix AWS S3 Cloud Sync hostname resolving to s3.None.amazonaws.com added

#2 Updated by Bug Clerk almost 3 years ago

  • Target version changed from Master - FreeNAS Nightlies to 11.2-U2

#3 Updated by Bug Clerk almost 3 years ago

  • Status changed from Unscreened to In Progress

#4 Updated by Bug Clerk almost 3 years ago

  • Status changed from In Progress to Ready for Testing

#5 Updated by Dru Lavigne almost 3 years ago

  • Subject changed from AWS S3 Cloud Sync hostname resolving to s3.None.amazonaws.com to Fix AWS S3 Cloud Sync hostname resolving to s3.None.amazonaws.com
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#6 Updated by Vladimir Vinogradenko almost 3 years ago

  • Needs QA changed from Yes to No

#7 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Ready for Testing to Done

Also available in: Atom PDF