Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Syslog Server fails to decode message facilities #35

Open
exaSR opened this issue Jan 28, 2021 · 0 comments · May be fixed by #36
Open

Syslog Server fails to decode message facilities #35

exaSR opened this issue Jan 28, 2021 · 0 comments · May be fixed by #36

Comments

@exaSR
Copy link

exaSR commented Jan 28, 2021

When receiving syslog messages, the message facility is reported wrongly.

RFC 5424

The Priority value is calculated by first multiplying the Facility
number by 8 and then adding the numerical value of the Severity. For
example, a kernel message (Facility=0) with a Severity of Emergency
(Severity=0) would have a Priority value of 0. Also, a "local use 4"
message (Facility=20) with a Severity of Notice (Severity=5) would
have a Priority value of 165.

While the sending part of syslog4j is doing things right, the receiving part is not, and
SyslogUtility fails to properly decode the facilities due to wrong constants in SyslogConstants.

@exaSR exaSR linked a pull request Jan 28, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant