Previous to v0.19.x (i.e. in v0.18.5), I could run lncli debuglevel --level info to reduce log verbosity. This no longer works and I continue to receive DBG logs after running the above command. It does appear to only affect the PEER subsystem, other subsystems seem to respect the command.
/ # lncli debuglevel --level info
{
"sub_systems": "ACSM=INF, ARPC=INF, ATPL=INF, BLPT=INF, BRAR=INF, BTCN=INF, BTWL=INF, CHAC=INF, CHBU=INF, CHCL=INF, CHDB=INF, CHFD=INF, CHFT=INF, CHIO=INF, CHNF=INF, CHRE=INF, CLUS=INF, CMGR=INF, CNCT=INF, CNFG=INF, CRTR=INF, DISC=INF, DRPC=INF, FNDG=INF, GRDB=INF, GRPH=INF, HLCK=INF, HSWC=INF, INVC=INF, IRPC=INF, LCHN=INF, LNWL=INF, LTND=INF, MSGX=INF, NANN=INF, NRPC=INF, NTFN=INF, NTFR=INF, PEER=INF, PFSM=INF, PRNF=INF, PROM=INF, PRPC=INF, RPCC=INF, RPCP=INF, RPCS=INF, RPWL=INF, RRPC=INF, SGNR=INF, SPHX=INF, SQLB=INF, SQLD=INF, SRVR=INF, SWPR=INF, TORC=INF, UTXN=INF, VRPC=INF, WLKT=INF, WTCL=INF, WTWR=INF"
}
2025-07-16 14:51:07.423 [DBG] PEER: Peer(020003b9499a97c8dfbbab6b196319db37ba9c37bccb60477f3c867175f417988e): Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=952307911615119360, mflags=00000001, cflags=00000000, update_time=2025-07-16 14:47:53 +0000 UTC) from 020003b9499a97c8dfbbab6b196319db37ba9c37bccb60477f3c867175f417988e@vr47stl576kawzuogikujvopddkztcsjigvu2jgnkcztl5kupjytumqd.onion:9735
Background
Previous to v0.19.x (i.e. in v0.18.5), I could run
lncli debuglevel --level infoto reduce log verbosity. This no longer works and I continue to receiveDBGlogs after running the above command. It does appear to only affect thePEERsubsystem, other subsystems seem to respect the command.Your environment
lnd: v0.19.1uname -aon *Nix): Linux lnd-0 6.6.72+ Fix name typo in README #1 SMP PREEMPT_DYNAMIC Sun Apr 27 08:53:34 UTC 2025 x86_64 Linuxbtcd,bitcoind, or other backend:Steps to reproduce
lnd.conf, havedebuglevel=debuglncli debuglevel --level infoDBGlevel, specifically for thePEERsubsystem.Expected behaviour
Only logs of
INFlevel should output after settingdebuglevelActual behaviour
Logs for the
PEERsubsystem continue to output atDBGlevelExample:
Shortly (seconds after running above):