The thing is that my time is perfectly valid... On Tue, Feb 10, 2015 at 10:50 PM, Akhil Das <ak...@sigmoidanalytics.com> wrote:
> Its with the timezone actually, you can either use an NTP to maintain > accurate system clock or you can adjust your system time to match with the > AWS one. You can do it as: > > telnet s3.amazonaws.com 80 > GET / HTTP/1.0 > > > [image: Inline image 1] > > Thanks > Best Regards > > On Wed, Feb 11, 2015 at 6:43 AM, Kane Kim <kane.ist...@gmail.com> wrote: > >> I'm getting this warning when using s3 input: >> 15/02/11 00:58:37 WARN RestStorageService: Adjusted time offset in >> response to >> RequestTimeTooSkewed error. Local machine and S3 server disagree on the >> time by approximately 0 seconds. Retrying connection. >> >> After that there are tons of 403/forbidden errors and then job fails. >> It's sporadic, so sometimes I get this error and sometimes not, what >> could be the issue? >> I think it could be related to network connectivity? >> > >
