rpm install in a syslog-ng environment

[rkomandu]

Environment info

• NooBaa Version: VERSION
• Platform: Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify

Noobaa 5.17.0-20240921 d/s build

Actual behavior

When we install a noobaa rpm with the default rsyslog enabled in the system, it restarts which is good. However if we have the syslog-ng enabled in the cluster there is no message in the stdout and the syslog-ng is not restarted. I think we need to have this check in the system

[root@rk522-33 ~]# systemctl stop rsyslog

[root@rk522-33 ~]# systemctl disable rsyslog

check syslog-ng and rsyslog 

[root@rk522-33 ~]# systemctl start syslog-ng
<bunch of messages have come into the stdout/stderr or console>

[root@rk522-33 ~]# systemctl status rsyslog
● rsyslog.service - System Logging Service
   Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:rsyslogd(8)
           https://www.rsyslog.com/doc/

Sep 24 09:53:15 rk522-33 systemd[1]: Stopped System Logging Service.
Sep 24 09:53:15 rk522-33 systemd[1]: Starting System Logging Service...
Sep 24 09:53:15 rk522-33 rsyslogd[60234]: [origin software="rsyslogd" swVersion="8.2102.0-15.el8" x-pid="60234" x-info="https://www.rsyslog.com"] start
Sep 24 09:53:15 rk522-33 systemd[1]: Started System Logging Service.
Sep 24 09:53:15 rk522-33 rsyslogd[60234]: imjournal: journal files changed, reloading...  [v8.2102.0-15.el8 try https://www.rsyslog.com/e/0 ]
Sep 24 10:43:01 rk522-33 rsyslogd[60234]: [origin software="rsyslogd" swVersion="8.2102.0-15.el8" x-pid="60234" x-info="https://www.rsyslog.com"] rsyslogd wa>
Sep 25 07:34:01 rk522-33 systemd[1]: Stopping System Logging Service...
Sep 25 07:34:01 rk522-33 rsyslogd[60234]: [origin software="rsyslogd" swVersion="8.2102.0-15.el8" x-pid="60234" x-info="https://www.rsyslog.com"] exiting on >
Sep 25 07:34:01 rk522-33 systemd[1]: rsyslog.service: Succeeded.
Sep 25 07:34:01 rk522-33 systemd[1]: Stopped System Logging Service.


[root@rk522-33 ~]# systemctl status syslog-ng
● syslog-ng.service - System Logger Daemon
   Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2024-09-25 07:34:34 CEST; 49s ago
     Docs: man:syslog-ng(8)
 Main PID: 2810330 (syslog-ng)
    Tasks: 2 (limit: 49038)
   Memory: 4.1M
   CGroup: /system.slice/syslog-ng.service
           └─2810330 /usr/sbin/syslog-ng -F -p /var/run/syslogd.pid

Sep 25 07:34:34 rk522-33 systemd[1]: Starting System Logger Daemon...
Sep 25 07:34:34 rk522-33 systemd[1]: Started System Logger Daemon.

5) Installed the noobaa 5.17.0-20240921 rpm on all the nodes that have the rsyslog and syslog-ng 

[root@rk522-33 ~]# rpm -ivh /root/noobaa-core-5.17.0-20240921.el8.x86_64.rpm  (where syslog-ng is enabled)
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:noobaa-core-5.17.0-20240921.el8  ################################# [100%]
**NOTE: THERE IS NO RESTART OF THE SERVICE HERE (SYSLOG-NG)** 

[root@rk522-31 ~]# rpm -ivh /root/noobaa-core-5.17.0-20240921.el8.x86_64.rpm
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:noobaa-core-5.17.0-20240921.el8  ################################# [100%]
Redirecting to /bin/systemctl restart rsyslog.service

Expected behavior

IMO, based on the underlying service (rsyslog, syslog-ng), it should be restarted. Otherwise it should display that please start your logging service etc.

Steps to reproduce

Posted above

More information - Screenshots / Logs / Other output