logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <apa...@elyograg.org>
Subject Re: how to detect logger is unable to write to file?
Date Thu, 29 Oct 2015 21:40:10 GMT
On 10/29/2015 11:21 AM, degenaro wrote:
> We use log4j with rolling appenders for daemons that run 24x7.  The daemons
> run as a user on linux and the log files are written to a filesystem that
> has a quota.  Normally this works great.  Once in a while (usually due to
> human error) the quota is exceeded.  This, unfortunately, prevents the
> daemons from writing their logs...worst of all silently.  There is no
> indication that anything is wrong!
> So my question is: how do we configure log4j so that when logging (to file)
> fails the daemon can find out and take appropriate action?

Something I would do even if I could find a solution by switching to
log4j2:  Implement a monitor that watches the quotas and sends alerts
when the used space in any quota is nearing capacity.  This is the sort
of general-purpose monitoring that will save you from a lot of headaches.


To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message