Comment 2 for bug 1513511

So, current findings:

Stacktrace about "failed_to_start_child,rabbit_mgmt_sup": it's acctualy the expected behaviour after a network split, this is documented at https://github.com/rabbitmq/rabbitmq-management/blob/master/src/rabbit_mgmt_sup_sup.erl#L19
This should not be the source of startup failure.

Records in /var/log/syslog about "node name already occupied epmd-starter-443584618" are also unrelated. They are about incorrent PRNG initialization (ala https://xkcd.com/221/), but also should not have any impact on startup process.

Still searching for real cause of startup failure.