Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: syslog-ng config obsoleted config [low proirity] (Read 1930 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

syslog-ng config obsoleted config [low proirity]

package syslog-ng configuration file needs a little update.

Code: [Select]
$ syslog-ng
syslog-ng: Error setting capabilities, capability management disabled; error='Operation not permitted'
[2023-05-04T22:42:20.317839] 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'

this file needs an update.
the warning suggest change " stats_freq (0); " to " stats(freq(0)); ".

Re: syslog-ng config obsoleted config [low proirity]

Reply #1 –
Quote from: suren – on
package syslog-ng configuration file needs a little update.

Code: [Select]
$ syslog-ng
syslog-ng: Error setting capabilities, capability management disabled; error='Operation not permitted'
[2023-05-04T22:42:20.317839] 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'

this file needs an update.
the warning suggest change " stats_freq (0); " to " stats(freq(0)); ".


Thank you for posting this fix. I had the same issue and this solves it.

Re: syslog-ng config obsoleted config [low proirity]

Reply #2 –
Fixed it myself today too. Thanks anyway for posting for others. Also, the first line should be changed to:

@version: 4.0

Otherwise, I'm getting the following warning:

Code: [Select]
WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. etc. etc.

It has been mentioned already on the forum before.

Re: syslog-ng config obsoleted config [low proirity]

Reply #4 –
Thank you!

Re: [SOLVED] syslog-ng config obsoleted config [low proirity]

Reply #5 –
A necro bump in the wild oooooo (sorry!!)

the config uses the same obsolete keyword again.

Re: syslog-ng config obsoleted config [low proirity]

Reply #6 –
Quote from: suren – on
A necro bump in the wild oooooo (sorry!!)

the config uses the same obsolete keyword again.
It appears that this warning has occurred again with the latest update. My config file is now updated per this old issue though and my tty console is still throwing this warning on start up. Does anyone know if there are other changes that need to be made to syslog-ng.conf?

Re: syslog-ng config obsoleted config [low proirity]

Reply #7 –
Quote from: z3rOR0ne – on
Does anyone know if there are other changes that need to be made to syslog-ng.conf?

There's another warning regarding python dependency and venv. But I was going to make another topic.
some optional python dependency should be added, But since arch didn't added them, I don't know it's the right thing. I am clueless about second warning. It asks ro run "syslog-ng-update-virtualenv" as root, But I don't like to install python packages with pip in root.

EDIT: I checked the script and it's safe to run.

Re: syslog-ng config obsoleted config [low proirity]

Reply #8 –
Quote from: suren – on
There's another warning regarding python dependency and venv. But I was going to make another topic.
some optional python dependency should be added, But since arch didn't added them, I don't know it's the right thing. I am clueless about second warning. It asks ro run "syslog-ng-update-virtualenv" as root, But I don't like to install python packages with pip in root.

Yeah, we're on the same page, I also am experiencing the same follow up error and am unsure how to proceed. Running pip generally gives a warning that it should be installed via pacman as well. I don't follow through on the prompt that is displayed:

Code: [Select]
This script will download 3rd party packages from the Python Package Index
(PyPI) using the pip tool.  The installation of these packages will cause
build/postinst scripts to be executed as the brian user on this system.

Press [ENTER] to confirm or Ctrl-C to terminate this script.