e.org<mailto:dev@stratos.apache.org>"
mailto:dev@stratos.apache.org>>
Date: Sunday, June 29, 2014 1:45 PM
To: dev mailto:dev@stratos.apache.org>>
Subject: Re: Carbon log flooded causing disk full and reboot
Hi Jeffrey,
A great finding! Did this occur while running Stratos in si
causing disk full and reboot
I have seen a continuous log getting printed in the Message Broker of a Stratos
setup I have (due to no subscribers available for a certain topic). But not in
Stratos instance. For the MB logs (one is an INFO and the other is a WARN), I
modified the log4j.properties
I have seen a continuous log getting printed in the Message Broker of a
Stratos setup I have (due to no subscribers available for a certain topic).
But not in Stratos instance. For the MB logs (one is an INFO and the other
is a WARN), I modified the log4j.properties to change log level of the
relev
We usually use daily rolling file appenders for log files. Did you check
what logs were printed more frequently? Perhaps we should fix the code to
change levels of log messages.
On Sun, Jun 29, 2014 at 1:45 PM, Imesh Gunaratne wrote:
> Hi Jeffrey,
>
> A great finding! Did this occur while runni
Hi Jeffrey,
A great finding! Did this occur while running Stratos in single JVM mode
without having any DEBUG level logs?
Please send these changes to both master and 4.0.0 branches.
Thanks
On Fri, Jun 27, 2014 at 7:52 PM, Jeffrey Nguyen (jeffrngu) <
jeffr...@cisco.com> wrote:
> Hi,
>
> In o
Hi,
In our Stratos deployment, we experienced issue where wso2carbon.log file grew
as much as 13 GB causing disk full and instance reboot and Stratos
inaccessible. We're deploying Stratos using default profile. To fix this
issue, we modified log4j.properties with the changes listed below.
