request timeout issue in rabbitmq

[Satheesh Kumar]

Hi 

I am using rabbitmq version 3.8.14 and were using peer discovery using consul in kubernetes
i am trying to increase timeout using the following option

# For RabbitMQ 3.7.9 and later versions. # # Configures HTTPS (TLS-enabled) listener timeouts management.ssl.idle_timeout = 120000 management.ssl.inactivity_timeout = 120000 management.ssl.request_timeout = 120000

but after this change my pod not starting

"log":" no other nodes on rabbitmq-57c58b6b48-9jkbf |
"log":" * epmd reports: node 'rabbit' not running at all |
"log":" * connected to epmd (port 4369) on  rabbitmq-57c58b6b48-9jkbf"} |
"log":" * suggestion: start the node", |
"log":" * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)", |
"log":" * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)" |
"log":" * Target node is not running"


How to increase the request time out for management api(now timeout after 1 minute)
I am using management api to exporting definition(It have nearly 25k connections, 30k queues and 50k exchanges and lot of user, bindings)

I know there is  rabbitmqctl export_definitions but i need http management api to get fixed

I am seeing this issue https://github.com/rabbitmq/rabbitmq-server/pull/4408
which is fixed in rabbitmq version 3.10

My question is there any way to fix it same version 3.8.14 or do i need to upgrade

[Luke Bakken]

Hello,

RabbitMQ 3.8 is no longer supported, so you should upgrade.

It is unclear why changing those settings affects RabbitMQ startup, because you do not share your complete, un-edited configuration file, nor do you share your RabbitMQ logs, nor what Erlang version you're using.

What I can reproduce is that if I use RabbitMQ 3.8.14 with Erlang 24.X and those management settings, RabbitMQ won't start due to a missing function in Erlang. Using Erlang 23.3.4.17 fixes the issue.

At any rate, please upgrade.

Thanks -
Luke