That's what I thought. As I said, we are running several daemons and all
are using common code comprising log4j v1. But one of the daemons does get
this exception:
java.io.IOException: Disk quota exceeded
at java.io.FileOutputStream.write(FileOutputStream.java:329)
at
There's the FailoverAppender <
http://logging.apache.org/log4j/2.x/manual/appenders.html#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 wrote:
> We use log4j with
This a quota on the filesystem. Writes are blocked when the total
permitted bytes for the user is exceeded. It looks like log4j2 might help
if an exception is being thrown. I see that one can specify
ignoreException="false".
We currently have log4j (not log4j2). Is there the equivalent or is
That feature is only in Log4j 2.
Ralph
> On Oct 29, 2015, at 1:18 PM, degenaro wrote:
>
> This a quota on the filesystem. Writes are blocked when the total
> permitted bytes for the user is exceeded. It looks like log4j2 might help
> if an exception is being thrown.
Lou,
I don't know if this will help, but it is a daily rolling file appender that
keeps a maximum of 6 log files. Rollover occurs at midnight, and if more that 6
log files exist, then the oldest is deleted.
You still can't tell if the logger fails to write to a file, but if your quota
is
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
I am seeing a similar issue with log4j2, is there any log that
contains the error that log4j was not able to write to file?
On Thu, Oct 29, 2015 at 3:53 PM, Remko Popma wrote:
> What action should the daemon take when its quota is reached?
>
> Sent from my iPhone
>
>> On
That's a log4j-1.2 system property.
Sent from my iPhone
> On 2015/10/30, at 9:22, Priya Ahuja wrote:
>
> The closest I could find was to use -Dlog4j.debug, this will put
> (configuration) errors with appenders on the console.
>
>> On Thu, Oct 29, 2015 at 5:17 PM, Ralph
With Async Loggers you can set an ExceptionHandler. Is that what you mean?
Sent from my iPhone
> On 2015/10/30, at 9:07, Nicholas Duane wrote:
>
> I could have sworn I saw some way to provide a sink for log4j2 (or maybe it
> was log4net) internal events. I just did a quick
It doesn't ring a bell. I'll look again more thoroughly to see if I can find
what I think I saw.
Thanks,
Nick
> Subject: Re: how to detect logger is unable to write to file?
> From: remko.po...@gmail.com
> Date: Fri, 30 Oct 2015 09:30:46 +0900
> To: log4j-user@logging.apache.org
>
> With
I could have sworn I saw some way to provide a sink for log4j2 (or maybe it was
log4net) internal events. I just did a quick search and couldn't find
anything. Is there such a mechanism? If so, couldn't this be a way for you to
at least capture internal errors which are not bubbled up
Did you specify ignoreException=false?
Ralph
> On Oct 29, 2015, at 4:06 PM, Priya Ahuja wrote:
>
> I am seeing a similar issue with log4j2, is there any log that
> contains the error that log4j was not able to write to file?
>
> On Thu, Oct 29, 2015 at 3:53 PM, Remko
The closest I could find was to use -Dlog4j.debug, this will put
(configuration) errors with appenders on the console.
On Thu, Oct 29, 2015 at 5:17 PM, Ralph Goers wrote:
> Did you specify ignoreException=false?
>
> Ralph
>
>> On Oct 29, 2015, at 4:06 PM, Priya Ahuja
13 matches
Mail list logo