Q: What are my options here?
A: As usual, the tradeoff is between functionality and stability:
- Named releases - known stable checkpoints.
- master branch - known stable, but a bit obsolete.
- dev branch - current development. Stable enough, with occasional flukes.
- imperative branch - rock stable, but ages old. Will not get new updates.
Q: How do I choose a stable revision?
A: Look at tags list, any tag containing the word "stable" in it is what you're looking for.
Additionally, if you take a look at the output of git tag -n, it will usually mention the uptime of that particular revision before it was tagged.
Q: Nothing works!
A: In approximately this order:
- Check the configuration.
- Use YAML anchors, they help to keep it consistent.
- Check if the order of configuration entries is the same as in the documentation.
- Make sure you examine the configuration dump (logged at
debuglevel) to see if the configuration you think you provided is the configuration that's actually been read.
- Check the logs. HCC is permissive (will completely stop operating only on unrecoverable errors), and verbose. Logs often contain links to documentation on how to correct a particular problem.
- Enable InfluxDB connector. HCC emits a lot of data, and one picture is better than a thousand words.
- Enable Console (incompatible with running in Docker, but well worth it for troubleshooting). Its instrument cluster might pinpoint problems immediately.
Q: HCC advertises itself on 127.0.1.1, clients can't connect
A: You're likely running Debian or derivative, and this is what is going on.
Remove 127.0.1.1 from /etc/hosts.