configmgr fails to start the first time it's run, then works fine on all subsequent runs. For physical hardware environments this is an issue exactly once so not that big a deal. However, with the move to self-service cloud environments (e.g. making HPCC available via the Amazon Marketplace) this is more of an issue.
This issue is very easy to reproduce for any version of HPCC within the last couple years using the following steps:
1. Create a new instance in AWS running CentOS 7. (I don't know if it occurs with other OSes, but it also did it with CentOS 6.)
2. Install HPCC.
3. Start configmgr. It will fail.
4. Start configmgr again. It will succeed.
It always fails the first time. It always works fine after that (assuming there isn't some other reason for it to not work.)
I've attached a log file. The first attempt is at the top (time 14:43:46). The second attempt starts about a minute later (time 14:44:45). I don't see an obvious difference between the two though.