Logger reports a malformatted string

[sergey-safarov]

Describe the bug

I have started rabbitmq:4.1.0-alpine docker image, and we have configured server with HAproxy support

loopback_users.guest = false
listeners.tcp.default = 5672
default_pass = xxxxxxx
default_user = yyyyyyy
vm_memory_high_watermark.relative = 0.7
cluster_partition_handling = autoheal
tcp_listen_options.keepalive = true
cluster_formation.peer_discovery_backend = rabbit_peer_discovery_classic_config
cluster_formation.classic_config.nodes.1 = rabbit@srv0.example.com
cluster_formation.classic_config.nodes.2 = rabbit@srv1.example.com
prometheus.tcp.port = 15692
prometheus.tcp.ip = ::
management.tcp.ip = ::
management_agent.disable_metrics_collector = false
proxy_protocol = true
log.console = true
log.console.level = info
log.file = false
channel_max = 0
deprecated_features.permit.management_metrics_collection = true
deprecated_features.permit.transient_nonexcl_queues = true

Some RabbitMQ clients negotiate wrong connection settings, and it looks like this triggers an error

FORMATTER CRASH: {"closing AMQP connection ~tp (~ts):~nfailed to negotiate connection parameters: ~ts",[<0.1785285.0>,<<"[2600:xxxx:6d8:5404:40b6:bcde:db0c:9e15]:55208 -> [2605:xxxx:49:1f00::4]:35672">>,"3s","negotiated frame_max = 4096 is lower than the minimum allowed value (8192)"]}

Could you check the format string of the log message?

Reproduction steps

...

Expected behavior

No error messages like

error: FORMATTER CRASH:

Additional context

No response

[michaelklishin]

@sergey-safarov we cannot comment on "some clients" and "wrong connection settings". We do not guess in this community.

The message is nothing more than log noise on a closing connection.

#13840 looks highly relevant and it's shipped in 4.1.1.