NethServer Version: 7.9
Module: updated april 27th, 2023
Hi,
not a big thing but I was giving systemctl a look and I saw some services failed to start. Something I need to take care of please?
Thanks
● rc-local.service loaded failed failed /etc/rc.d/rc.local Compatibility
● suricata.service loaded failed failed Suricata Intrusion Detection Service
● systemd-modules-load.service loaded failed failed Load Kernel Modules
Is it possible that you enabled the following?
Do you use IPS/suricata? Maybe it wasn’t fully removed?
Did you use wireguard or virtualbox? Let’s check if there are modules:
ls -l /usr/lib/modules-load.d/
The only thing in rc.local is the ‘add route …’ with the default route for eth0. This was automatically done at install time. No tinkering afterwards.
I installed it (Curious) a while back. Never used it tho and never tinkered with it. Will try to remove it.
Nothing in there, but I do have the dummy module loaded and functioning in /etc/sysconfig/modules/
No Wireguard or virtualbox, docker yes.
Thanks, again. No priority, only when time and fun permits.
Did you install the NethServer on a CentOS 7 image, like on a VPS? The image could have “special” services enabled.
You may check the service status to maybe get more info about the failed service:
systemctl status rc-local systemd-modules-load -l
If you’re really sure that you don’t need a service you could disable it:
systemctl disable <service>
Hmm, no mentioning of any specific module.
systemctl status rc-local systemd-modules-load -l
● rc-local.service - /etc/rc.d/rc.local Compatibility
Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2023-04-11 23:12:28 CEST; 2 weeks 1 days ago
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2023-04-11 23:12:36 CEST; 2 weeks 1 days ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Main PID: 3699 (code=exited, status=1/FAILURE)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
You may restart the services to get current log entries.
[root@srv01 ~]# systemctl restart systemd-modules-load
Job for systemd-modules-load.service failed because the control process exited with error code. See “systemctl status systemd-modules-load.service” and “journalctl -xe” for details.
[root@srv01 ~]# systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2023-04-27 19:34:44 CEST; 6s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 26712 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 26712 (code=exited, status=1/FAILURE)
Apr 27 19:34:44 myserver.com systemd[1]: Starting Load Kernel Modules…
Apr 27 19:34:44 myserver.com systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Apr 27 19:34:44 myserver.com systemd[1]: Failed to start Load Kernel Modules.
Apr 27 19:34:44 myserver.com systemd[1]: Unit systemd-modules-load.service entered failed state.
Apr 27 19:34:44 myserver.com systemd[1]: systemd-modules-load.service failed.
[root@srv01 ~]# systemctl restart suricata.service
[root@srv01 ~]# systemctl status suricata.service
● suricata.service - Suricata Intrusion Detection Service
Loaded: loaded (/usr/lib/systemd/system/suricata.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2023-04-27 19:36:15 CEST; 8s ago
Docs: man:suricata(1)
Process: 26959 ExecStartPre=/bin/rm -f /var/run/suricata.pid (code=exited, status=0/SUCCESS)
Main PID: 26961 (Suricata-Main)
Tasks: 12
Memory: 352.5M
CGroup: /system.slice/suricata.service
└─26961 /sbin/suricata -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid -q 0 -q 1 -q 2 -q 3 -q 4 -q 5 --user suricata
Apr 27 19:36:15 myserver.com systemd[1]: Starting Suricata Intrusion Detection Service…
Apr 27 19:36:15 myserver.com systemd[1]: Started Suricata Intrusion Detection Service.
Apr 27 19:36:15 myserver.com suricata[26961]: 27/4/2023 – 19:36:15 - - This is Suricata version 5.0.9 RELEASE running in SYSTEM mode
Apr 27 19:36:15 myserver.com suricata[26961]: 27/4/2023 – 19:36:15 - - all 6 packet processing threads, 4 management threads initialized, engine started.
Apr 27 19:36:15 myserver.com suricata[26961]: 27/4/2023 – 19:36:15 - - rule reload starting
Maybe there’s more info about the failed services in /var/log/messages?