Actions
Regression #14389
closed
syslog-ng cannot save config
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Affected Version:
2.7.0
Affected Plus Version:
23.05
Affected Architecture:
Description
Trying to save the configuration, even with the default values, in syslog-ng results in an error:
The following input errors were detected:
Syslog-ng syntax test failed: 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("/var/syslog-ng/default.log"); }; 5 log { source(_DEFAULT); destination(_DEFAULT); }; 6 source _DEFAULT { internal(); syslog(transport(udp) port(5140) ip(192.168.92.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("/var/syslog-ng/default.log"); }; 5 log { source(_DEFAULT); destination(_DEFAULT); }; 6 source _DEFAULT { internal(); syslog(transport(udp) port(5140) ip(192.168.92.1)); }; syslog-ng documentation: https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-edition contact: GitHub Project: https://github.com/syslog-ng/syslog-ng Chat with the Developers: https://gitter.im/syslog-ng/syslog-ng Mailing List: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Tested:
pfSense-2.7.0.a.20230510.0600
pfSense-23.05.r.20230509.2241
pfSense-pkg-syslog-ng-1.15_13
Related issues
Updated by Danilo Zrenjanin 11 months ago
I couldn't reproduce it on:
23.01-RELEASE (amd64) built on Fri Feb 10 20:06:33 UTC 2023 FreeBSD 14.0-CURRENT
May 20 10:31:50 php-fpm 358 /pkg_edit.php: Configuration Change: admin@172.21.10.154 (Local Database): syslog-ng: Settings saved
I tested saving:
- the default settings
- with minor changes
Both succeeded.
Updated by Jim Pingle 11 months ago
- Has duplicate Bug #14411: syslog-ng cannot start on 23.05 added
Updated by Jim Pingle 11 months ago
- Has duplicate Bug #14413: After upgrade to 23.05 RELEASE, Syslog-NG won't start added
Updated by Jim Pingle 11 months ago
I can reproduce it here on a clean install.
Better format of the error message:
: syslog-ng --syntax-only
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.2.
3-----> ^
4 destination _DEFAULT { file("/var/syslog-ng/default.log"); };
5 log { source(_DEFAULT); destination(_DEFAULT); };
6 source _DEFAULT { internal(); syslog(transport(udp) port(5140) ip(10.34.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.2.
3-----> ^
4 destination _DEFAULT { file("/var/syslog-ng/default.log"); };
5 log { source(_DEFAULT); destination(_DEFAULT); };
6 source _DEFAULT { internal(); syslog(transport(udp) port(5140) ip(10.34.0.1)); };
syslog-ng documentation: https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-edition
contact:
GitHub Project: https://github.com/syslog-ng/syslog-ng
Chat with the Developers: https://gitter.im/syslog-ng/syslog-ng
Mailing List: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Updated by Jim Pingle 11 months ago
- Status changed from In Progress to Feedback
- Target version deleted (
2.7.0) - % Done changed from 0 to 100
- Plus Target Version deleted (
23.09) - Affected Plus Version changed from 22.05 to 23.05
Fixed in pkg version 1.16: https://github.com/pfsense/FreeBSD-ports/commit/d848b6da1957d728a867b9010ed3795d946b68c4
Updated by Danilo Zrenjanin 11 months ago
- Status changed from Feedback to Resolved
Tested the package version 1.16.
Config modifications were successfully saved.
I am marking this ticket resolved.
Actions