Stuck mutex: any idea what happened?

1

Any idea what happened here? Last night Brewblox suddenly stopped cooling. From the UI, it looks like the mutex got stuck 401.54 seconds (no longer counting down). Power cycling the Spark released the mutex and put the fridge on again.

Ferment Graph
Ferment Graph3000×1500 247 KB

Screenshot_2020-04-30_18-28-43
Screenshot_2020-04-30_18-28-43966×243 20.1 KB

Logfile here: https://termbin.com/z1ue

It doesn’t look like the problem is with the PID’s (they are driving the PWM, but the actuator gets blocked), but in case I missed something, I’ve attached the PID graphs and the blocks as well.

I know I’m a couple of weeks behind on updates, but I don’t’ like to update while there’s a beer fermenting :grinning:

Rob

brewblox-blocks-spark-one.json (5.7 KB)

Ferment Cool PID
Ferment Cool PID3000×1500 401 KB
Ferment Heat PID
Ferment Heat PID3000×1500 404 KB

2

The only cause of mutex lockups I have seen is memory being full.

The latest release displays memory use on the display, but you’re not running that.

If you only have one process running, if is unlikely.
I’ll check your blocks later.

I recommend updating though!

3

Thanks Elco. I’ve updated in the meantime (I really should get a Pi4 or something x86-based because docker-compose takes a really long time on mine).

I’m seeing 2 figures in the top right of the screen now: 76% and 78%. Nothing complicated: just fermentation (3 sensors, 2 actuators).

FYI: the spark had been running for about 26 days (2 batches) when the failure occurred.