Setting Ranch options together with socket options is deprecated

[Raul Kaubi]

Hi

Rabbitmq 3.7.17

Erlang 21.3.8.6

What does this Ranch warning mean..?

And what would be the new syntax for that..?

2019-08-05 09:29:58.358 [info] <0.2777.0> rabbit on node 'rabbit@test-dc1-rabbit' up
2019-08-05 09:29:58.361 [warning] <0.3794.0> Setting Ranch options together with socket options is deprecated. Please use the new map syntax that allows specifying socket options separately from other options.
2019-08-05 09:29:58.362 [info] <0.3809.0> started TCP listener on [::]:5672
2019-08-05 09:29:58.363 [warning] <0.3810.0> Setting Ranch options together with socket options is deprecated. Please use the new map syntax that allows specifying socket options separately from other options.
2019-08-05 09:29:58.366 [info] <0.3825.0> started TLS (SSL) listener on [::]:5671
2019-08-05 09:29:58.366 [info] <0.2597.0> Running boot step direct_client defined by app rabbit
2019-08-05 09:29:58.452 [info] <0.3907.0> Management plugin: HTTP (non-TLS) listener started on port 15672
2019-08-05 09:29:58.483 [info] <0.3907.0> Management plugin: HTTPS listener started on port 15671
2019-08-05 09:29:58.483 [info] <0.4122.0> Statistics database started.
2019-08-05 09:29:58.483 [info] <0.4121.0> Starting worker pool 'management_worker_pool' with 3 processes in it
2019-08-05 09:29:58.614 [notice] <0.2470.0> Changed loghwm of /var/log/rabbitmq/rab...@test-dc2-rabbit.log to 50
2019-08-05 09:30:00.116 [info] <0.2362.0> Server startup complete; 7 plugins started.
 * rabbitmq_tracing
 * rabbitmq_shovel_management
 * rabbitmq_management
 * rabbitmq_web_dispatch
 * rabbitmq_auth_backend_ldap
 * rabbitmq_shovel
 * rabbitmq_management_agent

rabbitmq.conf looks like this:

listeners.tcp.default = 5672
listeners.ssl.default = 5671
ssl_options.cacertfile = <<cacertfile_location>>
ssl_options.certfile   = <<certfile_location>>
ssl_options.keyfile    = <<keyfile_location>>

handshake_timeout = 20000
ssl_handshake_timeout = 20000
reverse_dns_lookups = true
# Authentication/authorisation
auth_backends.1   = rabbit_auth_backend_internal
auth_backends.2   = rabbit_auth_backend_ldap
auth_ldap.servers.1 = <<AD domain>>
auth_ldap.use_ssl = true
auth_ldap.port = 636
auth_ldap.user_dn_pattern = ${username}@<<domain>>
auth_ldap.dn_lookup_attribute = userPrincipalName
auth_ldap.dn_lookup_base      = DC=<<domain>>,DC=<<com>>
# Management plugin
management.tcp.port = 15672
management.ssl.port       = 15671
management.ssl.cacertfile = <<cacertfile_location>>
management.ssl.certfile   = <<certfile_location>>
management.ssl.keyfile    = <<keyfile_location>>
# Retention policies
management.sample_retention_policies.global.minute  = 5
management.sample_retention_policies.global.hour    = 60
management.sample_retention_policies.global.day     = 1200
management.sample_retention_policies.basic.minute = 5
management.sample_retention_policies.basic.hour   = 60
management.sample_retention_policies.basic.day    = 1200
management.sample_retention_policies.detailed.10 = 5
cluster_partition_handling = autoheal

Raul

[Luke Bakken]

Hi Raul,

This is due to how RabbitMQ passes options to ranch. It is an internal warning that can be ignored. We will fix it when time allows.

Thanks,

Luke

On Sunday, August 4, 2019 at 11:45:43 PM UTC-7, Raul Kaubi wrote:

Hi

Rabbitmq 3.7.17

Erlang 21.3.8.6

What does this Ranch warning mean..?

And what would be the new syntax for that..?

2019-08-05 09:29:58.358 [info] <0.2777.0> rabbit on node 'rabbit@test-dc1-rabbit' up
2019-08-05 09:29:58.361 [warning] <0.3794.0> Setting Ranch options together with socket options is deprecated. Please use the new map syntax that allows specifying socket options separately from other options.
2019-08-05 09:29:58.362 [info] <0.3809.0> started TCP listener on [::]:5672
2019-08-05 09:29:58.363 [warning] <0.3810.0> Setting Ranch options together with socket options is deprecated. Please use the new map syntax that allows specifying socket options separately from other options.
2019-08-05 09:29:58.366 [info] <0.3825.0> started TLS (SSL) listener on [::]:5671
2019-08-05 09:29:58.366 [info] <0.2597.0> Running boot step direct_client defined by app rabbit
2019-08-05 09:29:58.452 [info] <0.3907.0> Management plugin: HTTP (non-TLS) listener started on port 15672
2019-08-05 09:29:58.483 [info] <0.3907.0> Management plugin: HTTPS listener started on port 15671
2019-08-05 09:29:58.483 [info] <0.4122.0> Statistics database started.
2019-08-05 09:29:58.483 [info] <0.4121.0> Starting worker pool 'management_worker_pool' with 3 processes in it

2019-08-05 09:29:58.614 [notice] <0.2470.0> Changed loghwm of /var/log/rabbitmq/rabbit@test-dc2-rabbit.log to 50

[Luke Bakken]

If you would like to monitor the issue, please watch this GitHub issue - https://github.com/rabbitmq/rabbitmq-server/issues/2069

[Diana Corbacho]

This is fixed in 3.8, see comments in https://github.com/rabbitmq/rabbitmq-server/issues/2069