From asteriskeasy at gmail.com Fri Dec 4 06:26:10 2009 From: asteriskeasy at gmail.com (Asterisk User) Date: Fri, 4 Dec 2009 16:56:10 +0530 Subject: [s3-dev] Help on 'The difference between the request time and the current time' Message-ID: <4710ff650912040326x29962d8eu424965f0619df8a6@mail.gmail.com> Hi All, I need your help on AWS::s3. I have several files being uploaded on S3 through ruby script using aws/s3 gem. time on my system is in sync with Amazon. I noticed while uploading files having bit larger sizes, following exception is being thrown from Amazon... **** The difference between the request time and the current time is too large. **** As I know this can happen if the system time is in not sync with Amazon which is not the case with me. Further, it (same script) uploads some other files successfully. One more thing, If amazon throws such exception then why not it removes that object from Bucket. Thanks, --Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdchaney at michaelchaney.com Fri Dec 4 10:47:25 2009 From: mdchaney at michaelchaney.com (Michael Chaney) Date: Fri, 4 Dec 2009 09:47:25 -0600 Subject: [s3-dev] Help on 'The difference between the request time and the current time' In-Reply-To: <4710ff650912040326x29962d8eu424965f0619df8a6@mail.gmail.com> References: <4710ff650912040326x29962d8eu424965f0619df8a6@mail.gmail.com> Message-ID: <3b456edd0912040747p7702c9a5ha75a1deff17d3d5d@mail.gmail.com> On Fri, Dec 4, 2009 at 5:26 AM, Asterisk User wrote: > Hi All, > I need your help on AWS::s3. > I have several files being uploaded on S3 through ruby script using aws/s3 > gem. > time on my system is in sync with Amazon. > I noticed while uploading files having bit larger sizes, following exception > is being thrown from Amazon... > **** > The difference between the request time and the current time is too large. > **** > As I know this can happen if the system time is in not sync with Amazon > which is not the case with me. > Further, it (same script) uploads some other files successfully. > One more thing, If amazon throws such exception then why not it removes that > object from Bucket. Your problem is that your internet connection is caching at some point upstream from you, so when you're machine thinks it's done uploading, it's not. Probably if you read the metadata for the object you just uploaded, it would provide the proper pause for you. Michael -- Michael Darrin Chaney, Sr. mdchaney at michaelchaney.com http://www.michaelchaney.com/ From asteriskeasy at gmail.com Mon Dec 7 03:40:16 2009 From: asteriskeasy at gmail.com (Asterisk User) Date: Mon, 7 Dec 2009 14:10:16 +0530 Subject: [s3-dev] Help on 'The difference between the request time and the current time' In-Reply-To: <3b456edd0912040747p7702c9a5ha75a1deff17d3d5d@mail.gmail.com> References: <4710ff650912040326x29962d8eu424965f0619df8a6@mail.gmail.com> <3b456edd0912040747p7702c9a5ha75a1deff17d3d5d@mail.gmail.com> Message-ID: <4710ff650912070040v6ee820b7wd3f9114a38770e0a@mail.gmail.com> Michael, Thanks for your prompt reply. I tried to read metadata for such objects but there was nothing in it. And I want to know, why amazon doesn't remove such objects from Bucket if an exception is thrown. On Fri, Dec 4, 2009 at 9:17 PM, Michael Chaney wrote: > On Fri, Dec 4, 2009 at 5:26 AM, Asterisk User > wrote: > > Hi All, > > I need your help on AWS::s3. > > I have several files being uploaded on S3 through ruby script using > aws/s3 > > gem. > > time on my system is in sync with Amazon. > > I noticed while uploading files having bit larger sizes, following > exception > > is being thrown from Amazon... > > **** > > The difference between the request time and the current time is too > large. > > **** > > As I know this can happen if the system time is in not sync with Amazon > > which is not the case with me. > > Further, it (same script) uploads some other files successfully. > > One more thing, If amazon throws such exception then why not it removes > that > > object from Bucket. > > Your problem is that your internet connection is caching at some point > upstream from you, so when you're machine thinks it's done uploading, > it's not. > > Probably if you read the metadata for the object you just uploaded, it > would provide the proper pause for you. > > Michael > -- > Michael Darrin Chaney, Sr. > mdchaney at michaelchaney.com > http://www.michaelchaney.com/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: