Skip to main content
Topic: Syslog-ng errors after updating (Read 1374 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Syslog-ng errors after updating

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.

Quote
* Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
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='afsmtp', error='libesmtp.so.6.2.0: cannot open shared object file: No such file or directory'
Error opening plugin module; module='cloud_auth', error='/usr/lib/syslog-ng/libcloud_auth.so: undefined symbol: _ZTVN10__cxxabiv117__class_type_infoE'
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='afamqp', error='librabbitmq.so.4: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afsnmp', error='libnetsnmp.so.40: cannot open shared object file: No such file or directory'
Error opening plugin module; module='afsql', error='libdbi.so.1: 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='afmongodb', error='libmongoc-1.0.so.0: cannot open shared object file: No such file or directory'                                                                                                                                     [ ok ]
 * Starting syslog-ng ...

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:
Quote
@version: 4.6
@include "scl.conf"
#
# /etc/syslog-ng/syslog-ng.conf
#

options {
  stats(freq(0));
  flush_lines (0);
  time_reopen (10);
  log_fifo_size (10000);
  chain_hostnames (off);
  dns_cache (no);
  use_dns (no);
  use_fqdn (no);
  create_dirs (no);
  keep_hostname (yes);
  perm(0640);
  group("log");
};

source src {
  system();
  internal();
};

destination d_authlog { file("/var/log/auth.log"); };
destination d_syslog { file("/var/log/syslog.log"); };
destination d_cron { file("/var/log/crond.log"); };
destination d_daemon { file("/var/log/daemon.log"); };
destination d_kernel { file("/var/log/kernel.log"); };
destination d_lpr { file("/var/log/lpr.log"); };
destination d_user { file("/var/log/user.log"); };
destination d_uucp { file("/var/log/uucp.log"); };
destination d_mail { file("/var/log/mail.log"); };
destination d_news { file("/var/log/news.log"); };
destination d_ppp { file("/var/log/ppp.log"); };
destination d_debug { file("/var/log/debug.log"); };
destination d_messages { file("/var/log/messages.log"); };
destination d_errors { file("/var/log/errors.log"); };
destination d_everything { file("/var/log/everything.log"); };
destination d_iptables { file("/var/log/iptables.log"); };
destination d_acpid { file("/var/log/acpid.log"); };
destination d_console { usertty("root"); };

# Log everything to tty12
destination console_all { file("/dev/tty12"); };

filter f_auth { facility(auth); };
filter f_authpriv { facility(auth, authpriv); };
filter f_syslog { program(syslog-ng); };
filter f_cron { facility(cron); };
filter f_daemon { facility(daemon); };
filter f_kernel { facility(kern) and not filter(f_iptables); };
filter f_lpr { facility(lpr); };
filter f_mail { facility(mail); };
filter f_news { facility(news); };
filter f_user { facility(user); };
filter f_uucp { facility(uucp); };
filter f_ppp { facility(local2); };
filter f_debug { not facility(auth, authpriv, news, mail); };
filter f_messages { level(info..warn) and not facility(auth, authpriv, mail, news, cron) and not program(syslog-ng) and not filter(f_iptables); };
filter f_everything { level(debug..emerg) and not facility(auth, authpriv); };
filter f_emergency { level(emerg); };
filter f_info { level(info); };
filter f_notice { level(notice); };
filter f_warn { level(warn); };
filter f_crit { level(crit); };
filter f_err { level(err); };
filter f_iptables { match("IN=" value("MESSAGE")) and match("OUT=" value("MESSAGE")); };
filter f_acpid { program("acpid"); };

log { source(src); filter(f_acpid); destination(d_acpid); };
log { source(src); filter(f_authpriv); destination(d_authlog); };
log { source(src); filter(f_syslog); destination(d_syslog); };
log { source(src); filter(f_cron); destination(d_cron); };
log { source(src); filter(f_daemon); destination(d_daemon); };
log { source(src); filter(f_kernel); destination(d_kernel); };
log { source(src); filter(f_lpr); destination(d_lpr); };
log { source(src); filter(f_mail); destination(d_mail); };
log { source(src); filter(f_news); destination(d_news); };
log { source(src); filter(f_ppp); destination(d_ppp); };
log { source(src); filter(f_user); destination(d_user); };
log { source(src); filter(f_uucp); destination(d_uucp); };
#log { source(src); filter(f_debug); destination(d_debug); };
log { source(src); filter(f_messages); destination(d_messages); };
log { source(src); filter(f_err); destination(d_errors); };
log { source(src); filter(f_emergency); destination(d_console); };
log { source(src); filter(f_everything); destination(d_everything); };
log { source(src); filter(f_iptables); destination(d_iptables); };

# Log everything to tty12
#log { source(src); destination(console_all); };

Does anyone have an idea what causes this and how to fix it?

Re: Syslog-ng errors after updating

Reply #1
Does anyone have an idea what causes this and how to fix it?

What does the output of:

Code: [Select]
pacman -Qi syslog-ng
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: Syslog-ng errors after updating

Reply #2

What does the output of:

Code: [Select]
pacman -Qi syslog-ng

Code: [Select]
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?

Re: Syslog-ng errors after updating

Reply #3
I face the same error
Keep it Simple. Simple is Secure, Simple is Beautiful.

Re: Syslog-ng errors after updating

Reply #4
Syslog-ng has always been a strange thing for me with periodic issues and errors. Installed metalog and never looked back since.

Re: Syslog-ng errors after updating

Reply #5
same here after last update
https://forum.artixlinux.org/index.php/topic,6827.0.html
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: Syslog-ng errors after updating

Reply #6
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:
Code: [Select]
# 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
Code: [Select]
 
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
Keep it Simple. Simple is Secure, Simple is Beautiful.

 

Re: Syslog-ng errors after updating

Reply #8
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
nothing unusual for such(bazzar) type of software development ;)

ps if its old bug, why Artix not using alternatives like metalog?
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)