https://dagster.io/ logo
Join Slack
Powered by
I’m having a little trouble launching dagster-daem...
# ask-community
m
I’m having a little trouble launching dagster-daemon. It prints
Copy code
2021-05-27 13:55:14 - dagster-daemon - INFO - instance is configured with the following daemons: ['BackfillDaemon', 'SchedulerDaemon', 'SensorDaemon']
2021-05-27 13:55:14 - SensorDaemon - INFO - Not checking for any runs since no sensors have been started.
2021-05-27 13:55:14 - SchedulerDaemon - INFO - Not checking for any runs since no schedules have been started.
2021-05-27 13:55:14 - BackfillDaemon - INFO - No backfill jobs requested.
and Dagit says no daemons are running. I have two sensors and a schedule that show fine in the UI and are turned on.
👍 1
d
hi Martim - are the daemon process and dagit using the same storage? Mind sharing your dagster.yaml file?
a
are the dagster instances the same in both places? 
dagster instance info
m
Copy code
run_storage:
  module: dagster.core.storage.runs
  class: SqliteRunStorage
  config:
    base_dir: /mnt/y/projetos/getty/dagster/storage/run

event_log_storage:
  module: dagster.core.storage.event_log
  class: SqliteEventLogStorage
  config:
    base_dir : /mnt/y/projetos/getty/dagster/storage/event_log

scheduler:
  module: dagster.core.scheduler
  class: DagsterDaemonScheduler

schedule_storage:
  module: dagster.core.storage.schedules
  class: SqliteScheduleStorage
  config:
    base_dir : /mnt/y/projetos/getty/dagster/storage/schedule

run_launcher:
  module: dagster.core.launcher
  class: DefaultRunLauncher
Copy code
$ dagster instance info
$DAGSTER_HOME: /mnt/y/projetos/getty/dagster

local_artifact_storage:
  module: dagster.core.storage.root
  class: LocalArtifactStorage
  config:
    base_dir: /mnt/y/projetos/getty/dagster
run_storage:
  module: dagster.core.storage.runs
  class: SqliteRunStorage
  config:
    base_dir: /mnt/y/projetos/getty/dagster/storage/run
event_log_storage:
  module: dagster.core.storage.event_log
  class: SqliteEventLogStorage
  config:
    base_dir: /mnt/y/projetos/getty/dagster/storage/event_log
compute_logs:
  module: dagster.core.storage.local_compute_log_manager
  class: LocalComputeLogManager
  config:
    base_dir: /mnt/y/projetos/getty/dagster/storage
schedule_storage:
  module: dagster.core.storage.schedules
  class: SqliteScheduleStorage
  config:
    base_dir: /mnt/y/projetos/getty/dagster/storage/schedule
scheduler:
  module: dagster.core.scheduler
  class: DagsterDaemonScheduler
  config: {}
run_coordinator:
  module: dagster.core.run_coordinator
  class: DefaultRunCoordinator
  config: {}
run_launcher:
  module: dagster.core.launcher
  class: DefaultRunLauncher
  config: {}
telemetry: NoneType
@daniel I’m running both via WSL
d
Do both the daemon and dagit have access to the same filesystem to load the Sqlite database? If not you may want to switch to a Postgres or MySQL storage instead
m
As far as I know they should… Sorry, I’m a total SQL noob. How are Postgres and MySQL different from SQLite?
a
sqlite is powered by files on the local filesystem read in to the process postgres and mysql are database servers communicated with over the network
👍 1
m
I’ll try changing that, thanks. My 
dagster_home
is located in a directory on a network share drive, I thought maybe Dagit and Dagster didn’t have access to it, but I tried setting a local folder as `dagster_home`and got the same behaviour…
What would be the minimal setup that allows me to use sensors and schedules? I don’t need any fancy logging in my case
Ok, I just realized the instances are not the same in both places. Configuration in Dagit points to 
/tmp/
👍 1
I think my problem was declaring DAGSTER_HOME via export, so I had to do it twice (once for each bash session) so both processes look at the same place. Including DAGSTER_HOME in the .bashrc file should do the trick, right?
a
yep
3 Views
Open in Slack
PreviousNext
Powered by