Get Hands-on with Amazon EKS - Workshop Event Series

Whether you're taking your first steps with Kubernetes or you're an experienced practitioner looking to sharpen your skills, our Amazon EKS workshop series delivers practical, real-world experience that moves you forward. Learn directly from AWS solutions architects and EKS specialists through hands-on sessions designed to build your confidence with Kubernetes. Register now and start building with Amazon EKS!

AWS MWAA - Message - Need fix

Need the fix for below message, even changed instance size. So that it reset. The scheduler does not appear to be running. Last heartbeat was received 19 hours ago.

The DAGs list may not update, and new tasks will not be scheduled.

Topics: Application Integration
Tags: Amazon Managed Workflows for Apache Airflow (MWAA)
Language: English

SumitJaiswal

asked 4 years ago678 views

1 Answer

Newest
Most votes
Most comments

Are these answers helpful? Upvote the correct answer to help the community benefit from your knowledge.

I recommend taking the two steps outlined in the support documentation: https://docs.aws.amazon.com/mwaa/latest/userguide/t-apache-airflow-202.html#error-scheduler-202

Confirm the VPC Security Group allows inbound access to port 5432.
Confirm that your DAGs, plugins, and requireemnts are working correctly by reviewing CloudWatch Logs.

Curtis_D

answered 3 years ago

Relevant content

The scheduler does not appear to be running
rePost-User-0168726
asked 4 years ago
MWAA Heartbeat failure
AWDevOps
asked 3 years ago
AWS instance scheduler for maintenance windows: does (endtime) need to be after (begintime) to work? currently just stopping and not starting
mrhyde
asked 2 years ago
AWS MWAA: DAG didn't start according to schedule, but run well if to start it manually
Konstantin
asked 7 months ago
How do I resolve common issues with my scheduler in Amazon MWAA?
AWS OFFICIALUpdated 2 years ago
How do I resolve SIGTERM and SIGKILL errors in my Amazon MWAA environment?
AWS OFFICIALUpdated 7 months ago
How do I fix a compute environment that's not valid in AWS Batch?
AWS OFFICIALUpdated 7 months ago
How do I troubleshoot the "Was the task killed externally" error in Amazon MWAA?
AWS OFFICIALUpdated 9 months ago
Handling large messages in Amazon Managed Streaming for Apache Kafka (MSK)
EXPERT
Masudur Rahaman Sayem
published a year ago
"The provided number does not exist or does not belong to the account." error when trying to send messages via SNS or Pinpoint even though the required origination identity is acquired in the account.
SUPPORT ENGINEER
rajaws
published a year ago

AWS MWAA - Message - Need fix

Add your answer

Relevant content