Hello. I’m trying to get started with Dagster. I’v...
# announcements
d
Hello. I’m trying to get started with Dagster. I’ve worked through the tutorials and have it running in docker. I’m trying to get schedules to work. I have a schedule set and can see them in the UI turned on (and set to run every minute for testing) but the scheduled pipeline don’t seem to be running. I’m sure I’m missing something obvious
The only thing I have defined in my
dagster.yaml
is
Copy code
scheduler:
   module: dagster_cron.cron_scheduler
   class: SystemCronScheduler
s
Hey Dennis! If you run
dagster schedule logs {schedule_name}
you may find the error you’re running into
d
I’m not seeing that as an option for
schedule
. I’m on version 0.7.12 is this new to 0.7.14?
s
yeah, this was introduced in either 0.7.13 or 0.7.14 i believe
d
ah. I’ll update some things and circle back on this
thanks
s
would it be a difficult upgrade? i could walk you through how to manually get the logs if so
d
give me one sec
Ok. I updated and ran
dagster schedule start test_schedule
to start up my schedule Not seeing any logs in appear in the directory
a
did you see https://docs.dagster.io/docs/deploying/local cron isnt active by default in most Docker base images
could be the issue
d
Yeah I based my docker setup off that documentation page. If I followed all that do I need to make any additional changes?
a
no - missing that stuff was my guess
you could add something manually to
cron
to verify its working
d
Yeah. I’ll keep playing around with it. Just wanted to ensure I wasn’t missing a basic thing (needing to set something else in the
dagster.yaml
)
thanks for the help
a
you may want to add
postgres
run, event, and schedule storage that or use a volume mount so that
$DAGSTER_HOME
can persist between deploys
👍 1
s
@dhume any luck? If it’s still not running, some steps I would take are: - Check the cron tab to make sure your cron job is there using
crontab -l
- Add a test cron job to the cron tab (something like
echo "test" > text_cron.txt
to make sure cron is running
d
Circling back on this if you still have the time.
crontab -l
is showing the schedule set. When I look in the container and check the logs for the schedule I’m getting this error
Copy code
ModuleNotFoundError: No module named 'repos'
I saw someone else had a similar issue in a previous slack thread but I didn’t see their resolution
a
how is your
repository.yaml
set up?
my initial guess is that you are using
module: repos
and repos is only a valid “module” in that current working directory (ie not installed or otherwise on the python module loading path). Switching to
file: repos.py
may resolve the issue
d
Thanks. I think that did it