https://dagster.io/ logo
#dagster-support
Title
# dagster-support
m

Mike Needham

01/11/2023, 9:35 PM
so trying to get the dagster-daemon to run. I have set the environment variable DAGSTER_HOME to my project home directory, but when I run dagster-daemon run i get and error that "Error: No arguments given and no [tool.dagster] block in pyproject.toml found."
d

daniel

01/11/2023, 9:38 PM
Hi Mike - what arguments (if any) are you passing in to dagit when you run it? Are you running dagster-daemon in that same folder as when you run dagit?
m

Mike Needham

01/11/2023, 9:49 PM
I figured it out. the dagster-daemon needed to be up one level when it ran and I had to add the [tool.dagster] to the pyproject.toml fiel
thanks
condagster 1
d

daniel

01/11/2023, 9:50 PM
no problem, i'll ping you when that
dagster dev
command that launches both of them for you in a single command is live
m

Mike Needham

01/11/2023, 9:50 PM
that would be awesome. thanks again
ok, so in dagit the daemon is running and I am working through the example at https://docs.dagster.io/guides/dagster/scheduling-assets
the job never seems to run
the daemon is running, the schedule appears to be active but nothing happens
FYI, this is step 1 of the example
a cron based schedule
d

daniel

01/11/2023, 10:14 PM
Would it be possible to share logs from the dagster-daemon output?
m

Mike Needham

01/11/2023, 10:21 PM
so I am seeing dagster.daemon.SchedulerDaemon - WARNING - Schedule update_job_schedule was started from a location test1.py that can no longer be found in the workspace. You can turn off this schedule in the Dagit UI from the Status tab
d

daniel

01/11/2023, 10:22 PM
are you running dagit and the daemon with the same command line arguments?
m

Mike Needham

01/11/2023, 10:22 PM
I am missing something obviously
i ran the daemon in the background using nohup dagster-daemon run &
d

daniel

01/11/2023, 10:22 PM
another thing the dagster dev command will fix
m

Mike Needham

01/11/2023, 10:22 PM
and then dagit -f test1.py
d

daniel

01/11/2023, 10:22 PM
You'll want to run them in the same folder with the same command-line arguments
so they look for your code in the same place
m

Mike Needham

01/11/2023, 10:23 PM
ok, will try that. seems a little disconnected
thanks
that worked. as a noob it seems disconnected that the daemon cannot figure out where the code is. just my 2 cents. just so I understand, if I just ran the dameon from the top of my project with no arguments except run, and dagit from the same folder would it work?
d

daniel

01/11/2023, 10:29 PM
yeah, they need to run with the same arguments and find the code in the same way
m

Mike Needham

01/11/2023, 10:31 PM
ok, that helps. thanks again for your help. the learning curve is killing me trying to get a POC to show my co-workers
d

daniel

01/11/2023, 10:32 PM
no problem - this is the exact situation / use case we are targeting this 'dagster dev' command at so hopefully this gets better very soon
m

Mike Needham

01/11/2023, 10:33 PM
that would be great, thanks again
d

daniel

01/19/2023, 9:30 PM
Hey @Mike Needham - just letting you know that that
dagster dev
command just shipped in 1.1.11 so it should be quite a bit easier to try out schedules and sensors locally now: https://docs.dagster.io/deployment/guides/running-locally
m

Mike Needham

01/19/2023, 10:43 PM
that's awesome. I will check it out. thanks for the update.
183 Views