Log file configuration not working

[Nilsp0]

Hi,

Despite configuring the log level in the chirpstack-packet-multiplexer.toml to "error", the multiplexer writes all levels to the log files during operation. Could it be that the log level configuration is not being applied?

image: chirpstack/chirpstack-packet-multiplexer:4.0.0-test.2

[brocaar]

I can not reproduce this issue. Please make sure to pass the path to the configfile using the -c argument.
The level is set here:

https://github.com/chirpstack/chirpstack-packet-multiplexer/blob/master/src/main.rs#L38

[leogaggl]

I changed the log level from "info" to "error," and the behaviour remained the same.

The logs are full of trace lines:

2025-03-13T03:46:02.678059Z TRACE chirpstack_packet_multiplexer::forwarder: Cleaning up inactive sockets
2025-03-13T03:46:02.678116Z TRACE chirpstack_packet_multiplexer::listener: Cleaning up inactive Gateway ID to addr mappings

I think @Nilsp0 might be right. I am also using image: chirpstack/chirpstack-packet-multiplexer:4.0.0-test.2

[jh83]

I'm also facing the same issue.

Logging in toml file is configured as (I have tested "error", "warn", "WARN" etc):

Servive appears to be started with the correct -c option:

But still there is a lot of logging happening:

[brocaar]

Could you confirm if this issue is still present in -test.3? When I test it on Debian / Ubuntu, this is my output:

# level = "info"

Oct 09 12:58:00 chirpstack-test systemd[1]: Stopping ChirpStack Packet Multiplexer...
Oct 09 12:58:00 chirpstack-test systemd[1]: chirpstack-packet-multiplexer.service: Deactivated successfully.
Oct 09 12:58:00 chirpstack-test systemd[1]: Stopped ChirpStack Packet Multiplexer.
Nov 17 11:48:07 chirpstack-test systemd[1]: Started ChirpStack Packet Multiplexer.
Nov 17 11:48:07 chirpstack-test chirpstack-packet-multiplexer[758098]: 2025-11-17T11:48:07.644976Z  INFO chirpstack_packet_multiplexer: Starting ChirpStack Packet Multiplexer (version: 4.0.0-test.3, docs: https://github.com/chirpstack/chirpstack-package-multiplexer/)
Nov 17 11:48:07 chirpstack-test chirpstack-packet-multiplexer[758098]: 2025-11-17T11:48:07.645722Z  INFO chirpstack_packet_multiplexer::listener: Setting up listener host="0.0.0.0:1700"
Nov 17 11:48:07 chirpstack-test chirpstack-packet-multiplexer[758098]: 2025-11-17T11:48:07.645890Z  INFO chirpstack_packet_multiplexer::forwarder: Setting up forwarder
Nov 17 11:48:07 chirpstack-test chirpstack-packet-multiplexer[758098]: 2025-11-17T11:48:07.645902Z  INFO chirpstack_packet_multiplexer::monitoring: Monitoring endpoint is not configured

# level = "warn"

Nov 17 11:49:21 chirpstack-test systemd[1]: Stopping ChirpStack Packet Multiplexer...
Nov 17 11:49:21 chirpstack-test systemd[1]: chirpstack-packet-multiplexer.service: Deactivated successfully.
Nov 17 11:49:21 chirpstack-test systemd[1]: Stopped ChirpStack Packet Multiplexer.
Nov 17 11:49:21 chirpstack-test systemd[1]: Started ChirpStack Packet Multiplexer.

As you can see, with warn it does not output any INFO logs.