[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: monit dying with "hostname did not resolve"

From: Martin Pala
Subject: Re: monit dying with "hostname did not resolve"
Date: Tue, 19 Dec 2006 15:41:07 +0100
User-agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20060627


Monit checks the monitored hostname during startup to make sure that there is no keying mistake in the configuration. In the case that the hostname is not resolvable, monit will refuse to start (because of 'invalid' configuration).

The question is, why your resolver isn't available during monit startup?

Maybe we should change this behavior just to warning ... for example when the user want's to start monit early as almost first service and make it responsible for nameserver startup, then this check may make problems.

What does the other developers think - do you agree with changing the hostname check on startup from showstopper to warning?


Martin Schröder wrote:
I've got an instance of monit 4.5 on debian which should also monitor
a host and which upon system boot fails to start. Its last words are
monit: /etc/monit/monitrc:417: Error: hostname did not resolve ''

Now, the name resolves later, so this seems to be a race condition. Is
there anything I can do to use a name (instead of an ip) which is not
resolvable at the start of monit but later?


To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]