Operation name: InstanceHealthQuery Message: too many retries for DB connection Path: ["instance","daemonHealth"] Locations: [{"line":52,"column":3}] Stack Trace: File "/usr/local/lib/python3.7/site-packages/graphql/execution/executor.py", line 452, in resolve_or_error return executor.execute(resolve_fn, source, info, **args) File "/usr/local/lib/python3.7/site-packages/graphql/execution/executors/sync.py", line 16, in execute return fn(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/dagster_graphql/schema/instance.py", line 135, in resolve_daemonHealth return GrapheneDaemonHealth(instance=self._instance) File "/usr/local/lib/python3.7/site-packages/dagster_graphql/schema/instance.py", line 78, in init instance, DaemonType.SCHEDULER File "/usr/local/lib/python3.7/site-packages/dagster/daemon/controller.py", line 236, in get_daemon_status heartbeats = instance.get_daemon_heartbeats() File "/usr/local/lib/python3.7/site-packages/dagster/core/instance/__init__.py", line 1418, in get_daemon_heartbeats return self._run_storage.get_daemon_heartbeats() File "/usr/local/lib/python3.7/site-packages/dagster/core/storage/runs/sql_run_storage.py", line 642, in get_daemon_heartbeats with self.connect() as conn: File "/usr/local/lib/python3.7/contextlib.py", line 112, in enter return next(self.gen) File "/usr/local/lib/python3.7/site-packages/dagster_postgres/utils.py", line 139, in create_pg_connection conn = retry_pg_connection_fn(engine.connect) File "/usr/local/lib/python3.7/site-packages/dagster_postgres/utils.py", line 112, in retry_pg_connection_fn raise DagsterPostgresException("too many retries for DB connection") from exc

Hi Cesar - this looks like dagit is having trouble connecting to your Postgres storage - first thing I’d check is if your DB is still up and running

Thanks! maybe fails by not enought free space on disk. How to clean the logs?

Which logs are you hoping to clear out?

From postgre. Would be interesting to clean it.

running "dagster run wipe" in the command line will clear out all the runs and event logs from the system - you can also run "dagster run delete <RUN_ID>" to delete individual runs. Would that be sufficient for what you're looking for here?

¡yes! thx 😉