rabbitmq-server died abruptly

We saw a rabbimq-server unit which is the leader in a cluster with 2 others die abruptly. Cluster status on other units remained ok, except for inability to communicate with the downed node. We were unable to determine a root cause. We've seen this happen on 3 other occasions and on one we observed that before starting the rabbit service the jujud agent was in error state; afterwards it was in executing state. I do not know if that was the case this time.

== LOGS ETC. ==

Service status after failure:

https://pastebin.canonical.com/p/nbcGBmr2b5/

================================

From juju unit log, I see repetitions similar to the first section (02:05:42-02:05:44) going back for days. At the time of the failure 02:05:45, it abruptly cuts away to reporting inability to connect. This section of enteries (02:05:45-02:10:49) basically repeats until the service is manually restarted around 02:46:18, where it goes back to the WARNING and entries resembling the first section:

https://pastebin.canonical.com/p/ZGjtM647JZ/

================================

In the rabbit logs (/<email address hidden>) we see it abruptly stop logging at the time of death and then start up again with the unit starting up at recovery:

https://pastebin.canonical.com/p/vd5kj3CvDf/

================================

syslog from time of failure to time of recovery:

https://pastebin.canonical.com/p/pVpFTVHXC3/