<p><code>bitcoind -printtoconsole -debug</code></p>

<p>This will output an unreasonable amount of information and break your terminal, and not particularly help you with your sovereignty. </p>

CC BY-SA 4.0
2020-02-29T23:10:32.850Z
Initially got  "Error: Cannot obtain a lock on data directory /node/BTC. Bitcoin Core is probably already running."  After issuing bitcoin-cli stop, it worked as expected.  Very informative.
MountainMan
CC BY-SA 4.0
2020-02-29T21:20:55.640Z
2020-02-29T21:20:55.640Z
Claris
<p>The debug.log files is updated regularly details activity of bitcoind and bitcoin-qt. The file can be found in $HOME/.bitcoin on Linux, and in %USERPROFILE%\AppData\Roaming\Bitcoin on Windows.</p>

<p>A "tail -f debug.log" will give you live info. It's not the most user-friendly.</p>

<p>I modified bitcoin core tn to give more useful information in debug.log, and more human readable, with more granular options to enable or disable certain debugging. It can be found at <a href="https://github.com/rebroad/bitcoin/" rel="nofollow noreferrer">https://github.com/rebroad/bitcoin/</a></p>

<p>It's not been updated since 0.13 though. I'm curious to know what specific information you'd like to see.</p>

CC BY-SA 4.0
2020-03-02T23:49:38.283Z
Hi, yes, used tail -f -n 200 debug.log a lot while the IBD was in progress.  Fascinating.  But once the node was up to date and properly indexed, that file activity drops to just the occasional activity of peers dropping off the network or new peers being added and of course every 10 minutes or so some info about a new block.  I specifically wanted to see as much as possible of the ongoing work the node performs for the network. -printtoconsole -debug got me a long ways towards that.  I see that all the settings to bitcoind can be used to tailor what gets included.  Looked at your repo.  Nice.
MountainMan
CC BY-SA 4.0
2020-03-01T09:45:44.783Z
2020-03-01T09:45:44.783Z
Rebroad
<p>Having examined the output of</p>

<pre><code>bitcoind -h
</code></pre>

<p>and searched through all the bitcoin-cli rpc items listed here</p>

<pre><code>https://bitcoincore.org/en/doc/0.19.0/rpc/
</code></pre>

<p>I did not find anything which produces a live stream to stdout of all the tasks my full node is running/performing.  What is required to make all that visible?</p>

<p>One is led to understand that the main benefit of running one's own full node is to be able to independently confirm transactions and that is all fine, but another important effect is supposedly the continual assistance the node provides to the network, serving historical blocks and so forth.  That traffic is what I would like to see.</p>

<bitcoin-core><full-node>
How can I view in my shell, live, ALL activity my bitcoind is generating?
MountainMan
# How can I view in my shell, live, ALL activity my bitcoind is generating?

(Asked by: username_0 on 2020-02-29)

Having examined the output of

```
bitcoind -h

```

and searched through all the bitcoin-cli rpc items listed here

```
https://bitcoincore.org/en/doc/0.19.0/rpc/

```

I did not find anything which produces a live stream to stdout of all the tasks my full node is running/performing. What is required to make all that visible?

One is led to understand that the main benefit of running one's own full node is to be able to independently confirm transactions and that is all fine, but another important effect is supposedly the continual assistance the node provides to the network, serving historical blocks and so forth. That traffic is what I would like to see.

**Tags:** bitcoin-core, full-node


---

## 2 answers

### Answer by username_1 on 2020-02-29. Score: 2

`bitcoind -printtoconsole -debug`

This will output an unreasonable amount of information and break your terminal, and not particularly help you with your sovereignty.

> **Comments:**
> **username_0**: Initially got  "Error: Cannot obtain a lock on data directory /node/BTC. Bitcoin Core is probably already running."  After issuing bitcoin-cli stop, it worked as expected.  Very informative.  

---

### Answer by username_2 on 2020-03-01. Score: 0

The debug.log files is updated regularly details activity of bitcoind and bitcoin-qt. The file can be found in $HOME/.bitcoin on Linux, and in %USERPROFILE%\AppData\Roaming\Bitcoin on Windows.

A "tail -f debug.log" will give you live info. It's not the most user-friendly.

I modified bitcoin core tn to give more useful information in debug.log, and more human readable, with more granular options to enable or disable certain debugging. It can be found at <https://github.com/username_2/bitcoin/>

It's not been updated since 0.13 though. I'm curious to know what specific information you'd like to see.

> **Comments:**
> **username_0**: Hi, yes, used tail -f -n 200 debug.log a lot while the IBD was in progress.  Fascinating.  But once the node was up to date and properly indexed, that file activity drops to just the occasional activity of peers dropping off the network or new peers being added and of course every 10 minutes or so some info about a new block.  I specifically wanted to see as much as possible of the ongoing work the node performs for the network. -printtoconsole -debug got me a long ways towards that.  I see that all the settings to bitcoind can be used to tailor what gets included.  Looked at your repo.  Nice.  

---

