Develop Reference

Log4j appender append/store log file to a particular location in Storm cluster environment

Is there any way to change the location of the log file for one particular appender of log4j in a Storm cluster environment?
Suppose I want to keep all logger files of RollingFileInfoappender at /logs/storm directory.

Yes, sure. You can add a log4j2.xml file to your resources-folder and specify the appenders as you like.
For instance:
<RollingFile name="mylog"
fileName="path/to/log.file"
filePattern="path/to/log.file.%i.gz"
append="false"
createOnDemand="true">
<PatternLayout>
<pattern>${patternNoTime}</pattern>
</PatternLayout>
<Policies>
<SizeBasedTriggeringPolicy size="100 MB"/>
</Policies>
<DefaultRolloverStrategy max="4"/>
</RollingFile>

Jsonlayout with complete="True" not writing the file in correct way

I have configured the log4j2 with RollingFile + Jsonlayout and compact="true" attribute and i'm rolling the log file every day.
When i run the application for first time the logs are written correctly. if i restart my application the logger misses to write "," filed between old log messages and new log messages.
How Can i Resolve This.?
<RollingFile name="AuditLog" fileName="D:\Logs\ASSETAudit.log" filePattern="D:\Logs\ASSETAudit-%d-%i{yyyy-MM-dd}.log" ignoreExceptions="false" immediateFlush="true">
<Jsonlayout complete="true" compact ="true" eventEol="true" objectMessageAsJsonObject="false" includeStacktrace="false">
</Jsonlayout>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
Due to this problem i'm unable to parse the json log file using Gson and display in web page

log4j2 periodically cleaning log file

I use log4j2 to log my programs. In my xml configuration file, I have this appender:
<RollingFile name="General" fileName="log/logs/giornale.log" filePattern="log/logs/log-%d{yyyyMMdd}.log">
<PatternLayout>
<Pattern>%d{HH:mm:ss,SSS} [%t] %-5level %logger{-1} - %msg%n</Pattern>
</PatternLayout>
<Policies>
<TimeBasedTriggeringPolicy />
</Policies>
</RollingFile>
What I need is a way to configure it, so that it will delete automatically all files older than n days.
I already found some questions like this, but they don't help, since they don't say how to do it via xml configuration.
To make it short, where exactly am I suppose to indicate parameters like "MaxBackupIndex" in the above snippet? Or which other parameter should I use (and where can I put it)?

Add the following tag under 'RollingFile' tag. Remove the 'policies' tag. You probably don't need it.
<DefaultRolloverStrategy>
<Delete basePath="log/logs" maxDepth="2">
<IfLastModified age="60d" />
</Delete>
</DefaultRolloverStrategy>
With this configuration, logs older than 60 days will be auto-deleted.
Refer to the log4j2 docs for more configuration information.

You can add the DefaultRolloverStrategy to your xml as -
<RollingFile name="General" fileName="log/logs/giornale.log" filePattern="log/logs/log-%d{yyyyMMdd}.log">
<PatternLayout>
<Pattern>%d{HH:mm:ss,SSS} [%t] %-5level %logger{-1} - %msg%n</Pattern>
</PatternLayout>
<Policies>
<TimeBasedTriggeringPolicy />
</Policies>
<DefaultRolloverStrategy max="<specify maximum archive count>"/>
</RollingFile>
As well you can use the combination of time and size based roll over for logs using -
<Policies>
<TimeBasedTriggeringPolicy interval="6" modulate="true"/>
<SizeBasedTriggeringPolicy size="250 MB"/>
</Policies>
..a sample configuration that uses a RollingFileAppender with both the
time and size based triggering policies, will create up to 7 archives
on the same day (1-7) that are stored in a directory based on the
current year and month, and will compress each archive using gzip and
will roll every 6 hours when the hour is divisible by 6

log4j2 RollingFile Error renaming file

I have this appender
<RollingFile name="Application" fileName="/home/user/log/abc.log" filePattern="/var/log/mylog/abc-%d{yyy-MM-dd}-%i.log.gz">
<PatternLayout>
<Pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} abc %-10level %class{36} %L %M - %msg%xEx%n</Pattern>
</PatternLayout>
<Policies>
<TimeBasedTriggeringPolicy />
<SizeBasedTriggeringPolicy size="5 MB" />
</Policies>
<DefaultRolloverStrategy max="9999"/>
</RollingFile>
when the 5 MB are reached and there is no space on /var/log/mylog I get the error "ERROR renaming file from xx to yy If I make space afterwards, the logger does not try again to rename the file. Any ideas how I could solve that?
I use log4j2 2.2

This is not an answer. I don't have enough reputation to make a comment.
SUGGESTION: Log4j2 allows you to automatically delete files older then X days. I've been struggling with this some time ago. The issue has been resolved here:
Log4j2 - Configure RolloverStrategy to delete old log files
Maybe this will be helpful for you.

If you configure a FailoverAppender and put your RollingFileAppender within it then you can configure the FailoverAppender to retry at an interval you configure. In the meantime, the log events can be routed to a secondary appender that can do something else. See http://logging.apache.org/log4j/2.x/manual/appenders.html#FailoverAppender.

try removing ":" here {yyyy-MM-dd HH:mm:ss.SSS}
something like below
<PatternLayout>
<Pattern>%d{yyyy-MM-dd} abc %-10level %class{36} %L %M - %msg%xEx%n</Pattern>
</PatternLayout>

User JVM parameter in log4j2 configuration

I have an RollingFile Appender defined in my log4j2.xml.
<RollingFile name="RollingFile" fileName="/logs/app.log"
filePattern="logs/$${date:yyyy-MM}/app-%d{MM-dd-yyyy}-%i.log.gz">
<PatternLayout>
<Pattern>%d{HH:mm:ss.SSS} - %-5p - %m - [%l]%n</Pattern>
</PatternLayout>
<Policies>
<TimeBasedTriggeringPolicy />
<SizeBasedTriggeringPolicy size="10 MB" />
</Policies>
<DefaultRolloverStrategy max="20" />
</RollingFile>
What I want to do is to pass this parameter to the JVM at startup:
-Dapp_home=/home/admin/server
The documentation is pretty straight forward. And from what I understand it should work like this:
<RollingFile name="RollingFile" fileName="${jvmrunargs:app_home}/logs/app.log"
But it doesn't. I verified that it is working in general by using the absolut path.
In an other application where I use log4j (1.x) it works like this:
log4j.appender.file.File=${app_home}/logs/app.log

Take a look at the System Properties Lookup section of the documentation. If you define a variable as system property using -D like this:
-Dapp_home=/home/admin/server
use
${sys:app_home}
in your Log4j 2 configuration to access it.