Closed dotsinspace closed 6 months ago
That's not much to go on but version 4.6.0 was released today. Do you have the same issue with 4.5.x?
-------- Original Message -------- On May 17, 2024, 10:57 PM, rootandleaves wrote:
AMQPConnectionError: connection timed out at Timeout._onTimeout @.***/node_modules/rabbitmq-client/lib/Connection.js:285:32) at listOnTimeout (node:internal/timers:573:17) at processTimers (node:internal/timers:514:7) { code: 'CONNECTION_TIMEOUT'
Getting this error from this morning. Tried to restart it did everything but still.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Yes on 4.5.4
Same for 4.6.0
...and for sure local installation have issue. i just executed the command systemctl status rabbitmq-server.service
which outputs following
● rabbitmq-server.service - RabbitMQ Messaging Server
Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2024-05-18 07:54:37 CEST; 26min ago
Main PID: 178753 (beam.smp)
Tasks: 51 (limit: 76072)
Memory: 104.2M
CPU: 9.712s
CGroup: /system.slice/rabbitmq-server.service
├─178753 /usr/lib/erlang/erts-12.2.1/bin/beam.smp -W w -MBas ageffcbf -MHas ageffcbf -MBlmbcs 512 -MHlmbcs 512 -MMmcs 30 -P 1048576 -t 5000000 -stbt db -zdbbl 128000 -sbwt none -sbwtdcpu none -sbwtdio none -- -root /usr/lib/erlang >
├─178764 erl_child_setup 65536
├─178873 inet_gethost 4
└─178874 inet_gethost 4
May 18 07:54:33 Ubuntu-2204-jammy-amd64-base systemd[1]: rabbitmq-server.service: Scheduled restart job, restart counter is at 13.
May 18 07:54:33 Ubuntu-2204-jammy-amd64-base systemd[1]: Stopped RabbitMQ Messaging Server.
May 18 07:54:33 Ubuntu-2204-jammy-amd64-base systemd[1]: Starting RabbitMQ Messaging Server...
May 18 07:54:37 Ubuntu-2204-jammy-amd64-base systemd[1]: Started RabbitMQ Messaging Server.
and even the UI is working fine i can access host:1562 which opens up Rabbit MQ Server
Same here, did you figure it out @dotsinspace ?
Just restarted the server and it worked fine after wards.
Getting this error from this morning. Tried to restart it did everything but still.