Hi experts, Why does Dagster stop by itself please ? (Windows env) (...)

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Completed scheduled launch of run 988c79e8-5ab1-46f5-b8b5-9e3686e50fc2 for job_test1

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Completed scheduled launch of run c24d23ba-6dbb-429d-9297-ca5fc89aad52 for job_test2

[32m2023-09-05 16:55:02 +0200[0m - dagster.daemon.QueuedRunCoordinatorDaemon - [34mINFO[0m - Retrieved 5 queued runs, checking limits.

[32m2023-09-05 16:55:09 +0200[0m - dagster - [34mINFO[0m - Shutting down Dagster services...

[32m2023-09-05 16:55:09 +0200[0m - dagster - [34mINFO[0m - Dagster services shut down.

Tx for help,

hey @Sebastien - dagster shouldn’t be shutting down by itself. what is happening before the daemon shuts down? does anything error? are you typing anything on the keyboard? do you have a process running that uses up a lot of memory or cpu?

Hi, Here are the last lines of the log : (...)

[32m2023-09-05 16:54:35 +0200[0m - dagster.daemon.SensorDaemon - [34mINFO[0m - Not checking for any runs since no sensors have been started.

`[32m2023-09-05 165444 +0200[0m - dagster.daemon.AssetDaemon - [34mWARNING[0m - Auto materialize evaluations are not getting logged. Run

dagster instance migrate

to enable.`

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Checking for new runs for the following schedules: job_dec_integration_plan_mtz_schedule, job_extractloader_plan_duration_mtz_schedule, job_extractloader_plan_mtz_schedule, job_extractloader_statement_config_json_schedule, job_extractloader_statement_new_mtz_schedule, job_ftp_inout_mtz_schedule, job_ope_integration_plan_mtz_schedule, job_sentinel_is_alive_mtz_schedule, job_sentinel_jde920_expl_tld_lock_mtz_schedule, job_sentinel_pending_file_mtz_schedule, job_talend_executiontask_error_mtz_schedule

`[32m2023-09-05 165500 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Evaluating schedule

job_dec_integration_plan_mtz_schedule

at 2023-09-05 165500 +0200`

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - No new tick times to evaluate for job_extractloader_plan_duration_mtz_schedule

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - No new tick times to evaluate for job_extractloader_plan_mtz_schedule

`[32m2023-09-05 165500 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Evaluating schedule

job_extractloader_statement_config_json_schedule

at 2023-09-05 165500 +0200`

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - No new tick times to evaluate for job_extractloader_statement_new_mtz_schedule

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - No new tick times to evaluate for job_ftp_inout_mtz_schedule

`[32m2023-09-05 165500 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Evaluating schedule

job_ope_integration_plan_mtz_schedule

at 2023-09-05 165500 +0200`

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Completed scheduled launch of run 7e74d5ac-b2cf-4334-8537-2561c24041f1 for job_dec_integration_plan_mtz_schedule

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Completed scheduled launch of run 477622c6-630a-430c-ab36-ef01fb63c36a for job_extractloader_statement_config_json_schedule

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - No new tick times to evaluate for job_sentinel_is_alive_mtz_schedule

`[32m2023-09-05 165500 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Evaluating schedule

job_sentinel_jde920_expl_tld_lock_mtz_schedule

at 2023-09-05 165500 +0200`

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - No new tick times to evaluate for job_sentinel_pending_file_mtz_schedule

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Completed scheduled launch of run 2f7c4908-9ec3-44b9-88c1-f6f049cd139d for job_ope_integration_plan_mtz_schedule

`[32m2023-09-05 165500 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Evaluating schedule

job_talend_executiontask_error_mtz_schedule

at 2023-09-05 165500 +0200`

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Completed scheduled launch of run 988c79e8-5ab1-46f5-b8b5-9e3686e50fc2 for job_sentinel_jde920_expl_tld_lock_mtz_schedule

[32m2023-09-05 16:55:00 +0200[0m - dagster.daemon.SchedulerDaemon - [34mINFO[0m - Completed scheduled launch of run c24d23ba-6dbb-429d-9297-ca5fc89aad52 for job_talend_executiontask_error_mtz_schedule

[32m2023-09-05 16:55:02 +0200[0m - dagster.daemon.QueuedRunCoordinatorDaemon - [34mINFO[0m - Retrieved 5 queued runs, checking limits.

[32m2023-09-05 16:55:09 +0200[0m - dagster - [34mINFO[0m - Shutting down Dagster services...

[32m2023-09-05 16:55:09 +0200[0m - dagster - [34mINFO[0m - Dagster services shut down.

hmmm ok, i’m not too sure about this. I’ll bring it up to the team and find someone who knows more

putting up a fix so we print the cause of the shutdown https://github.com/dagster-io/dagster/pull/16333 based on the related code, one guess is that the daemon or webserver are causing OOMs