logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: how to detect logger is unable to write to file?
Date Thu, 29 Oct 2015 20:32:44 GMT
There's the FailoverAppender <
that gives you a way to automatically switch to a different appender when
the primary one errs.

On 29 October 2015 at 12:21, degenaro <lou.degenaro@gmail.com> 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?
> --
> View this message in context:
> http://apache-logging.6191.n7.nabble.com/how-to-detect-logger-is-unable-to-write-to-file-tp59123.html
> Sent from the Log4j - Users mailing list archive at Nabble.com.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org

Matt Sicker <boards@gmail.com>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message