2017-03-07 30 views
1

我試圖讓問題與亞馬遜SQS一起工作,但任務未運行。但是我的任務運行在開箱即用的RabbitMQ你如何獲得亞馬遜SQS與Django芹菜

下面是我曾嘗試(等等)的鏈接

Celery with Amazon SQS

https://www.caktusgroup.com/blog/2011/12/19/using-django-and-celery-amazon-sqs/

他們似乎相當過時。我暗示我不要收到任何消息,當我登錄到亞馬遜的控制檯,但我看到芹菜日誌的活動表明他們正在與亞馬遜溝通

DEBUG b'<?xml version="1.0"?><ReceiveMessageResponse xmlns="http://queue.amazonaws.com/doc/2012-11-05/"><ReceiveMessageResult/><ResponseMetadata><RequestId>f8d10c14-99f7-520b-a58d-5d2cc203ad8b</RequestId></ResponseMetadata></ReceiveMessageResponse>' 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Method: GET 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Path: /967610578225/transfer_files 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Data: 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Headers: {} 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Host: eu-west-1.queue.amazonaws.com 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Port: 443 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Params: {'Version': '2012-11-05', 'Action': 'ReceiveMessage', 'WaitTimeSeconds': 0, 'MaxNumberOfMessages': 4} 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG Token: None 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log DEBUG CanonicalRequest: 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log GET 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log /967610578225/transfer_files 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log Action=ReceiveMessage&MaxNumberOfMessages=4&Version=2012-11-05&WaitTimeSeconds=0 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log host:eu-west-1.queue.amazonaws.com 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log x-amz-date:20170307T065652Z 
    Mar 7 08:56:52 ip-172-31-41-253 e-celery-worker.log 
, 'Authorization': 'AWS4-HMAC-SHA256 Credential=xxxxxx/20170307/eu-west-1/sqs/aws4_request,SignedHeaders=host;x-amz-date,Signature=xxxxxx', 'User-Agent': 'Boto/2.45.0 Python/3.4.3 Linux/4.1.17-22.30.amzn1.x86_64', 'X-Amz-Date': '20170307T065652Z'} 
    Mar 7 08:56:52 ip-172-31-41-253 eright-celery-worker.log DEBUG Response headers: [('Server', 'Server'), ('Date', 'Tue, 07 Mar 2017 06:56:52 GMT'), ('Content-Type', 'text/xml'), ('Content-Length', '240'), ('Connection', 'keep-alive'), ('x-amzn-RequestId', 'bbad9a79-f65e-568d-aaeb-cb41adaa390d')] 

我的設置

BROKER_TRANSPORT = 'sqs' 
BROKER_TRANSPORT_OPTIONS = { 
    'region': 'eu-west-1', 
    'polling_interval': 2, 
    'visibility_timeout': 3600, 
} 
BROKER_USER = 'xxx' 
BROKER_PASSWORD = 'xxxxx/xxxx' 

CELERY_IMPORTS = (
    'apps.files.tasks', 
) 

CELERY_QUEUES = { 
    'default': { 
     'binding_key': 'default' 
    }, 

    # Files 
    'files_copy_paste': { 
     'binding_key': 'files.copy.paste' 
    }, 
} 

任何幫助將極大地讚賞

回答

1

我有Django的+芹菜正與SQS以下設置:

import urllib.parse 

# Defined in environment settings 
AWS_ACCESS_KEY_ID = os.environ["AWS_ACCESS_KEY_ID"] 
AWS_SECRET_ACCESS_KEY = os.environ["AWS_SECRET_ACCESS_KEY"] 

CELERY_BROKER_URL = 'sqs://{0}:{1}@'.format(
    urllib.parse.quote(AWS_ACCESS_KEY_ID, safe=''), 
    urllib.parse.quote(AWS_SECRET_ACCESS_KEY, safe='') 
) 

CELERY_BROKER_TRANSPORT_OPTIONS = { 
    'region': 'sqs.eu-west-1', 
    'queue_name_prefix': 'celery-' 
} 

您是否指定了您的AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEY

我還發現我必須在我的地區名稱前加上sqs.

+0

嗨@Isaac,問題是我需要爲S3設置AWS_ACCESS_KEY_ID和AWS_SECRET_ACCESS_KEY,所以我使用s3用戶訪問。而對於經紀人我asumed BROKER_USER ='xxx' BROKER_PASSWORD ='xxxxx/xxxx'是我把我的訪問密鑰和ID。你把這個區域放在前面的點是我沒有嘗試過的唯一的東西,我會馬上得到它,並讓你知道它是否有效 –

+0

@TawandaMinya嘿,它的工作? :)如果是這樣,請接受我的回答。 –

+0

嗨,還沒有機會測試呢。但是,當我確定將 –