Workers randomly die for some reason

> [!NOTE]
> Migrated from [augurlabs/augur#3612](https://github.com/augurlabs/augur/issues/3612)
> Originally opened by `@MoralCode` on 2026-01-19

---

This is mostly an issue just to document some weird behavior ive seen so i can reference it in a PR.

Main symptoms: all workers show "offline" in flower. logs for rabbit show really unhelpful (but scary) red text. lots of it looks kidna like this, with lots of indents, almost like its dumping its internal state or something (the weird unicode you see at the beginning and end are the ASCII color codes)

Stack Trace

```
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> reason: {noproc,{gen_server,call,[mnesia_sync,sync,infinity]}}
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> offender: [{pid,<0.533.0>},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> {id,rabbit_amqqueue},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> {mfargs,
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> {rabbit_prequeue,start_link,
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> [{amqqueue,
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> {resource,<<"augur_vhost">>,queue,<<"celery">>},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> true,false,none,[],<0.533.0>,[],[],[],undefined,
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> undefined,[],[],stopped,0,[],<<"augur_vhost">>,
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> #{user => <<"augur">>},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> rabbit_classic_queue,#{}},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> recovery,<0.531.0>]}},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> {restart_type,transient},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> {significant,true},
rabbitmq-1 | 2026-01-16 03:30:43.238430+00:00 [error] <0.532.0> {shutdown,600000},
```

I suspect (after seeing this a couple times) this may be either some kind of startup race condition, or some kind of issue tied to running out of disk space on the root disk (which i remember hearing from @sgoggins recently that some part of augur does not like very much/is least able to handle it).