Rabbitmq not starts at booting

125 views
Skip to first unread message

Rajalakshmi A

unread,
Jul 23, 2024, 7:24:29 AM7/23/24
to rabbitmq-users
i believe  channel leaks are there .how to control  it via rabbitmq.config. i am using rabbitmq-server 3.12.12 based on rhel9 OS.One more info ,the below error observe  during boot only. after boot if we start or restart rabbitmq service the below error gwent and rabbitmq working.

Please find the error logs from my end: 
2024-07-20 04:00:01.617184-07:00 [debug] <0.138.0> Boot state/systemd: notifying of state `ready`
2024-07-20 04:00:01.673503-07:00 [info] <0.9.0> Time to start RabbitMQ: 9581382 us
2024-07-20 04:00:05.844938-07:00 [info] <0.1482.0> accepting AMQP connection <0.1482.0> (127.0.0.1:51884 -> 127.0.0.1:5672)
2024-07-20 04:00:05.848631-07:00 [debug] <0.1482.0> Client address during authN phase: {0,0,0,0,0,65535,32512,1}
2024-07-20 04:00:05.848769-07:00 [debug] <0.1482.0> User 'app' authenticated successfully by backend rabbit_auth_backend_internal
2024-07-20 04:00:05.852698-07:00 [info] <0.1482.0> connection <0.1482.0> (127.0.0.1:51884 -> 127.0.0.1:5672): user 'app' authenticated and granted access to vhost '/'
2024-07-20 04:00:28.265695-07:00 [debug] <0.1499.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-07-20 04:00:28.265802-07:00 [debug] <0.1499.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-07-20 04:00:30.525248-07:00 [debug] <0.1506.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-07-20 04:00:30.525353-07:00 [debug] <0.1506.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-07-20 04:00:34.282772-07:00 [info] <0.1510.0> accepting AMQP connection <0.1510.0> (127.0.0.1:37508 -> 127.0.0.1:5672)
2024-07-20 04:00:34.284562-07:00 [debug] <0.1510.0> Client address during authN phase: {0,0,0,0,0,65535,32512,1}
2024-07-20 04:00:34.284691-07:00 [debug] <0.1510.0> User 'app' authenticated successfully by backend rabbit_auth_backend_internal
2024-07-20 04:00:34.285852-07:00 [info] <0.1510.0> connection <0.1510.0> (127.0.0.1:37508 -> 127.0.0.1:5672): user 'app' authenticated and granted access to vhost '/'
2024-07-20 04:00:34.468220-07:00 [warning] <0.1510.0> closing AMQP connection <0.1510.0> (127.0.0.1:37508 -> 127.0.0.1:5672, vhost: '/', user: 'app'):
2024-07-20 04:00:34.468220-07:00 [warning] <0.1510.0> client unexpectedly closed TCP connection
2024-07-20 04:00:34.468693-07:00 [debug] <0.1523.0> Closing 1 channel(s) because connection '127.0.0.1:37508 -> 127.0.0.1:5672' has been closed
2024-07-20 04:00:35.177521-07:00 [info] <0.1529.0> RabbitMQ is asked to start...
2024-07-20 04:00:35.177690-07:00 [info] <0.1529.0> Time to start RabbitMQ: 178 us
2024-07-20 04:00:36.040895-07:00 [info] <0.1534.0> RabbitMQ is asked to stop...
2024-07-20 04:00:36.079275-07:00 [debug] <0.1534.0> Plugins discovery: ignoring getopt, not a RabbitMQ plugin
2024-07-20 04:00:36.079386-07:00 [debug] <0.1534.0> Plugins discovery: ignoring quantile_estimator, not a RabbitMQ plugin
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0> Stopping RabbitMQ applications and their dependencies in the following order:
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     rabbitmq_management
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     rabbitmq_management_agent
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     rabbitmq_web_dispatch
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     cowboy
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     cowlib
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     rabbit
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     rabbitmq_prelaunch
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     amqp_client
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     rabbit_common
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     ra
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     os_mon
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     sysmon_handler
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     osiris
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>     mnesia
2024-07-20 04:00:36.089828-07:00 [info] <0.1534.0>
2024-07-20 04:00:36.090078-07:00 [info] <0.1534.0> Stopping application 'rabbitmq_management'
2024-07-20 04:00:36.092316-07:00 [warning] <0.1382.0> HTTP listener registry could not find context rabbitmq_management_tls
2024-07-20 04:00:36.094855-07:00 [notice] <0.44.0> Application rabbitmq_management exited with reason: stopped
2024-07-20 04:00:36.095016-07:00 [info] <0.1534.0> Stopping application 'rabbitmq_management_agent'
2024-07-20 04:00:36.098534-07:00 [notice] <0.44.0> Application rabbitmq_management_agent exited with reason: stopped
2024-07-20 04:00:36.098675-07:00 [info] <0.1534.0> Stopping application 'rabbitmq_web_dispatch'
2024-07-20 04:00:36.100659-07:00 [notice] <0.44.0> Application rabbitmq_web_dispatch exited with reason: stopped
2024-07-20 04:00:36.100765-07:00 [info] <0.1534.0> Stopping application 'cowboy'
2024-07-20 04:00:36.102346-07:00 [notice] <0.44.0> Application cowboy exited with reason: stopped
2024-07-20 04:00:36.102490-07:00 [info] <0.1534.0> Stopping application 'cowlib'
2024-07-20 04:00:36.102581-07:00 [notice] <0.44.0> Application cowlib exited with reason: stopped
2024-07-20 04:00:36.102664-07:00 [info] <0.1534.0> Stopping application 'rabbit'
2024-07-20 04:00:36.102783-07:00 [debug] <0.237.0> Change boot state to `stopping`
2024-07-20 04:00:36.102906-07:00 [debug] <0.138.0> Boot state/systemd: sending non-systemd state (stopping) as status description: ""
2024-07-20 04:00:36.102904-07:00 [info] <0.237.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping unregistration.
2024-07-20 04:00:36.103079-07:00 [info] <0.1478.0> stopped TCP listener on [::]:5672
2024-07-20 04:00:36.103992-07:00 [error] <0.1482.0> Error on AMQP connection <0.1482.0> (127.0.0.1:51884 -> 127.0.0.1:5672, vhost: '/', user: 'app', state: running), channel 0:
2024-07-20 04:00:36.103992-07:00 [error] <0.1482.0>  operation none caused a connection exception connection_forced: "broker forced connection closure with reason 'shutdown'"
2024-07-20 04:00:36.105741-07:00 [info] <0.1539.0> Closing all connections in vhost '/' on node "rabbit@node-009778-internal" because the vhost is stopping

