Hey folks, I have a question re. dagster-daemon. K...
# ask-community
m
Hey folks, I have a question re. dagster-daemon. Kindly redirect me to the relevant channel. To share with you a short context, we are running dagster pipelines (using python) on EC2 instance and have scheduled a couple of jobs every 2 hrs. Now the issue is that the jobs are not getting triggered as expected. Does anyone know what could be the root causes? For further clarification, please feel free to connect with me. P.S. As per the official documentation, “dagster-daemon” is responsible for the scheduler, backfill and sensors and we have “dagster-daemon” running on the EC2 instance. Thanks
🤖 1
d
Hi Mayank - there's a set of troubleshooting steps here for schedules not running: https://docs.dagster.io/concepts/partitions-schedules-sensors/schedules#troubleshooting - can you try these and let us know if they help? If they don't, more information about what exactly the symptoms are that you're seeing and what you were able to rule out by following those steps would be helpful
That sounds to me like your dagit and dagster-daemon aren't using the same DAGSTER_HOME - did you set that environment variable? There are some examples of how to run dagit and the daemon here: https://docs.dagster.io/deployment/guides/service#running-dagster-as-a-service
highfive 1
thank you box 1
m
Hey @daniel, thanks for that pointer. Somehow my
DAGSTER_HOME
variable got reset and I was not aware of it.
Closing this issue.
Copy code
The solution of the problem was the  DAGSTER_HOME variable was not same because of which Daemons were not running and the reason schedule jobs were not getting triggered.
cc @Darshan Bhagat