Can't add a new trace

[ysjjovo]

Steps to reproduce.
Setup rabbitmq cluster with tracing plugin enabled.

apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
  name: def
  namespace: default
spec:
  image: rabbitmq:3.9.11
  replicas: 1
  resources:
    requests:
      cpu: 500m
      memory: 500Mi
    limits:
      cpu: 500m
      memory: 500Mi
  persistence:
    storageClassName: hostpath
    storage: 1Gi
  service:
    type: NodePort
  rabbitmq:
    additionalPlugins:
      - rabbitmq_tracing

Then going to management UI,admin tab,tracing menu,input name 'df',last click 'Add trace' button',here is the prompt error messages.

Node '[email protected]' could not be contacted: {badrpc,
...

But trace log successfully generated in the target file.

 kubectl exec def-server-0 -- cat /var/tmp/rabbitmq-tracing/gf.log

Defaulted container "rabbitmq" out of: rabbitmq, setup-container (init)

================================================================================
2021-12-06 8:56:38:529: Message published

Node:         [email protected]
Connection:   192.168.65.3:48300 -> 10.1.0.100:5672
Virtual host: /
User:         default_user_EtvssC4bIGU7rznNoCy
Channel:      1
Exchange:     logs_topic
Routing keys: [<<"-test.run">>]
Routed queues: []
Properties:   [{<<"content_type">>,longstr,<<"text/plain">>}]
Payload:
^TestSend$
...

Aditional environment info

➜  rabbitmq cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"
➜  rabbitmq kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.5", GitCommit:"aea7bbadd2fc0cd689de94a54e5b7b758869d691", GitTreeState:"clean", BuildDate:"2021-09-15T21:10:45Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:53:14Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"linux/amd64"}

[mkuratczyk]

Your pod is called def-server-0 (which matches the YAML you provided) but the error is Node '[email protected]' could not be contacted - did you edit the output before submitting? If not - do you have any idea where definitions came from?

[ysjjovo]

Your pod is called def-server-0 (which matches the YAML you provided) but the error is Node '[email protected]' could not be contacted - did you edit the output before submitting? If not - do you have any idea where definitions came from?

Sorry for my carelessness，I will correct it right now and supply more environment infomation.

[michaelklishin]

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(

[michaelklishin]

Every trace is backed by a text file stored under rabbitmq_tracing.directory (configurable using advanced.config). If the node has no permissions to create files there, you won't be able to add a trace. You also don't have to trace to a file, any consumer would do.

[ysjjovo]

The click action 'Add Trace' returns error message,but when i send and receive some message ,the trace log successfuly appended into file '/var/tmp/rabbitmq-tracing/gf.log'.I think it's not a permission problem.