We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No
When i add RabbitMQ node (With rabbitmq_management enabled) into Kuma, kuma return 406 in results Node appear Offline.
Add RabbitMQ node HTTP (If rabbitmq-plugins enable rabbitmq_management work) Wait for results
Node appear Online and working
Node appear Offline
2.0.0-beta.0
Ubuntu 22.04 LTS
Opera
uptime-kuma-1 | 2024-11-07T08:21:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:21:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:22:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:22:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:22:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:23:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:25:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:25:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:26:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:26:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:26:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:27:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:29:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:29:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:30:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:30:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:30:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0 uptime-kuma-1 | 2024-11-07T08:31:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
The text was updated successfully, but these errors were encountered:
cc: @Suven-p
Sorry, something went wrong.
@FlashModz Which version of rabbitmq are you using?
Hi,
It's the 3.8.14, Erlang 23.2.3.
@FlashModz Could you also include the response from rabbitmq health check endpoint? Preferably from inside kuma container
curl -v "http://$rmqHost:$rmqPort/api/health/checks/alarms" -H "Authorization:Basic $(echo -n $rmqUser:$rmqPass | base64)"
No branches or pull requests
π I have found these related issues/pull requests
No
π‘οΈ Security Policy
Description
When i add RabbitMQ node (With rabbitmq_management enabled) into Kuma, kuma return 406 in results
Node appear Offline.
π Reproduction steps
Add RabbitMQ node HTTP (If rabbitmq-plugins enable rabbitmq_management work)
Wait for results
π Expected behavior
Node appear Online and working
π Actual Behavior
Node appear Offline
π» Uptime-Kuma Version
2.0.0-beta.0
π» Operating System and Arch
Ubuntu 22.04 LTS
π Browser
Opera
π₯οΈ Deployment Environment
π Relevant log output
The text was updated successfully, but these errors were encountered: