https://bugzilla.redhat.com/show_bug.cgi?id=1360657
--- Comment #5 from Mathieu Bridon <bochecha(a)daitauha.fr> ---
(In reply to Peter Lemenkov from comment #3)
(In reply to Mathieu Bridon from comment #2)
> I guess an update might have fixed it?
I doubt that. I've just downgraded to rabbitmq-server-3.6.2-3.fc24.noarch
and it still starts fine on my PC.
I meant an update of something like the selinux policy.
In my original comment, when I said « it might be an update that broke it? », I
didn't mean a rabbitmq update, since I hadn't had any after installing it, but
I had received other updates, among which there might have been an selinux one.
Perhaps someone messed with selinux permissions in your
/var/lib/rabbitmq or
/var/log/rabbitmq.
Try restoring selinux permissions by running
restorecon -R /var/lib/rabbitmq /var/log/rabbitmq
I'm not working with rabbitmq any more, so I don't have it setup any more.
Closing this is fine, since it works for you and I can't reproduce any more.
Sorry I didn't investigate further at the time I had the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.