SQSError: 400 Bad Request on CentOS 5.6

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Start with CentOS 5.6, python2.6, boto2.0rc1 (also tried boto1.9b)

Also fails with python2.4 and boto1.9b from epel repo

2. run the following:

[boto-2.0rc1]# python2.6
Python 2.6.5 (r265:79063, Feb 28 2011, 21:55:45) 
[GCC 4.1.2 20080704 (Red Hat 4.1.2-50)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from boto.sqs.connection import SQSConnection
>>> conn = SQSConnection( 'xxxxx', 'xxxxx' )
>>> conn.get_all_queues()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "boto/sqs/connection.py", line 222, in get_all_queues
    return self.get_list('ListQueues', params, [('QueueUrl', Queue)])
  File "boto/connection.py", line 683, in get_list
    raise self.ResponseError(response.status, response.reason, body)
boto.exception.SQSError: SQSError: 400 Bad Request
<?xml version="1.0"?>
<ErrorResponse 
xmlns="http://queue.amazonaws.com/doc/2009-02-01/"><Error><Type>Sender</Type><Co
de>RequestExpired</Code><Message>Request has expired. Timestamp date is 
2011-06-08T15:00:51Z.</Message><Detail/></Error><RequestId>68ac8c4d-6e3e-4727-88
86-cbbba825074f</RequestId></ErrorResponse>
>>> 

What is the expected output? What do you see instead?
On Ubuntu Lucid, python2.6 and version 1.9b I get:
root@cloud:~# python
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) 
[GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from boto.sqs.connection import SQSConnection
>>> conn = SQSConnection( 'xxxxxx', 'xxxx' )
>>> conn.status()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: SQSConnection instance has no attribute 'status'
>>> conn.get_all_queues()
[<boto.sqs.queue.Queue instance at 0x21f92d8>, <boto.sqs.queue.Queue instance 
at 0x21f9320>]

What version of the product are you using? On what operating system?
-- see above --

Please provide any additional information below.

Original issue reported on code.google.com by idb...@pugetworks.com on 8 Jun 2011 at 10:50

[GoogleCodeExporter]

This error is commonly seen when the system clock on the client machine is off, 
either not set to the correct time or some problem with time zones.  Have you 
checked that?

Original comment by Mitch.Ga...@gmail.com on 9 Jun 2011 at 12:18

[GoogleCodeExporter]

That was it!

I'm running the django dev on a temporary xen box, which (being  
temporary) hasn't been fully configured.

Thank you for the quick response.

Bill

Bill Levering
idbill@pugetworks.com
KFP: 38F4 8C79 A763 7437 B7E5  92D8 CBAA 9DC6 87FC 137E

Original comment by idb...@pugetworks.com on 9 Jun 2011 at 3:57