RabbitMQ - 无法联系统计数据库。消息速率和队列长度将不会显示

发布于 2024-12-08 18:40:36 字数 183 浏览 1 评论 0原文

我已经设置了一个兔子经纪人集群,在管理门户插件中,我收到以下消息

“无法联系统计数据库。消息速率和队列长度将不会显示”

我已经搜索了此错误,但谷歌并不友善。任何人都可以阐明这一点吗?

在此处输入图像描述

I have setup a cluster of rabbit brokers and within the management portal plugin I get the following message

"Statistics database could not be contacted. Message rates and queue lengths will not be shown"

I have searched for this error but google is not being kind. Can anyone shed any light on this?

enter image description here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

淡淡的优雅 2024-12-15 18:40:36

我最近在旧安装的RabbitMQ(2.8.7)上遇到了同样的问题,发现这个问题没有解决方案。我发现要重新启动统计数据库,可以执行:

rabbitmqctl eval 'application:stop(rabbitmq_management), application:start(rabbitmq_management).'

(来源:http://en.it-usenet.org/thread/15496 /19206/#post19199

I had the same problem recently on an old installation of RabbitMQ (2.8.7) and found that there was no solution in this question. I found that to restart the statistics database, you can execute:

rabbitmqctl eval 'application:stop(rabbitmq_management), application:start(rabbitmq_management).'

(Source: http://en.it-usenet.org/thread/15496/19206/#post19199)

淡忘如思 2024-12-15 18:40:36

2012-01-11 更新:我们相信我们找到了这个问题的根源并在 2.7.1 中修复了它。然而,它非常依赖于时间,所以我们永远无法复制它。如果有人在 2.7.1 或更高版本中看到此内容,您可以邮寄[电子邮件受保护]请?

旧答案如下:

这实际上不是您应该在 2.6.1 中看到的消息。我很想知道你是如何到达那里的。

管理插件在集群中的一个节点上维护单个内存统计数据库,即使它安装在多个/所有节点上。在 2.6.0 之前,如果托管数据库的节点出现故障或被删除,您会看到该错误。但在 2.6.0 中,我们确保(或者我认为我们做到了)统计数据库将迁移到另一个节点并在必要时重建自身。

所以这可能不是一个很好的 Stack Overflow 问题,因为它看起来更像是一个错误报告。您是在节点发生故障/被删除后还是从一开始就看到了这一点? mgmt 是安装在所有节点上还是只安装在一个节点上?您能将各个节点的日志发送给我们吗?事实上,回复[电子邮件受保护]可能更好。

Update 2012-01-11: We believe we found the source of this and fixed it in 2.7.1. However it's very timing-dependent so we were never able to replicate it. If anyone sees this in 2.7.1 or later, can you mail [email protected] please?

Old answer follows:

That's not really a message you should even be able to see in 2.6.1. I would be interested to know how you got there.

The management plugin maintains a single in-memory statistics database on one node in the cluster, even if it's installed on several / all nodes. Prior to 2.6.0 you would see that error if the node hosting the database failed or was removed. But in 2.6.0 we ensured (or I thought we did) that the statistics database would migrate to another node and reconstruct itself if necessary.

So this might not be a very good Stack Overflow question as it's looking more like a bug report. Do you see this after a node has failed / been removed or right from the start? Is mgmt installed on all nodes or just one? Can you send us the logs from the various nodes? Probably better to reply to [email protected] in fact.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文