bitcoind loglevel=info too noisy #31796

issue embetrix openend this issue on February 4, 2025
  1. embetrix commented at 5:27 pm on February 4, 2025: none

    Is there an existing issue for this?

    • I have searched the existing issues

    Current behaviour

    when setting bitcoind log level in bitcoin.conf:

    loglevel=info

    the journactl logs are too noisy:

    this of course make the journal full and remove all other applications logs after a while.

    Expected behaviour

    loglevel=info should avoid printing out UpdateTip

    Steps to reproduce

    NA

    Relevant log output

     0Feb 04 17:23:07 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:07Z UpdateTip: new best=000000000000000001b96471b919f7f13656152099b9484ddadc446b5c067620 height=464311 version=0x00000004 log2_work=86.362716 tx=217963485 date='2017-05-01T06:54:32Z' progress=0.187834 cache=156.7MiB(1269783txo)
     1Feb 04 17:23:07 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:07Z UpdateTip: new best=00000000dc68b1790126db7f6de33939666 height=464317 version=0x20000000 log2_work=86.362911 tx=217975729 date='20100000000000f87e812bfe3ec23a7813ca5078aa41eb9224d8f8986dbb height=464312 version=0x20000000 log2_work=86.362749 tx=217965391 date='2017-05-01T07:02:49Z' progress=0.187836 cache=156.9MiB(1271998txo)
     2Feb 04 17:23:07 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:07Z UpdateTip: new best=000000000000000000dc676018a865d57cf5600b5705535f0b3271cf6b6719f0 height=464313 version=0x20000002 log2_work=86.362781 tx=217966965 date='2017-05-01T07:07:17Z' progress=0.187837 cache=157.2MiB(1273461txo)
     3Feb 04 17:23:08 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:08Z UpdateTip: new best=000000000000000000e6122e7927af3d7f6d9c7ef8c12915cd35c7f43f4c54e1 height=464314 version=0x20000002 log2_work=86.362814 tx=217969664 date='2017-05-01T07:22:19Z' progress=0.187840 cache=157.4MiB(1276100txo)
     4Feb 04 17:23:08 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:08Z UpdateTip: new best=0000000000000000019b6f3038196350d79f8611f7613c1153af78cabf0e34c4 height=464315 version=0x20000000 log2_work=86.362846 tx=217971903 date='2017-05-01T07:33:39Z' progress=0.187842 cache=157.7MiB(1278565txo)
     5Feb 04 17:23:08 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:08Z UpdateTip: new best=000000000000000000afb346eeff2de5a7fb634503a4bcba0002132df4495904 height=464316 version=0x00000004 log2_work=86.362879 tx=217973844 date='2017-05-01T07:36:23Z' progress=0.187843 cache=157.9MiB(1280309txo)
     6Feb 04 17:23:08 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:08Z UpdateTip: new best=000000000000000001f3028d356fb5976ffe7-05-01T07:45:38Z' progress=0.187845 cache=158.2MiB(1283484txo)
     7Feb 04 17:23:08 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:08Z UpdateTip: new best=000000000000000000ca968c83b97b7ad4eeb09a2ea6456ef2b19186a19292e9 height=464318 version=0x20000000 log2_work=86.362944 tx=217977017 date='2017-05-01T07:51:27Z' progress=0.187846 cache=158.7MiB(1286411txo)
     8Feb 04 17:23:08 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:08Z UpdateTip: new best=00000000000000000203c41063378c2daeceadbd15dcd7c54337bba429da2085 height=464319 version=0x20000000 log2_work=86.362976 tx=217977530 date='2017-05-01T07:53:58Z' progress=0.187847 cache=158.9MiB(1290158txo)
     9Feb 04 17:23:24 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:24Z UpdateTip: new best=000000000000000001dcc2194c7a334fac60c0c3fd660422be07aee7242fef4e height=464320 version=0x00000004 log2_work=86.363009 tx=217979725 date='2017-05-01T08:07:44Z' progress=0.187848 cache=159.4MiB(1292984txo)
    10Feb 04 17:23:52 raspberrypi5-c8-bf-64 bitcoind[1470]: 2025-02-04T17:23:52Z UpdateTip: new best=000000000000000001bd33d5bc3b4d25d41854a435d3a0f43b155ee793e25c12 height=464321 version=0x20000000 log2_work=86.363041 tx=217981579 date='2017-05-01T08:14:19Z' p
    

    How did you obtain Bitcoin Core

    Compiled from source

    What version of Bitcoin Core are you using?

    all

    Operating system and version

    Linux

    Machine specifications

    No response

  2. pinheadmz commented at 5:58 pm on February 4, 2025: member

    loglevel=info should avoid printing out UpdateTip height=464313

    You are in initial block download. Once the chain is synced these messages will be reduced to one every ten minutes or so ;-)

  3. embetrix commented at 6:06 pm on February 4, 2025: none
    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.
  4. pinheadmz commented at 6:08 pm on February 4, 2025: member

    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?

  5. embetrix commented at 6:12 pm on February 4, 2025: none
    the systemd-journald can be configured to rotate and prune old logs, in this case I see only bitcoind logs
  6. pinheadmz commented at 6:17 pm on February 4, 2025: member
    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.
  7. embetrix commented at 6:18 pm on February 4, 2025: none
    probably the noisy logs from #31796 are writing too much data and wearing out the SDCard quickly if configured to an sd partition instead of RAM.
  8. pinheadmz commented at 6:20 pm on February 4, 2025: member

    wearing out the SDCard

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

  9. embetrix commented at 6:24 pm on February 4, 2025: none
    I have an industrial grade SDCard, I will let you know how it went ;-)
  10. maflcko added the label Linux/Unix on Feb 4, 2025
  11. maflcko commented at 11:31 am on February 5, 2025: member

    If you don’t want the logs to end up in the journal at all, you can configure it so. If you want to disable logs completely, you can do so as well. If you want to filter out info logs, you can do so as well.

    You can also modify the log level locally of the log that you don’t want to see (Bitcoin Core is open source).

    However, I don’t think modifying the log level in the source code here is the correct fix, because (as mentioned) this only happens during IBD and other people expect the log.

    Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

    General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange or the #bitcoin IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

  12. maflcko added the label Questions and Help on Feb 5, 2025
  13. pinheadmz closed this on Feb 5, 2025


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-02-07 15:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me