[
https://issues.apache.org/jira/browse/LOG4J2-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512292#comment-17512292
]
Piotr Karwasz commented on LOG4J2-3436:
---------------------------------------
[~ragini],
If you read the issue
[LOG4J-3359|https://issues.apache.org/jira/browse/LOG4J2-3359] I linked before,
you'll find out that version 2.17.1 didn't work correctly: that is why all your
syslog messages have a facility of "USER" and level "Notice" (those must be the
default values your server assigns to invalid packets).
A solution to your problem is waiting for review as [PR
#807|https://github.com/apache/logging-log4j2/pull/807]. You can compile the
{{log4j-1.2-api}} module from that branch and check if it solves your problem.
Remark also that the "${hostName}" placeholder you used in 2.17.1 will no
longer work. Log4j 2.17.1 erroneously used Log4j2 variable interpolation
instead of Log4j 1.x variable interpolation. From 2.17.2 the "${...}" will only
resolve to system properties or properties in your "log4j.properties" file.
> Log4j 2 syslogAppender prints localhost.localdomain instead of actual hostname
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-3436
> URL: https://issues.apache.org/jira/browse/LOG4J2-3436
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders, Log4j 1.2 bridge
> Environment: Using log4j 2 bridge API: snapshot version of 2.17.3
> log4j-1.2-api-2.17.3.jar
> Reporter: Ragini Gawande
> Assignee: Piotr Karwasz
> Priority: Blocker
>
> We are trying to use syslogAppender for our logging but in the logs its
> prints localhost.localdomain instead of actual hostname
> <13>Mar 14 22:33:41 *localhost.localdomain* Main[6133] +05:30 2022 572 1
> com.test.common.logging.Test | FINE#com.test.common.logging.Level - Can
> print FINE
> <13>Mar 14 22:33:41 *localhost.localdomain* Main[6133] +05:30 2022 572 1
> com.test.common.logging.Test | INFO#com.test.common.logging.Level - Can
> print Info
>
> Here we are using snapshot version of log4j 2.17.3
> This issue was not seen when using log4j 2.17.1
>
> Additional info:
> JDK 1.8
> -Dlog4j1.compatibility=true
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
