# Plotting Stops after Error (taurus-oct-2024)

**URL:** <https://forum.autonomys.xyz/t/plotting-stops-after-error-taurus-oct-2024/4520>\
**Category:** Support\
**Created:** [October 30, 2024, 5:18am UTC](https://forum.autonomys.xyz/t/plotting-stops-after-error-taurus-oct-2024/4520 "2024-10-30T05:18:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [October 30, 2024, 11:59pm UTC](https://forum.autonomys.xyz/t/plotting-stops-after-error-taurus-oct-2024/4520/6 "2024-10-30T23:59:47Z")

</div>

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:

```bash
docker run --rm -it --pid host --privileged --user root --entrypoint /bin/bash ghcr.io/autonomys/farmer:whatever-tag-you-used

```

In the container:

```bash
apt-get install --no-install-recommends gdb
gdb /subspace-farmer PID_OF_FARMER_PROCESS_ON_THE_HOST

```

Now in gdb type the following:

```auto
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.

---

_[View the full topic](https://forum.autonomys.xyz/t/plotting-stops-after-error-taurus-oct-2024/4520)._