[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Apache, rotatelogs & chroot environment
From: |
Jan-Henrik Haukeland |
Subject: |
Re: Apache, rotatelogs & chroot environment |
Date: |
Fri, 03 Dec 2004 01:26:35 +0100 |
On Thu, 2004-12-02 at 23:18 +0000, David Fletcher wrote:
> I've been looking at the http.c protocol file in Monit. Would this be a
> good place to put something, or is it wrong to have something Apache
> specific in that file?
It would be a good place for you to put the test in. I think the problem
domain and solution is so specialized that I cannot see this as a
general useful thing to add to monit?
> Should the percentage limit of "bad" state processes
> be hard coded, or can there be a configuration line somewhere?
A way to configure this is of course better but as long as it's a hack,
hard coding has tradition :) BTW I'm not sure how much I would trust the
status output from apache if it is stuck in a log-loop. But don't listen
to me, the best way to find out is just to try it.
> Perhaps just using /server-status/?auto as the page to check could
> automatically indicate that we want to do the extra Apache checks.
>
> if failed host 192.168.1.1 port 80
> protocol HTTP request /server-status/?auto then restart
- Re: Apache, rotatelogs & chroot environment, Marco Ermini, 2004/12/01
- Re: Apache, rotatelogs & chroot environment, David Fletcher, 2004/12/01
- Re: Apache, rotatelogs & chroot environment, David Fletcher, 2004/12/02
- Re: Apache, rotatelogs & chroot environment,
Jan-Henrik Haukeland <=
- Re: Apache, rotatelogs & chroot environment, David Fletcher, 2004/12/03
- Re: Apache, rotatelogs & chroot environment, David Fletcher, 2004/12/06
- Re: Apache, rotatelogs & chroot environment, David Fletcher, 2004/12/07
- Re: Apache, rotatelogs & chroot environment, David Fletcher, 2004/12/09