httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Bannert <aa...@clove.org>
Subject Re: mod_unique_id failure mode
Date Thu, 21 Feb 2002 15:06:22 GMT
On Thu, Feb 21, 2002 at 01:03:00AM -0800, Manoj Kasichainula wrote:
> apache.org DNS was down today; it's back up now. But when DNS was back
> up, we found that the web server was down, and saw this in the error
> log:
> 
> [Thu Feb 21 00:00:03 2002] [alert] (22007)No address associated with hostname: mod_unique_id:
unable to find IPv4 address of "daedalus.apache.org"
> Configuration Failed
> 
> Should mod_unique_id's failure have prevented the server from parsing
> the configuration and restarting? I can see an argument both ways for
> this. I guess it depends on whether you think it's more important to
> keep the server running, or to be sure that all the features are
> working if the server does (re)start.

This is just because it was restarted at midnight, right? I would think
that it's ok to fail at configuration time due to DNS failures, but
I also think that DNS failures should _never_ halt a working server
(if there is a choice).

-aaron

Mime
View raw message