sstamatiadis-dlt commented on issue #42136: URL: https://github.com/apache/airflow/issues/42136#issuecomment-3799136118
Hello, is there any working fix yet? I am using `Helm chart version 1.18.0 with Airflow 3.0.2` on AWS EKS after an update from `Helm chart version 1.15.0 with Airflow 2.9.3`. I cannot run DAGs because I get this error. I have tried above suggestions without any success. ``` Log message source details: sources=["Could not read served logs: Invalid URL 'http://:8793/log/dag_id=demo_DAG/run_id=scheduled__2026-01-26T00:00:00+00:00/task_id=meteo-data_fetching_in_airflow/attempt=1.log': No host supplied"] ``` If I exec into the airflow-worker pod and cat the logs, the run file exists but it is empty. My 3.0.2 config is as below: ``` [core] auth_manager = airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager colored_console_log = False dags_folder = /opt/airflow/dags execution_api_server_url = http://airflow-xxxxxxxxxxx-api-server:8080/execution/ executor = CeleryExecutor load_examples = False remote_logging = False [webserver] enable_proxy_fix = True rbac = True [logging] colored_console_log = False remote_logging = False [celery] flower_url_prefix = worker_concurrency = 16 [celery_kubernetes_executor] kubernetes_queue = kubernetes [elasticsearch] json_format = True log_id_template = {dag_id}_{task_id}_{execution_date}_{try_number} [elasticsearch_configs] max_retries = 3 retry_timeout = True timeout = 30 [fab] enable_proxy_fix = True [kerberos] ccache = /var/kerberos-ccache/cache keytab = /etc/airflow.keytab principal = [email protected] reinit_frequency = 3600 [kubernetes] airflow_configmap = airflow-xxxxxxxxxxx-config airflow_local_settings_configmap = airflow-xxxxxxxxxxx-config multi_namespace_mode = False namespace = admins pod_template_file = /opt/airflow/pod_templates/pod_template_file.yaml worker_container_repository = apache/airflow worker_container_tag = 3.0.2 [kubernetes_executor] multi_namespace_mode = False namespace = admins pod_template_file = /opt/airflow/pod_templates/pod_template_file.yaml worker_container_repository = apache/airflow worker_container_tag = 3.0.2 [metrics] statsd_host = airflow-xxxxxxxxxxx-statsd statsd_on = False statsd_port = 9125 statsd_prefix = airflow [scheduler] run_duration = 41460 standalone_dag_processor = True statsd_host = airflow-xxxxxxxxxxx-statsd statsd_on = False statsd_port = 9125 statsd_prefix = airflow ``` The older version was 2.9.3: ``` [celery] flower_url_prefix = worker_concurrency = 16 [celery_kubernetes_executor] kubernetes_queue = kubernetes [core] colored_console_log = False dags_folder = /opt/airflow/dags executor = CeleryExecutor load_examples = False remote_logging = False [elasticsearch] json_format = True log_id_template = {dag_id}_{task_id}_{execution_date}_{try_number} [elasticsearch_configs] max_retries = 3 retry_timeout = True timeout = 30 [kerberos] ccache = /var/kerberos-ccache/cache keytab = /etc/airflow.keytab principal = [email protected] reinit_frequency = 3600 [kubernetes] airflow_configmap = airflow-xxxxxxxxxxx-config airflow_local_settings_configmap = airflow-xxxxxxxxxxx-config multi_namespace_mode = False namespace = admins pod_template_file = /opt/airflow/pod_templates/pod_template_file.yaml worker_container_repository = apache/airflow worker_container_tag = 2.9.3 [kubernetes_executor] multi_namespace_mode = False namespace = admins pod_template_file = /opt/airflow/pod_templates/pod_template_file.yaml worker_container_repository = apache/airflow worker_container_tag = 2.9.3 [logging] colored_console_log = False remote_logging = False [metrics] statsd_host = airflow-xxxxxxxxxxx-statsd statsd_on = False statsd_port = 9125 statsd_prefix = airflow [scheduler] run_duration = 41460 standalone_dag_processor = False statsd_host = airflow-xxxxxxxxxxx-statsd statsd_on = False statsd_port = 9125 statsd_prefix = airflow [triggerer] default_capacity = 1000 [webserver] enable_proxy_fix = True rbac = True ``` - Should I be trying a newer version of the Airflow image? I read that the issue is more than just a misconfiguration logic. - The `hostname_callable = airflow.utils.net.get_host_ip_address` did not fix my issue - Other `base_url` or similar configuration seem to have not alleviate the problem -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
