well, I discovered this morning that rabbitmqctl is one of the root causes of this particular breakage -- among other things, it parses the config files to try and find the rabbit instance it should manage.  Guess what happens when the config files change while rabbitmq is running...

Do your init scripts rely on rabbitmqctl for status and stopping of rabbitmq-server?