Okay, so something hangs on the farmer.
Now there are two things I’d like to request.
First to start farmer with RUST_LOG=info,subspace_farmer=trace, which will generate a lot more logs, but should also help with debugging (make sure Docker is configured to retain a couple GB of logs at least).
Second, it’d help to dump backtraces of threads with gdb when this happens.
Here is how I’d do it:
docker run --rm -it --pid host --privileged --user root --entrypoint /bin/bash ghcr.io/autonomys/farmer:whatever-tag-you-used
In the container:
apt-get install --no-install-recommends gdb
gdb /subspace-farmer PID_OF_FARMER_PROCESS_ON_THE_HOST
Now in gdb type the following:
set pagination off
thead apply all bt
And send me the whole output.
Then you can exit gdb and container.
This should hopefully provide a hint about what got stuck and where.
@Jim-Autonomys I’m not sure how to debug apps so easily on Windows, but enabling and collecting trace logs might help there as well.