Icinga
Let Windows service start automatically, but delayed
Can someone please explain the situation where this is supposed to help?
so the network has enough time to get up.
What happens otherwise? What does the agent need the network for? I mean sure, it needs network connectivity to connect to its master/satellite but if that's not working yet, it should still start and retry connecting (or wait for an incoming connection).
There seems to be an issue related on the binding part of Icinga, in case the network is not in-time on a virtual environment.
@carraroj therefore referenced ref/NC/852508
In general it should be fine to have a delayed start, as during that time the network should be already be ready 99% of the time. Based on the mentioned references, there might how ever be an issue in some edge cases, when the network connection itself is not up in time.
By default, Icinga for Windows adds retries in case the service crashes and with the combination of delayed restart, the problem should more or less be by then. I'm not sure if the mentioned case in the referenced issue is resolved by this, but i'm certainly sure it should be.
referenced ref/NC/852508
I've read that internal ticket but unfortunately, it misses information that would help me to understand the issue.
First of all, it mentions that there are errors in the event log but does not contain the actual error messages. So what is the error that it preventing Icinga 2 from starting in that scenario?
Second, it mentions bind_host out of nowhere without additional information how this came to anyone's attention.
One scenario that I could imagine from this occurring was if the bind_host attribute was set to a domain name that can only be resolved using DNS, and if that fails, the ApiListener fails to start. Was something like that the case? I don't see any information that would allow me to confirm that. With the current information provided in this PR, this just claims to fix something without even proving concrete information on what it fixes.