Hi, I recently moved to a new server and since then the amazon module is not working. In my drupal recent log entries I get this message:
"Amazon error returned. Code=AWS.TimestampExceedsTimeToLive, Message=Timestamp 2009-10-23T05:07:06Z is more then 900 seconds before current time 2009-10-23 07:37:20Z. //Amazon error returned. Code=AWS.InvalidSignature, Message=The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."
I shall be grateful if you are able to provide a solution to this issue.
Many thanks in advance

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

One other person has reported this, and they solved it by moving to a working machine.

I suspect the new server is not set to run on GMT, as Unix/Linux servers should. 

cat /etc/timezone

- is it your timezone?

date

is the date, time, and timezone correct?

Froggie-2’s picture

Froggie-2 commented

well, I have set the time zone on the new server exactly as it was on the old server but still getting the error messages. I am using a dedicated server and is live.

Would it work if I uninstall the module and re install it again. Thanks for your attention + support!

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

I I seriously doubt this has anything to do with the software you're running. It has to do with your server configuration. That's supported by the fact that you're having the trouble on a new server, not with a different software installation.

When you use the date command on the command line, is the date, time, and timezone all correct?

Of course, you should read the message carefully also. Did you change your keys? Are the two keys correct in Amazon settings?

Froggie-2’s picture

Froggie-2 commented

This certainly is a issue related to the server but I am trying to find a way out to have it solved. I have not checked the date command on the command line as I use Plesk to configure the server.
However, the keys are correct in the Amazon Settings.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

You'll need to get someone to check the server at the command line with the commands I gave in #1

Froggie-2’s picture

Froggie-2 commented

I checked the server through command line and reset the time and date to GMT settings. Still no luck with the Amazon Store.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

I'm not there to see what you did, but you still haven't answered the questions in #1. Please answer the questions in #1. When you "reset the server" what did you do? Use the date command to change the time? Change /etc/timezone? Change the time at the BIOS level? change $TZ?

Froggie-2’s picture

Froggie-2 commented

What I did was to change the timezone of the server to GMT using Plesk and thereafter run the command line using shell commands to check the date which showed the date to be 23rd October 2009 which is correct and then the GMT time as: 08:05:56

The command line output is as follows:

login as: boratz
boratz@xxx.xxx.xxx.xx's password:
Last login: Fri Oct 23 08:05:56 2009 from xx.xx.xxx.xx
-bash-3.2$ su
Password:
[root@ip-xxx-xxx-xxx-xx boratz]# cat /etc/timezone
cat: /etc/timezone: No such file or directory
[root@ip-xxx-xxx-xxx-xx boratz]# timezone
bash: timezone: command not found
[root@ip-xxx-xxx-xxx-xx boratz]# date
Fri Oct 23 08:19:36 GMT 2009
[root@ip-xxx-xxx-xxx-xx boratz]# time

real 0m0.000s
user 0m0.000s
sys 0m0.000s
[root@ip-xxx-xxx-xxx-xx boratz]#

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

That's not what you need to do.

The internal clock of the server needs to be GMT. That's what is used with the Amazon request. Every machine in the world needs to internally run on GMT. The display for you should be your own timezone and the correct time in that timezone.

Neither you nor I knows what Plesk is telling you with its timezone configuration.

Please use the command line to execute the two commands I specified.

Please follow up with your own server support/hosting support. Or follow up with Amazon. And please report back here when you solve the problem.

You need to talk to someone who understands how a server needs to be set up.

If you want to get me root command-line access (ssh) to the system I will take a look. You can send details via the contact form.

Froggie-2’s picture

Froggie-2 commented

I modified the system time to my local time using Plesk and the Amazon Module started to work on the new server. Thanks for your time & support! I appreciate it with gratitude.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Fixed

Excellent! Thanks for reporting back.

I assume you mean that you set the timezone to your local time and then set the time correctly.

Froggie-2’s picture

Froggie-2 commented

Yep, exactly!

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Title: Amazon Error after moving to another server » AWS.TimestampExceedsTimeToLive: Timestamp is more then 900 seconds before current time

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.