It's hard to see (huge command line), but that's the output when
rabbitmq is started, believe me.
I tried stop / start the rabbitmq-server.service a few times, and it did
work for me, no problem (even though it was a bit slow on the arm64 VM I
was using, which is kind of expected with rabbitmq-server).
I'm therefore downgrading this bug to severity: important, until further
investigation can be done on your side. Indeed, this looks like specific
to your environment here.