Rsyslog not starting

Support
1

NethServer Version: 7.9.2009
I cannot start rsyslog: it gives me the following error:
" Error
dns.service_action_error
The following command has failed:
system-services/update"

I get the same error when I want to Enable/Start clamd.

Any ideas on how to get around this and what is causing it?
Thank you!

2

what is the output of

systemctl restart rsyslog
systemctl status rsyslog
3

[root@server ~]# systemctl restart rsyslog
Job for rsyslog.service failed because the control process exited with error code. See “systemctl status rsyslog.service” and “journalctl -xe” for details.
[root@server ~]#
[root@server ~]# systemctl status rsyslog
● rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Mon 2021-03-15 07:53:20 EET; 4s ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Process: 8019 ExecStart=/usr/sbin/rsyslogd -n $SYSLOGD_OPTIONS (code=exited, status=1/FAILURE)
Main PID: 8019 (code=exited, status=1/FAILURE)
Mar 15 07:53:20 myserver.com systemd[1]: Failed to start System Logging Service.
Mar 15 07:53:20 myserver.com systemd[1]: Unit rsyslog.service entered failed state.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service failed.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service holdoff time over, scheduling restart.
Mar 15 07:53:20 myserver.com systemd[1]: Stopped System Logging Service.
Mar 15 07:53:20 myserver.com systemd[1]: start request repeated too quickly for rsyslog.service
Mar 15 07:53:20 myserver.com systemd[1]: Failed to start System Logging Service.
Mar 15 07:53:20 myserver.com systemd[1]: Unit rsyslog.service entered failed state.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service failed.
[root@server ~]# journalctl -xe
–
– The result is failed.
Mar 15 07:53:20 myserver.com systemd[1]: Unit rsyslog.service entered failed state.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service failed.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service holdoff time over, scheduling restart.
Mar 15 07:53:20 myserver.com systemd[1]: Stopped System Logging Service.
– Subject: Unit rsyslog.service has finished shutting down
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit rsyslog.service has finished shutting down.
Mar 15 07:53:20 myserver.com systemd[1]: Starting System Logging Service…
– Subject: Unit rsyslog.service has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit rsyslog.service has begun starting up.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service: main process exited, code=exited, status=1/FAILURE
Mar 15 07:53:20 myserver.com systemd[1]: Failed to start System Logging Service.
– Subject: Unit rsyslog.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit rsyslog.service has failed.
–
– The result is failed.
Mar 15 07:53:20 myserver.com systemd[1]: Unit rsyslog.service entered failed state.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service failed.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service holdoff time over, scheduling restart.
Mar 15 07:53:20 myserver.com systemd[1]: Stopped System Logging Service.
– Subject: Unit rsyslog.service has finished shutting down
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit rsyslog.service has finished shutting down.
Mar 15 07:53:20 myserver.com systemd[1]: start request repeated too quickly for rsyslog.service
Mar 15 07:53:20 myserver.com systemd[1]: Failed to start System Logging Service.
– Subject: Unit rsyslog.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit rsyslog.service has failed.
–
– The result is failed.
Mar 15 07:53:20 myserver.com systemd[1]: Unit rsyslog.service entered failed state.
Mar 15 07:53:20 myserver.com systemd[1]: rsyslog.service failed.
Mar 15 07:53:31 myserver.com kernel: Shorewall:net2fw:DROP:IN=enp2s0 OUT= MAC=40:3f:8c:b1:ad:2d:cc:e1:7f:74:48:20:08:00 SRC=185.156.73.19 DST=x.x.x.x LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=53797 PROTO=TCP SPT=59850 DPT=572 WINDOW=1024 RES=0x00 SYN URGP=0
Mar 15 07:53:35 myserver.com kernel: Shorewall:net2fw:DROP:IN=enp2s0 OUT= MAC=40:3f:8c:b1:ad:2d:cc:e1:7f:74:48:20:08:00 SRC=144.76.137.80 DST=x.x.x.x LEN=1500 TOS=0x00 PREC=0x00 TTL=57 ID=6037 DF PROTO=TCP SPT=443 DPT=50849 WINDOW=260 RES=0x00 ACK URGP=0
Mar 15 07:53:35 myserver.com kernel: Shorewall:net2fw:DROP:IN=enp2s0 OUT= MAC=40:3f:8c:b1:ad:2d:cc:e1:7f:74:48:20:08:00 SRC=144.76.137.80 DST=x.x.x.x LEN=1500 TOS=0x00 PREC=0x00 TTL=57 ID=3513 DF PROTO=TCP SPT=443 DPT=50851 WINDOW=260 RES=0x00 ACK URGP=0
Mar 15 07:53:35 myserver.com dnsmasq-dhcp[1469]: DHCPREQUEST(enp3s0) 192.168.6.217 1c:b7:96:41:b6:b8
Mar 15 07:53:35 myserver.com dnsmasq-dhcp[1469]: DHCPACK(enp3s0) 192.168.6.217 1c:b7:96:41:b6:b8 HUAWEI_P30_Pro-c0e84155a0
Mar 15 07:53:37 myserver.com kernel: Shorewall:net2fw:DROP:IN=enp2s0 OUT= MAC=40:3f:8c:b1:ad:2d:cc:e1:7f:74:48:20:08:00 SRC=185.236.11.31 DST=x.x.x.x LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=13028 PROTO=TCP SPT=47542 DPT=6960 WINDOW=1024 RES=0x00 SYN URGP=0
Mar 15 07:53:45 myserver.com kernel: ndpi_net_exit:ns20
Mar 15 07:53:45 myserver.com dnsmasq-dhcp[1469]: DHCPREQUEST(enp3s0) 192.168.6.28 f8:c3:9e:c4:dc:82
Mar 15 07:53:45 myserver.com dnsmasq-dhcp[1469]: DHCPACK(enp3s0) 192.168.6.28 f8:c3:9e:c4:dc:82 HUAWEI_Mate_20_Pro-c1db80
lines 1147-1201/1201 (END)

4

Check in messages log if you have more clues, for now we just know the UI is not broken, we just do not know why rsyslog does not restart

5

In logs I find only this:
Failed to start System Logging Service.

CODE_FILE src/core/job.c
CODE_FUNCTION job_log_status_message
CODE_LINE 774
MESSAGE_ID be02cf6855d2428ba40df7e9d022f03d
PRIORITY 3
RESULT failed
SYSLOG_FACILITY 3
SYSLOG_IDENTIFIER systemd
UNIT rsyslog.service
_BOOT_ID 8f0c633ce5e840d48070426f618ee947
_CAP_EFFECTIVE 1fffffffff
_CMDLINE /usr/lib/systemd/systemd --switched-root --system --deserialize 22
_COMM systemd
_EXE /usr/lib/systemd/systemd
_GID 0
_HOSTNAME myserver.com
_MACHINE_ID 0835150034214041b4f3f4345399ff29
_PID 1
_SOURCE_REALTIME_TIMESTAMP 1615896625673406
_SYSTEMD_CGROUP /
_TRANSPORT journal
_UID 0
__CURSOR s=384c879f20a0466d9e307c504ccd0c17;i=16e2;b=8f0c633ce5e840d48070426f618ee947;m=cff3a449;t=5bda6405df7cc;x=ed6a081bd15f06d2
__MONOTONIC_TIMESTAMP 3488851017
__REALTIME_TIMESTAMP 1615896625674188