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.
Code
× service.rsyslog.service - System Logging Service
Loaded: loaded (/storage/.config/system.d/service.rsyslog.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2023-09-27 20:18:31 CEST; 12min ago
Docs: http://www.rsyslog.com/doc/
Process: 738 ExecStartPre=/bin/sh /storage/.kodi/addons/service.rsyslog/bin/rsyslog.init (code=exited, status=0/SUCCESS)
Process: 754 ExecStart=/storage/.kodi/addons/service.rsyslog/bin/rsyslogd -n -f /storage/.kodi/userdata/addon_data/service.rsysl
Main PID: 754 (code=exited, status=1/FAILURE)
CPU: 75ms
Sep 27 20:18:31 LibreELEC systemd[1]: service.rsyslog.service: Scheduled restart job, restart counter is at 5.
Sep 27 20:18:31 LibreELEC systemd[1]: Stopped service.rsyslog.service.
Sep 27 20:18:31 LibreELEC systemd[1]: service.rsyslog.service: Start request repeated too quickly.
Sep 27 20:18:31 LibreELEC systemd[1]: service.rsyslog.service: Failed with result 'exit-code'.
Sep 27 20:18:31 LibreELEC systemd[1]: Failed to start service.rsyslog.service.
Display More