"rabbitmq-diagnostics resolver_info" error

[Duncan Ferguson]

Hi,

I have a problem with using "rabbitmqctl status" communicating with the node it is run on.  I have gone through the diagnostic output suggestions and not found an issue, so I am trying to use "rabbitmq-diagnostics resolver_info" to give me a hint about where to look next.

However, this tools returns the attached stack trace which I have been unable to find the cause of.

I have two servers that (I believe are) built the same, one had no problems, the other does.  I have checked contents and permissions on /etc/hosts, /etc/resolv.conf and /etc/nsswitch.conf (which I picked up from the erlang inetrc docs pages for system lookups), and not yet found a difference between the hosts.

Where might I look next?

Thanks

  Duncs

[Michal Kuratczyk]

Hi,

The important part of the error is badrpc/nodedown - the CLI could not connect to the server node to retrieve the information. If you are running the command locally on the same machine, then you may need to provide "-n node_name". For example, I have a node called "rabbit" running on my machine:

$ rabbitmq-diagnostics -n rabbit resolver_info
Asking node rabbit@mkuratczyk-a01 for its effective hostname resolver (inetrc) configuration...
Runtime Hostname Resolver (inetrc) Settings

Lookup order: native
Hosts file: /etc/hosts
Resolver conf file: /etc/resolv.conf
Cache size:

inetrc File Host Entries

(none)

If I try any other name, I get the same error as you:

$ rabbitmq-diagnostics -n rabbit-1 resolver_info
Asking node rabbit-1@mkuratczyk-a01 for its effective hostname resolver (inetrc) configuration...
Stack trace:

** (FunctionClauseError) no function clause matching in Access.get/3
    (elixir 1.11.4) lib/access.ex:284: Access.get({:badrpc, :nodedown}, "lookup", nil)

"rabbit" is the default node name for the CLIs so in my case, I can skip "-n rabbit" and it still works.

Best,

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/8db7234b-ed91-4c04-8a00-e69b7ed7a910n%40googlegroups.com.

--

Michał

RabbitMQ team

[Duncan Ferguson]

Thank you for replying - unfortunately, using the -n switch against the local node did not help and I got the exact same error, and there was nothing in any logs or rabbitmq-server output that suggested what was happening.  Using a ping test against the node host name in the resolver output all worked without issue.

I have resorted to purging everything and resetting it up from scratch to see if there was a typo or other problem I couldn't find

  Duncs