Chirpstack Bridge logging

Hi,

I have set up a chirpstack gateway bridge for connecting to my MQTT server. That’s work fine but I have a problem with the logging. All logs are written into the syslog. In the chirpstack-gateway-bridge.toml file I have set the log_level=2 and log_to_syslog=false
Any idea why that not work?
Here the .toml file

# This configuration provides a Semtech UDP packet-forwarder backend and
# integrates with a MQTT broker. Many options and defaults have been omitted
# for simplicity.
#
# See https://www.chirpstack.io/gateway-bridge/install/config/ for a full
# configuration example and documentation.
[general]
# debug=5, info=4, warning=3, error=2, fatal=1, panic=0
log_level=2
log_to_syslog=false

# Gateway backend configuration.
[backend]
# Backend type.
type="semtech_udp"

  # Semtech UDP packet-forwarder backend.
  [backend.semtech_udp]

  # ip:port to bind the UDP listener to
  #
  # Example: 0.0.0.0:1700 to listen on port 1700 for all network interfaces.
  # This is the listener to which the packet-forwarder forwards its data
  # so make sure the 'serv_port_up' and 'serv_port_down' from your
  # packet-forwarder matches this port.
  udp_bind = "127.0.0.1:1700"


# Integration configuration.
[integration]
# Payload marshaler.
#
# This defines how the MQTT payloads are encoded. Valid options are:
# * protobuf:  Protobuf encoding
# * json:      JSON encoding (easier for debugging, but less compact than 'protobuf')
#marshaler="protobuf"
marshaler="json"
  # MQTT integration configuration.
  [integration.mqtt]
  # Event topic template.
  event_topic_template="my_lora_gateway/{{ .GatewayID }}/event/{{ .EventType }}"

  # Command topic template.
  command_topic_template="my_lora_gateway/{{ .GatewayID }}/command/#"

  # MQTT authentication.
  [integration.mqtt.auth]
  # Type defines the MQTT authentication type to use.
  #
  # Set this to the name of one of the sections below.
  type="generic"

    # Generic MQTT authentication.
    [integration.mqtt.auth.generic]
    # MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
    server="tcp://192.168.42.31:1883"

    # Connect with the given username (optional)
    username="<user>"

    # Connect with the given password (optional)
    password="<pw>"

Norbert

Is it still logging to syslog when set to false?

And you restarted to service after changing the config?