Skip to content
New issue

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

[RabbitMQ] Monitor troubleshooting #5320

Open
1 task done
FlashModz opened this issue Nov 7, 2024 · 4 comments
Open
1 task done

[RabbitMQ] Monitor troubleshooting #5320

FlashModz opened this issue Nov 7, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@FlashModz
Copy link

πŸ“‘ 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.

image
image

πŸ‘Ÿ 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

  • Runtime: Docker 27.2.1, build 9e34c9b
  • Database: sqlite/embedded
  • Filesystem used to store the database on:
  • number of monitors: 62

πŸ“ Relevant log output

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
@FlashModz FlashModz added the bug Something isn't working label Nov 7, 2024
@louislam
Copy link
Owner

louislam commented Nov 9, 2024

cc: @Suven-p

@Suven-p
Copy link
Contributor

Suven-p commented Nov 9, 2024

@FlashModz Which version of rabbitmq are you using?

@FlashModz
Copy link
Author

@FlashModz Which version of rabbitmq are you using?

Hi,

It's the 3.8.14, Erlang 23.2.3.

@Suven-p
Copy link
Contributor

Suven-p commented Nov 16, 2024

@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)"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants