💬 pinheadmz commented on issue "bitcoind debug log file is growing without limit":
(https://github.com/bitcoin/bitcoin/issues/31795#issuecomment-2634696088)
The log file gets truncated when you restart bitcoind. There have been proposals for pruning the log but I think the recommendation is just to use a manager on your own system:

https://github.com/bitcoin/bitcoin/pull/24950#issuecomment-1111900473

https://github.com/bitcoin/bitcoin/pull/22350#issuecomment-899539876

💬 Sjors commented on pull request "Add waitNext() to BlockTemplate interface":
(https://github.com/bitcoin/bitcoin/pull/31283#discussion_r1941669280)
I think #31785 is a more thorough solution that avoids having to deal with this edge case all over the place.

💬 embetrix commented on issue "bitcoind loglevel=info too noisy":
(https://github.com/bitcoin/bitcoin/issues/31796#issuecomment-2634704979)
the problem is that I use a raspberrypi/sdcard over tor proxy which take a lot of time to download the initial blockchain, if there are other application on my system which crashes or kernel problem, I cannot see it since bitcoind logs are all over the place.

💬 pinheadmz commented on issue "bitcoind loglevel=info too noisy":
(https://github.com/bitcoin/bitcoin/issues/31796#issuecomment-2634710807)
I have a lot of experience running bitcoind on raspberry pi and I strongly encourage you to use the SD card as little as possible: the bitcoin data directory should be on an external SSD.

> other application on my system

How does bitcoin's debug log interfere with monitoring or logging any other application?

💬 embetrix commented on issue "bitcoind debug log file is growing without limit":
(https://github.com/bitcoin/bitcoin/issues/31795#issuecomment-2634715222)
I'm using a raspberrypi with sdcard (1TB), I want to let my full node running and do not plan to restart my bitcoind everyday, this is unnecessary to use humongous amout of RAM or SDCard for the logs.

I disabled now the debug by setting

`nodebuglogfile=1 `

But I think that log rotation make sense.

💬 pinheadmz commented on issue "bitcoind debug log file is growing without limit":
(https://github.com/bitcoin/bitcoin/issues/31795#issuecomment-2634717766)
Please see the linked comments above. I think your issue is a duplicate and has been addressed many times already

💬 embetrix commented on issue "bitcoind loglevel=info too noisy":
(https://github.com/bitcoin/bitcoin/issues/31796#issuecomment-2634717943)
the `journald` can be configured to rotate and prune old logs, in this case I see only `bitcoind` logs

💬 embetrix commented on issue "bitcoind debug log file is growing without limit":
(https://github.com/bitcoin/bitcoin/issues/31795#issuecomment-2634724360)
I saw the MR but they were not merged

💬 pinheadmz commented on issue "bitcoind loglevel=info too noisy":
(https://github.com/bitcoin/bitcoin/issues/31796#issuecomment-2634729108)
Ok well, `UpdateTip` means a block is being added to the consensus block chain, there's gonna be about a million of them, and its arguably the entire purpose of running a full node. I think you should reconsider your monitoring.

💬 pinheadmz commented on issue "bitcoind debug log file is growing without limit":
(https://github.com/bitcoin/bitcoin/issues/31795#issuecomment-2634732936)
but did you read the **comments** -- the reason bitcoin core doesn't manage its logs how you want

💬 embetrix commented on issue "bitcoind loglevel=info too noisy":
(https://github.com/bitcoin/bitcoin/issues/31796#issuecomment-2634732990)
probably the noisy logs from https://github.com/bitcoin/bitcoin/issues/31796 are writing too much data and wearing out the SDCard quickly if configured to an sd partition instead of RAM.

💬 pinheadmz commented on issue "bitcoind loglevel=info too noisy":
(https://github.com/bitcoin/bitcoin/issues/31796#issuecomment-2634737121)
> wearing out the SDCard

Do not write bitcoin's data directory to an SD card, you're gonna have a bad time

💬 embetrix commented on issue "bitcoind debug log file is growing without limit":
(https://github.com/bitcoin/bitcoin/issues/31795#issuecomment-2634739067)
it's not how I want, it just make a sens to implement that if using a system with restricted ressources and have in mind that not all bitcoin nodes are powerful PCs.

💬 embetrix commented on issue "bitcoind loglevel=info too noisy":
(https://github.com/bitcoin/bitcoin/issues/31796#issuecomment-2634744533)
I have an industrial grade SDCard, I will let you know how it went ;-)

💬 ismaelsadeeq commented on pull request "mining: bugfix: Fix duplicate coinbase tx weight reservation":
(https://github.com/bitcoin/bitcoin/pull/31384#discussion_r1941748759)
Done!

💬 ismaelsadeeq commented on pull request "mining: bugfix: Fix duplicate coinbase tx weight reservation":
(https://github.com/bitcoin/bitcoin/pull/31384#discussion_r1941751254)
Fixed!

💬 hebasto commented on pull request "ci: build multiprocess on most jobs":
(https://github.com/bitcoin/bitcoin/pull/30975#issuecomment-2634831978)
> ... then found another issue:
>
> ```
> /home/runner/work/_temp/src/ipc/libmultiprocess/src/mp/gen.cpp:633:26: error: comparison of integers of different signs: 'size_t' (aka 'unsigned long') and 'int' [-Werror,-Wsign-compare]
> 633 | for (size_t i = 4; i < argc; ++i) {
> | ~ ^ ~~~~
> 1 error generated.
> ```

Fixed in https://github.com/chaincodelabs/libmultiprocess/pull/151.

💬 ismaelsadeeq commented on pull request "mining: bugfix: Fix duplicate coinbase tx weight reservation":
(https://github.com/bitcoin/bitcoin/pull/31384#issuecomment-2634860548)
Force-pushed from 6709e185b93d97b9191597acfecb25c33ab43a0a to 386eecff5f14d508688e6e7374b67cb54aaa7249.

See [6709e185b9....386eecff5f14](https://github.com/bitcoin/bitcoin/compare/6709e185b93d97b9191597acfecb25c33ab43a0a..386eecff5f14d508688e6e7374b67cb54aaa7249)

- The changes in this push ensure that the consensus `MAX_BLOCK_WEIGHT` is used in block assembler instead of a policy constant `DEFAULT_BLOCK_MAX_WEIGHT`.
- The policy value is only used when the user has not provided a cus
...

💬 willcl-ark commented on pull request "Double check all block rules in `ConnectBlock`, not only `CheckBlock`":
(https://github.com/bitcoin/bitcoin/pull/31792#issuecomment-2634905893)
I seem to have a problem running IBD with this change @ dd2714ed13eea3591162dbade8132ff517ca5509, which I have not investigated yet:

<details>
<summary>tail debug.log</summary>

```log
<snip>
2025-02-04T19:38:24Z init message: Verifying blocks…
2025-02-04T19:38:24Z Block index and chainstate loaded
2025-02-04T19:38:24Z Setting NODE_NETWORK on non-prune mode
2025-02-04T19:38:24Z initload thread start
2025-02-04T19:38:24Z [bench] - Load block from disk: 0.05ms
2025-02-04T19:38:24Z [
...

💬 ryanofsky commented on issue "test: 32-bit Clang `ipc_test` failure at `-O0`":
(https://github.com/bitcoin/bitcoin/issues/31772#issuecomment-2634917217)
I thought I tracked down the problem, and some change I made to the test caused it to pass, but rerunning the the fix in a new container, it no longer works, so I have to go back.

Here were notes I was about to post about potential problem & fix. In any case I suspect problem would be avoided if we just consistently used gcc or clang for this build and didn't try to mix them.

---

Test failure seems to be caused by the container using incompatible ABI versions for the depends build and the mai
...