2017-03-01 5 views
0

셀러리를 사용하기 위해 New Relic을 구성하려고합니다. Amazon EC2 w/CentOS 7에서 호스팅되는 Django 응용 프로그램을 작성 중입니다.셀러리와 새 유적 통합

셀러리에 대한 New Relic을 구성하려면 /etc/systemd/system/celery.service에서 다음 행을 편집해야한다고 생각했습니다. :

ExecStart=/home/myuser/project/venv/bin/celery -A project worker -l info -c 4



과로 변경 :

ExecStart=/home/myuser/project/newrelic.ini newrelic-admin run-program celery -A project worker -l info -c 4

그러나 나는 다음과 같은 오류를 참조하십시오

012,351을
[[email protected] system]# systemctl daemon-reload 
[[email protected] system]# systemctl restart celery 
[[email protected] system]# systemctl status celery.service -l 
● celery.service - datasidekick celery service 
    Loaded: loaded (/etc/systemd/system/celery.service; enabled; vendor preset: disabled) 
    Active: failed (Result: start-limit) since Wed 2017-03-01 04:16:33 UTC; 900ms ago 
    Process: 22969 ExecStart=/home/datasidekick/datasidekick/newrelic.ini newrelic-admin run-program /home/datasidekick/datasidekick/venv/bin/celery -A datasidekick worker -l info -c 4 (code=exited, status=203/EXEC) 
Main PID: 22969 (code=exited, status=203/EXEC) 

Mar 01 04:16:33 ip-172-31-60-222.ec2.internal systemd[1]: Unit celery.service entered failed state. 
Mar 01 04:16:33 ip-172-31-60-222.ec2.internal systemd[1]: celery.service failed. 
Mar 01 04:16:33 ip-172-31-60-222.ec2.internal systemd[1]: celery.service holdoff time over, scheduling restart. 
Mar 01 04:16:33 ip-172-31-60-222.ec2.internal systemd[1]: start request repeated too quickly for celery.service 
Mar 01 04:16:33 ip-172-31-60-222.ec2.internal systemd[1]: Failed to start datasidekick celery service. 
Mar 01 04:16:33 ip-172-31-60-222.ec2.internal systemd[1]: Unit celery.service entered failed state. 
Mar 01 04:16:33 ip-172-31-60-222.ec2.internal systemd[1]: celery.service failed. 

내가 잘못하고있는 것이 확실하지 않습니다. 어떤 도움이라도 대단히 감사합니다!

답변