You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "HemanthKumar8124 (via GitHub)" <gi...@apache.org> on 2023/04/25 10:52:56 UTC

[GitHub] [airflow] HemanthKumar8124 commented on issue #21605: KubernetesPodOperator Fails on empty log line

HemanthKumar8124 commented on issue #21605:
URL: https://github.com/apache/airflow/issues/21605#issuecomment-1521584387

   Hi Team,
   
   Even with Airflow MWAA 2.4.3 version with Kubernetes POD Operator task, we are seeing the below issue in Airflow logs.
   
   kubernetes version - 1.24
   
   {{pod_manager.py:410}} ERROR - Error parsing timestamp (no timestamp in message ''). Will continue execution but won't update timestamp
   {{logging_mixin.py:137}} WARNING - /usr/local/airflow/.local/lib/python3.10/site-packages/watchtower/__init__.py:349 WatchtowerWarning: Received empty message. Empty messages cannot be sent to CloudWatch Logs
   {{logging_mixin.py:137}} WARNING - Traceback (most recent call last):
   {{logging_mixin.py:137}} WARNING -   File "/usr/local/airflow/config/cloudwatch_logging.py", line 161, in emit
       self.sniff_errors(record)
   {{logging_mixin.py:137}} WARNING -   File "/usr/local/airflow/config/cloudwatch_logging.py", line 211, in sniff_errors
       if pattern.search(record.message):
   {{logging_mixin.py:137}} WARNING - AttributeError: 'LogRecord' object has no attribute 'message'
   
   I don't see any issue with POD logs when I manually checked using kubectl client. Each line contains timestamp in it. But the above warning message appears in Airflow logs.
   
   
   


-- 
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