Posts by jsaathof

    This is specifically for the rsyslog RELP module. I am using the same command and environment as the service does. The config is present and correct. And 'systemctl status' does not show enough. If I configure the RELP protocol IT DOES NOT WORK.

    If you read the output I sent carefully you'll see that the error in the config file is because the RELP module cannot be loaded. As it says: "inputs would run but no output whatsoever were created". And this is due to the missing symbols in the module. The rsyslog package, or rather the omrelp.so module is built against other libraries than present on the system.

    I am trying to get the rsyslog working. I have found out the the settings had to be done from the master profile. Now that I have correct settings and a config the service still does not start. This is due to a missing symbol error. The symbol BIO_get_callback_arg comes from crypt/bio/bio_cb.c according to this page: https://linux.die.net/man/3/bio_get_callback_arg

    I am running Libreelec 11.0.3 on x86_64 (Intel NUC7i3BNK)

    This is the error when starting rsyslog by hand:

    Code
    LibreELEC:~/.kodi/addons/service.rsyslog/lib/rsyslog # RSYSLOG_MODDIR=/storage/.kodi/addons/service.rsyslog/lib/rsyslog/ /storage/.k
    odi/addons/service.rsyslog/bin/rsyslogd -n -f /storage/.kodi/userdata/addon_data/service.rsyslog/rsyslog.conf
    rsyslogd: could not load module 'omrelp', errors: trying to load module /storage/.kodi/addons/service.rsyslog/lib/rsyslog/omrelp.so: /storage/.kodi/addons/service.rsyslog/lib/rsyslog/omrelp.so: undefined symbol: BIO_get_callback_arg [v8.2308.0 try https://www.rsyslog.com/e/2066 ]
    rsyslogd: module name 'omrelp' is unknown [v8.2308.0 try https://www.rsyslog.com/e/2209 ]
    rsyslogd: error during parsing file /storage/.kodi/userdata/addon_data/service.rsyslog/rsyslog.conf, on or before line 88: errors occurred in file '/storage/.kodi/userdata/addon_data/service.rsyslog/rsyslog.conf' around line 88 [v8.2308.0 try https://www.rsyslog.com/e/2207 ]
    rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.2308.0 try https://www.rsyslog.com/e/2103 ]
    rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)

    I know this is an old thread but running into the same issue I was saddend to see that the community did not respond at all. Is this open source at it's best?

    The error is about the modules that cannot be found. Looking at the man page (on another machine since the man page is not installed with this addon) I found the issue

    Code
    FILES
           /etc/rsyslog.conf
                  Configuration file for rsyslogd.  See rsyslog.conf(5) for exact information.
           /dev/log
                  The Unix domain socket to from where local syslog messages are read.
           /var/run/rsyslogd.pid
                  The file containing the process id of rsyslogd.
           prefix/lib/rsyslog
                  Default directory for rsyslogd modules. The prefix is specified during compilation 
                  (e.g. /usr/local).

    Since the modules are searched for in /usr/lib/rsyslog I assume the addon was compiled with /usr as prefix. This is incorrect. By the looks of it this cannot be changed. The package should be recompiled with a prefix of /storage/.kodi/addons/service.rsyslog.