Bug #14413
closedAfter upgrade to 23.05 RELEASE, Syslog-NG won't start
0%
Description
Low priority for me, but thought I'd mention. Cannot start manually, un/reinstalled no difference.
Running service syslog-ng onestart generates a readable error.
@[23.05-RELEASE][root@fw.workgroup]/root: service syslog-ng onestart
Starting syslog_ng.
Error parsing pragma, syntax error, unexpected invalid token, expecting LL_EOL in /usr/local/etc/syslog-ng.conf:3:13-3:14:
1 # This file is automatically generated by pfSense
2 # Do not edit manually !
3-----> @version:4.1.
3-----> ^
4 destination _DEFAULT { file("/HDD/data/var/syslog-ng/default.log"); };
5 log { source(_DEFAULT); destination(_DEFAULT); };
6 source _DEFAULT { internal(); syslog(transport(udp) port(5140) ip(127.0.0.1)); };
Error parsing config, syntax error, unexpected LL_ERROR, expecting end of file in /usr/local/etc/syslog-ng.conf:3:1-3:2:
1 # This file is automatically generated by pfSense
2 # Do not edit manually !
*3-----> version:4.1.
3-----> ^*
4 destination _DEFAULT { file("/HDD/data/var/syslog-ng/default.log"); };
5 log { source(_DEFAULT); destination(_DEFAULT); };
I got it to start by editing /usr/local/etc/syslog-ng.conf and deleting the period at the end of line 3. Service will start then. HOWEVER, I still cannot do a save from the syslog-ng config page w/o seeing the same error. Likely an upstream problem in the prog that generates the "don't edit" config file.
Related issues
Updated by Jim Pingle over 1 year ago
- Project changed from pfSense Plus to pfSense Packages
- Category changed from Logging to syslog-ng
- Status changed from New to Duplicate
- Release Notes deleted (
Default)
Duplicate of #14389
Updated by Jim Pingle over 1 year ago
- Is duplicate of Regression #14389: syslog-ng cannot save config added