> > Wido, makes sense that log4j and logrotate would conflict. Log4j
> > has its
> > own rotate functionality.
>
Note that a few CS log files are not generated by log4j.
You still need external logrotatation if you don't want them to fill up
your disk.
I had this issue with access.log, for
On 9/5/19 11:13 AM, Daan Hoogland wrote:
> Wido, makes sense that log4j and logrotate would conflict. Log4j has its
> own rotate functionality.
It does indeed :-)
> I didn't understand before but the binary data is always the beginning of
> the file? Is always nulls?
I found this out
Wido, makes sense that log4j and logrotate would conflict. Log4j has its
own rotate functionality.
I didn't understand before but the binary data is always the beginning of
the file? Is always nulls?
Op do 5 sep. 2019 09:18 schreef Wei ZHOU :
> Hi Wido,
>
> I saw this issue in a 4.11.3 platform
Hi Wido,
I saw this issue in a 4.11.3 platform today.
It seems to be caused by file
https://github.com/apache/cloudstack/blob/master/agent/conf/cloudstack-agent.logrotate.in
Maybe the file /etc/logrotate.d/cloudstack-agent is not needed ( in Ubuntu
?).
-Wei
On Thu, 5 Sep 2019 at 08:08, Wido
On 9/3/19 2:55 PM, Daan Hoogland wrote:
> On Tue, Sep 3, 2019 at 2:22 PM Wido den Hollander wrote:
>
>>
>>
>> On 9/3/19 9:57 AM, Daan Hoogland wrote:
>>> Can you find/look at the line before in the log. It is probably the one
>>> containing the hindering data. Or otherwise it *might* be a
