nexd: Excessive logging and restarts when device has no internet connection

[russellb]

I have a server running nexd that is currently disconnected from the internet. The logging is much more than necessary.

The behavior I see in a loop:

1. systemd launches nexd
2. some startup logs
3. log message showing a stun error because it couldn't look up the stun server via DNS
4. Four warning logs every 15 seconds showing a DNS lookup failure for the API server
5. A fatal log message that the API DNS lookup has failed
6. nexd exits
7. systemd restarts nexd

I don't think exiting is necessary. I would expect nexd to start up just fine without an internet connection and go into its reconciliation loop. It should log the DNS lookup failures once and then log again when it works again. It should not exit because of this normal condition.

[chirino]

having that state machine might help.