You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Martin Schröder (JIRA)" <ji...@apache.org> on 2017/11/30 10:16:00 UTC
[jira] [Updated] (LOG4J2-2084) appname gets pid attached when
logging with syslog appender after upgrade from 2.8.2 to 2.10.0
[ https://issues.apache.org/jira/browse/LOG4J2-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Schröder updated LOG4J2-2084:
------------------------------------
Summary: appname gets pid attached when logging with syslog appender after upgrade from 2.8.2 to 2.10.0 (was: appname gets pid attached when logging with syslog appender after upgrade from 2.8.2 to 2.9.1)
> appname gets pid attached when logging with syslog appender after upgrade from 2.8.2 to 2.10.0
> ----------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2084
> URL: https://issues.apache.org/jira/browse/LOG4J2-2084
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.10.0
> Environment: Sender: Java 8, Debian 7.11, rsyslogd 7.6.3
> Syslog server: Ubuntu 14.0, rsyslogd 8.23.0
> Reporter: Martin Schröder
> Labels: regression, syslogappender
> Attachments: log4j2.xml
>
>
> We use the attached configuration in projects with Java8 on Debian 7.11. After upgrading from 2.8.2 to 2.9.1, we notice that the appName field has a number (probably the pid of the process) attached in brackets, i.e. instead of "foo" it's "foo[21063]". Since we have configured rsyslog on the receiving side to create directories with the appName field, this creates a new log directory every time the application is restarted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)