FS#79104 - [syslog-ng] obsolete keyword "stats_freq" in default syslog-ng.conf + missing dep on "requests"

Attached to Project: Arch Linux
Opened by Bernd Amend (ptb) - Friday, 14 July 2023, 12:38 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

WARNING: Your configuration file uses an obsoleted keyword, please update your configuration; keyword='stats_freq', change='Use the stats() block. E.g. stats(freq(1));', location='/etc/syslog-ng/syslog-ng.conf:8:3'

While testing 4.2.0-1 I noticed that I was unable to start it, since python-requests is required:
[2023-07-14T14:23:08.093225] python: private virtualenv is not initialized, use the `syslog-ng-update-virtualenv' script to initialize it or make sure all required Python dependencies are available in the system Python installation;>
[2023-07-14T14:23:08.114800] Error evaluating global Python block; exception='ModuleNotFoundError: No module named \'requests\''
Traceback (most recent call last):
File "/etc/syslog-ng/syslog-ng.conf{python-global-code:25}", line 3, in <module>
import syslogng.modules.hypr
File "/usr/lib/syslog-ng/python/syslogng/modules/hypr/__init__.py", line 48, in <module>
import requests
ModuleNotFoundError: No module named 'requests'
Error parsing python, Error processing global python block in /usr/lib/syslog-ng/python/syslogng/modules/hypr/scl/hypr.conf:25:1-25:7:
20 # OpenSSL libraries as published by the OpenSSL project. See the file
21 # COPYING for details.
22 #
23 #############################################################################
24
25----> python {
25----> ^^^^^^
26
27 import syslogng.modules.hypr
28
29 syslogng.modules.hypr.register_hypr_config_generator()
30
Included from /usr/share/syslog-ng/include/scl/python/python-modules.conf:25:1-25:1:
Included from /etc/syslog-ng/scl.conf:31:1-31:1:
26 #
27
28 @module appmodel
29
30 @include 'scl/*/*.conf'
31---->
31----> ^
32 @define java-module-dir "`module-install-dir`/java-modules"
Included from /etc/syslog-ng/syslog-ng.conf:3:1-3:1:
1 @version: 4.2
2 @include "scl.conf"
3-----> #
3-----> ^
4 # /etc/syslog-ng/syslog-ng.conf
5 #
6
7 options {
8 stats_freq (0);


Additional info:
* package version(s): 4.1.1-1 and 4.2.0-1
* config and/or log files etc. /etc/syslog-ng/syslog-ng.conf
* link to upstream bug report, if any

Steps to reproduce:
pacman -S syslog-ng
systemctl start syslog-ng@default.service.
journalctl -xeu syslog-ng@default.service
# or
systemctl status syslog-ng@default.service
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:18 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/syslog-ng/issues/1
Comment by Toolybird (Toolybird) - Tuesday, 25 July 2023, 20:49 GMT
Dupe  FS#79199 
Comment by Neil Darlow (neildarlow) - Monday, 23 October 2023, 12:26 GMT
I believe this is caused by the removal of the minimal /etc/syslog-ng/scl.conf file in version 4.4.0-1 and later.

The parser falls-back to reading /usr/share/syslog-ng/include/scl.conf which is more comprehensive and has a dependency on Python which isn't a mandatory dependency.

For now, I've commented-out @include "scl.conf" in /etc/syslog-ng/syslog-ng.conf which caused syslog-ng to fail to start on my ArchlinuxArm install.

Loading...