rabbitmq crash - old version

[vjvel]

Hi,
@michaelklishin this discussion is based on the below issue. I understand we have too old version and its recommended to 3 node cluster.

#5750

{"log":"2022-09-10 04:05:49.096 [error] \u003c0.9326.50\u003e Supervisor {\u003c0.9326.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exit son noproc in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:05:49.286323973Z"}
{"log":"2022-09-10 04:05:50.088 [error] \u003c0.8918.50\u003e Supervisor {\u003c0.8918.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exit son shutdown in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:05:50.186507194Z"}
{"log":"2022-09-10 04:05:53.586 [error] \u003c0.14891.50\u003e Supervisor {\u003c0.14891.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exieason shutdown in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:05:53.587486765Z"}
{"log":"2022-09-10 04:05:53.890 [error] \u003c0.19236.50\u003e Supervisor {\u003c0.19236.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exieason shutdown in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:05:53.987212657Z"}
{"log":"2022-09-10 04:05:54.490 [error] \u003c0.14126.50\u003e Supervisor {\u003c0.14126.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exieason shutdown in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:05:54.491935074Z"}
{"log":"2022-09-10 04:05:58.287 [error] \u003c0.25638.50\u003e Supervisor {\u003c0.25638.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exieason shutdown in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:05:58.386332497Z"}
{"log":"2022-09-10 04:05:59.192 [error] \u003c0.11951.50\u003e Supervisor {\u003c0.11951.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exieason shutdown in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:05:59.286367619Z"}
{"log":"2022-09-10 04:06:00.292 [error] \u003c0.28680.50\u003e Supervisor {\u003c0.28680.50\u003e,rabbit_channel_sup_sup} had child channel_sup started with rabbit_channel_sup:start_link() at undefined exieason shutdown in context shutdown_error\n","stream":"stdout","time":"2022-09-10T04:06:00.488689958Z"}
{"log":"2022-09-10 04:06:00.392 [error] \u003c0.18532.50\u003e Supervisor {\u003c0

you mentione the above error can be ignored, but during this error only the docker container exited and restarted by liveness probe. before we upgrading the version increase to 3 replicas. we need to know why it got crash with this error log. if you could give some inputs it would be great.

   "rabbitmq-server"
        ],
        "State": {
            "Status": "exited",
            "Running": false,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 0,
            "ExitCode": 137,
            "Error": "",
            "StartedAt": "2022-09-08T21:27:03.990458671Z",
            "FinishedAt": "2022-09-10T04:06:42.343269017Z"

I have another question about HA , currently if one pod fail the associate queue is getting down, to acheive ha, we need to enable ha-fed agent and enable mirroring for the classic queues ?

[michaelklishin]

We cannot suggest much without full logs from all nodes and a Kubernetes deployment file. We do not guess in this community: guessing is very expensive and you pay $0 for support here.

[vjvel]

I will share the logs and configuration, I am not asking you to guess, I ask the recommendation for the config.