home server debugging issues

[Josip Rodin]

On Fri, Nov 27, 2009 at 11:30:02AM +0100, Alan DeKok wrote:
> > After re-reading proxy.conf comments, this actually looks logical - there is
> > no kind of a status check that would unmark it as a zombie. revive_interval
> > can resurrect it from the 'dead' state, but not from the zombie state. Also
> > this part of the revive_interval comment is a bit confusing:
> > 
> >         #  As a result, we recommend enabling status checks, and
> >         #  we do NOT recommend using "revive_interval".
> >         #
> >         #  The "revive_interval" is used ONLY if the "status_check"
> >         #  entry below is not "none".  Otherwise, it will not be used,
> >         #  and should be deleted.
> > 
> > So it's supposed to be a crutch only for people who *have* status checks,
> > but not a crutch for those of us who do *not* have status checks.
> 
>   Huh?  That's not what it says.  It says "revive_interval" is ONLY for
> people who have "status_check = none".  i.e. no status checks.

But the sentence says

	The "revive_interval" is used ONLY if the "status_check"   
	entry below is not "none".
	               ~~~

Notice the underlined "not" :) Simple thinko?

> > What is a crutch for this situation? A cron job that keeps doing
> > radmin -e 'set home_server state X Y alive'? :)
> 
>   If you don't have status-checks, then the "revive_interval" should
> apply.  If it's not being applied, that should be fixed.

Nope, it's not, my primary server is still a zombie.

-- 
     2. That which causes joy or happiness.