Closed Siva-Taicho77 closed 4 months ago
I am using 8.8.0 and see a similar issue:
2023-12-11T02:24:32.625+0000] {cli_action_loggers.py:135} WARNING - Failed to log action (psycopg2.OperationalError) connection to server at "airflow-pgbouncer.airflow-cluster.svc.cluster.local" (180.64.126.241), port 6432 failed: SSL SYSCALL error: EOF detected (Background on this error at: https://sqlalche.me/e/14/e3q8) /home/airflow/.local/lib/python3.9/site-packages/airflow/utils/db.py:1738 RemovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings. Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "airflow-pgbouncer.airflow-cluster.svc.cluster.local" (180.64.126.241), port 6432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections?
@anirao Is there any way to get in touch with the experts here?
I know it's been a while since this issue was raised, but the issue the original poster @Siva-Taicho77 was having was just that they had not created a database called airflow_cluster1
in their RDS instance.
For the other people like @anirao who are getting sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "airflow-pgbouncer.airflow-cluster.svc.cluster.local" (180.64.126.241), port 6432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections?
, you should check the logs for the pgbouncer
pod to see if it's running, and can see your RDS instance.
This issue can be closed, I was able to solve it.
Checks
User-Community Airflow Helm Chart
.Chart Version
8.8.0
Kubernetes Version
Helm Version
Description
I am trying to setup an airflow application which has been configured to use PostgreSQL RDS for storing metadata. Both the EKS cluster and RDS share the same VPC, the worker node can communicate with RDS. In pod airflow-migrations init contianer check-db is failing (Error logs has been shared in the log section,). Can anyone please let me know why is it trying to reach out to airflow-cluster-pgbouncer.airflow-cluster.svc.cluster.local" (192.168.115.94) instead of the RDS cluster?
Relevant Logs
Custom Helm Values