Check that your timezone is correct as well, an incorrect timezone can make it look like your time is correct when it is skewed.
cheers On Fri, Feb 13, 2015 at 5:51 AM, Kane Kim <kane.ist...@gmail.com> wrote: > 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? >>> >> >> > -- *Franc Carter* | Systems Architect | Rozetta Technology franc.car...@rozettatech.com <franc.car...@rozettatech.com>| www.rozettatechnology.com Tel: +61 2 8355 2515 Level 4, 55 Harrington St, The Rocks NSW 2000 PO Box H58, Australia Square, Sydney NSW 1215 AUSTRALIA
