Syslog fails to start syslog-ng.service when using an external Syslog Server
Description
Problem/Justification
Impact
Activity

Bug Clerk October 30, 2023 at 2:04 PM
23.10.0.1 PR: https://github.com/truenas/middleware/pull/12417

Automation for Jira October 27, 2023 at 8:34 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Andrew Walker October 27, 2023 at 8:04 PM
Sorry to hear that. Fix is fairly trivial if you want to validate for yourself. C.f. attached pull request.

Bug Clerk October 27, 2023 at 8:04 PM
23.10.1 PR: https://github.com/truenas/middleware/pull/12403

Automation for Jira October 27, 2023 at 4:24 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Details
Details
Assignee

Reporter

After doing an in place upgrade from TrueNAS-SCALE-22.12.3.3 to TrueNAS-SCALE-23.10.0 I noticed the logs stopped sending to my logging server. When I tried manually starting syslog-ng this was the error I was getting:
Removing the logging server from the advanced settings allows syslog-ng to work properly but of course without sending logs anymore.