Ask Your Question
1

systemd-modules-load.service failed

asked 2016-12-09 02:05:03 -0500

azughe3a gravatar image

updated 2016-12-12 01:40:17 -0500

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 Fri 2016-12-09 09:35:06 CET; 56min left
Condition: start condition failed at Fri 2016-12-09 08:39:03 CET; 2s ago
├─ ConditionDirectoryNotEmpty=|/lib/modules-load.d was not met
├─ ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d was not met
├─ ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d was not met
├─ ConditionDirectoryNotEmpty=|/etc/modules-load.d was not met
├─ ConditionDirectoryNotEmpty=|/run/modules-load.d was not met
├─ ConditionKernelCommandLine=|modules-load was not met
└─ ConditionKernelCommandLine=|rd.modules-load was not met
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Main PID: 200 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

systemctl is-enabled systemd-modules-load
static

What I've done.
I guess this started after the upgrade to fedora 25.
I had oracle virtualbox 5.1 installed.
I've uninstalled all virtualbox packages for now.
I can't figure out why this service is static if virtualbox got removed.

How can I get a clean system again?

Edit: Comment from @bitwiseoperator

Thanks for the response :)

Both directories seem empty, see below:

[root@localhost modules-load.d]# pwd
/etc/modules-load.d
[root@localhost modules-load.d]# ls -la
total 16
drwxr-xr-x. 2 root root 4096 Oct 11 19:21 .
drwxr-xr-x. 172 root root 12288 Dec 12 08:10 ..

[root@localhost modules-load.d]# pwd
/usr/lib/modules-load.d
[root@localhost modules-load.d]# ls -la
total 44
drwxr-xr-x. 2 root root 4096 Dec 9 08:24 .
dr-xr-xr-x. 70 root root 36864 Dec 9 08:14 ..

journalctl from last boot: http://pastebin.com/9J9SNwTx

In the journalctl log I found the line
Dec 12 09:10:29 localhost.localdomain systemd-modules-load[196]: Failed to find module 'nf_conntrack_pptp'
I guess, that's the problematic module.
I found this open bug
https://bugzilla.redhat.com/show_bug....
From my understanding, I need to wait for an PPTP update and should meanwhile ignore the error.

edit retag flag offensive close merge delete

Comments

That service is standard with Fedora systems; as it says, it is the method employed by systemd to load kernel modules. It will be static regardless of whether or not VirtualBox is installed. It may be failing, however, because it is attempting to load a VirtualBox kernel module which no longer exists on your system.

Check out /usr/lib/modules-load.d/ and /etc/modules-load.d/ and see what *.conf files are in there; if you see one for VirtualBox, you could rename it to "whatever.conf.old" and try rebooting and looking for the error to recur.

bitwiseoperator gravatar imagebitwiseoperator ( 2016-12-10 10:52:56 -0500 )edit
1

Also, if you check out your system journal (with journalctl) and search for "Started Load Kernel Modules", you should be able to see an error message of some sort logged shortly thereafter which indicates what the issue is.

bitwiseoperator gravatar imagebitwiseoperator ( 2016-12-10 10:53:33 -0500 )edit

Thanks for your comment, I edited the question because my answer was longer than the allowed character limit.

azughe3a gravatar imageazughe3a ( 2016-12-12 01:42:04 -0500 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2016-12-17 09:00:45 -0500

So actually, I had forgotten that I had encountered this issue myself and resolved it in the process of troubleshooting a different, unrelated issue;

The module is provided by the kernel-core package (whichever version you're using). I booted with a previous kernel, erased the latest kernel, kernel-core, and kernel-headers packages (the ones I was booting with which were exhibiting the symptom you describe), and performed a dnf upgrade operation to reinstall those kernel packages along with all available upgrades. When I rebooted, the error message no longer appeared.

If the issue hasn't been resolved through your regular upgrade operations by this point, give that a try.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-12-09 02:04:13 -0500

Seen: 1,829 times

Last updated: Dec 17 '16