You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/04/08 21:01:14 UTC

[GitHub] [airflow] don1uppa opened a new issue, #22868: There is no handler for BACKEND=sqs in entrypoint_prod.sh function wait_for_connection

don1uppa opened a new issue, #22868:
URL: https://github.com/apache/airflow/issues/22868

   ### Apache Airflow version
   
   2.2.5 (latest released)
   
   ### What happened
   
   Actually this is looking more like a bug see error below. I think I am configuring it correctly.
   Might be a configuration issue see https://github.com/apache/airflow/issues/22863
   
   
   
   From a docker container running on an EC2 I'm trying to use AWS sqs as my celery broker.
   I'm using ec2 IAM credentials so I set
   
   broker_url = sqs://
   
   According to https://docs.celeryq.dev/en/latest/getting-started/backends-and-brokers/sqs.html
   If you are using IAM roles on instances, you can set the BROKER_URL to: sqs:// and kombu will attempt to retrieve access tokens from the instance metadata.
   
   The error I get is:
   airflow-worker-1_1 |
   airflow-worker-1_1 | ### BACKEND=sqs
   airflow-worker-1_1 | DB_HOST=None
   airflow-worker-1_1 | DB_PORT=
   airflow-worker-1_1 | ....................
   airflow-worker-1_1 | ERROR! Maximum number of retries (20) reached.
   airflow-worker-1_1 |
   airflow-worker-1_1 | Last check result:
   airflow-worker-1_1 | $ run_nc 'None' ''
   airflow-worker-1_1 | Traceback (most recent call last):
   airflow-worker-1_1 | File "", line 1, in
   airflow-worker-1_1 | socket.gaierror: [Errno -5] No address associated with hostname
   airflow-worker-1_1 | Can't parse as an IP address
   
   I traced the source of the error to entrypoint_prod.sh. 
   
   FROM function wait_for_connection {
   echo BACKEND="${BACKEND:=${detected_backend}}"
   readonly BACKEND
   
   if [[ -z "${detected_port=}" ]]; then
       if [[ ${BACKEND} == "postgres"* ]]; then
           detected_port=5432
       elif [[ ${BACKEND} == "mysql"* ]]; then
           detected_port=3306
       elif [[ ${BACKEND} == "mssql"* ]]; then
           detected_port=1433
       elif [[ ${BACKEND} == "redis"* ]]; then
           detected_port=6379
       elif [[ ${BACKEND} == "amqp"* ]]; then
           detected_port=5672
       fi
   fi
   There is no handler for ### BACKEND=sqs
   
   Verified the ### BACKEND=sqs is comming from the broker_url = sqs://
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   _No response_
   
   ### Operating System
   
   Ubuntu container
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   _No response_
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [airflow] potiuk closed issue #22868: There is no handler for BACKEND=sqs in entrypoint_prod.sh function wait_for_connection

Posted by GitBox <gi...@apache.org>.
potiuk closed issue #22868: There is no handler for BACKEND=sqs in entrypoint_prod.sh function wait_for_connection 
URL: https://github.com/apache/airflow/issues/22868


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org