After updating my system yesterday i got greeted by errors at boot. The system boots fine and i havent found any issues yet. The errors appear after the syslog-ng config file gets checked but syslog-ng itself starts fine afterwards (maybe a little slower then usual). Ive checked the config file but couldnt find anything.
Im using open-rc.
So far ive tried to install any of the packages which seems to have a missing shared library but the error persists.
Syslog-ng.conf:
Does anyone have an idea what causes this and how to fix it?
Name : syslog-ng
Version : 4.6.0-2
Description : Next-generation syslogd with advanced networking and filtering capabilities
Architecture : x86_64
URL : https://www.syslog-ng.com/products/open-source-log-management/
Licenses : GPL2 LGPL2.1
Groups : None
Provides : None
Depends On : awk bash curl glib2 glibc grpc json-c libcap libnet libnsl openssl pcre2 protobuf
Optional Deps : logrotate: for rotating log files
libdbi: for the SQL plugin
librabbitmq-c: for the AMQP plugin
mongo-c-driver: for the MongoDB plugin
libesmtp: for the SMTP plugin
hiredis: for the Redis plugin
libmaxminddb: for the GeoIP2 plugin
net-snmp: for the SNMP plugin
librdkafka: for the Kafka C plugin
python: for Python-based plugins [installed]
python-ply: for debugger CLI
Required By : syslog-ng-openrc
Optional For : None
Conflicts With : eventlog
Replaces : eventlog
Installed Size : 7.55 MiB
Packager : Artoo <[email protected]>
Build Date : Sun 14 Apr 2024 05:10:38 PM CEST
Install Date : Mon 29 Apr 2024 11:12:43 PM CEST
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
They seem to be the optional deps, but how can i disable the check for those?
Syslog-ng has always been a strange thing for me with periodic issues and errors. Installed metalog and never looked back since.
any progress on this, it is 12 days now :-\
I did not notice any effects of this errors so far ( I did not dig deep in logs).
Still, this errors on boot make me feel uneasy.
I can reproduce them in terminal after boot with
syslog-ng -s:
# syslog-ng -s
Error opening plugin module; module='geoip2-plugin', error='libmaxminddb.so.0: cannot open shared object file: No such file or directory'
Error opening plugin module; module='redis', error='libhiredis.so.1.1.0: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afmongodb', error='libmongoc-1.0.so.0: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afamqp', error='librabbitmq.so.4: cannot open shared object file: No such file or directory'
Error opening plugin module; module='kafka', error='librdkafka.so.1: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afsmtp', error='libesmtp.so.6.2.0: cannot open shared object file: No such file or directory'
output of
sudo syslog-ng -V
syslog-ng 4 (4.6.0)
Config version: 4.2
Installer-Version: 4.6.0
Revision:
Compile-Date: Apr 14 2024 15:10:38
Module-Directory: /usr/lib/syslog-ng
Module-Path: /usr/lib/syslog-ng
Include-Path: /usr/share/syslog-ng/include
Error opening plugin module; module='geoip2-plugin', error='libmaxminddb.so.0: cannot open shared object file: No such file or directory'
Error opening plugin module; module='redis', error='libhiredis.so.1.1.0: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afmongodb', error='libmongoc-1.0.so.0: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afamqp', error='librabbitmq.so.4: cannot open shared object file: No such file or directory'
Error opening plugin module; module='kafka', error='librdkafka.so.1: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afsmtp', error='libesmtp.so.6.2.0: cannot open shared object file: No such file or directory'
Available-Modules: metrics-probe,affile,correlation,afstomp,regexp-parser,confgen,examples,csvparser,graphite,basicfuncs,add-contextual-data,mod-python,http,syslogformat,xml,afuser,cryptofuncs,otel,secure-logging,rate-limit-filter,appmodel,stardate,bigquery,afsql,loki,azure-auth-header,kvformat,tfgetent,hook-commands,afsnmp,json-plugin,disk-buffer,system-source,afprog,pseudofile,cef,cloud_auth,afsocket,map-value-pairs,timestamp,linux-kmsg-format,tags-parser
Enable-Debug: off
Enable-GProf: off
Enable-Memtrace: off
Enable-IPv6: on
Enable-Spoof-Source: on
Enable-TCP-Wrapper: off
Enable-Linux-Caps: on
Enable-Systemd: off
I think these "errors" can be safely ignored. Actually these are "Warnings". see https://github.com/syslog-ng/syslog-ng/issues/1248 and commit 8ba71ae (https://github.com/syslog-ng/syslog-ng/pull/1256/commits/8ba71ae626ae78d7b916e200e2a1416e93d29fbb)
nothing unusual for such(bazzar) type of software development ;)
ps if its old bug, why Artix not using alternatives like metalog?
https://gitea.artixlinux.org/packages/metalog
Our community ISOs use metalog.
Do you mean only the two ones: -gtk and -qt ISOs with openrc?
Or mate, xfce, lxqt, lxde, plasma too?