jo...@cloudamqp.com

unread,
Jul 23, 2024, 12:36:42 PM7/23/24
to rabbitmq-users
Hi,

Stopping a channel leak is done in the client. It is not RabbitMQ opening channels (except for federation and shovel, but you are not using them). You can set a channel_max in the config, to say 100. That way you'll make sure than not more than 100 channels can be opened per connection.

There is no evidence for a channel leak in the log you sent. You have one connection and channel opening and closing between RabbitMQ starting and stopping.
Check your syslog, because "RabbitMQ is asked to stop..."

/Johan

Rajalakshmi A

unread,
Jul 24, 2024, 2:11:24 AM7/24/24
to rabbitmq-users

how can i resolve this issue  and any other logs do you need for this issue. why rabbitmq is stopping on boot?

jo...@cloudamqp.com

unread,
Jul 24, 2024, 10:27:40 AM7/24/24
to rabbitmq-users
The first step is to look at the syslog, it should tell you why RabbitMQ is stopped.

Rajalakshmi A

unread,
Aug 16, 2024, 11:56:29 AM8/16/24
to rabbitmq-users
IN syslog i am not observing any error related to rabbitmq. Can you please confirm me  these two versions will work or not somewhere in google  i see rabbitmq server 3.12  works on erlang 25.x versions .rabbitmq-server  version is 3.12.12 and erlang version is 26.2.5.. I am  facing only amqp protocol error .As per my understanding  5672 port is for AMQP and rabbitmq  is gracefully shutting down. Could you please  help me what are the possible cases  rabbitmq went to grace shutdown.

jo...@cloudamqp.com

unread,
Aug 16, 2024, 1:13:18 PM8/16/24
to rabbitmq-users
Hi,
"RabbitMQ is asked to stop" means that some system process is asking it to stop. Maybe a monitoring system?

Using this link you can see which versions of RabbitMQ works with corresponding Erlang versions: https://www.rabbitmq.com/docs/which-erlang

/Johan
Reply all
Reply to author
Forward
0 new messages