Troubleshooting
Problem
Rebuilding the initial RAM disk (initrd) using kdump on redhat linux with loaded Guardium K-TAP module fails. Error appears like: No module ktap-79390 found for kernel 2.6.32-431.20.5.el6.x86_64, aborting.
Cause
K-TAP is seen as a "third-party" module on redhat linux and therefore is not in the default module path. This causes the building of the initrd with kdump to fail.
Diagnosing The Problem
Example of the problem:
[root@db_server ~]# service kdump restart
Stopping kdump: [ OK ]
Detected change(s) the following file(s):
/etc/kdump.conf
Rebuilding /boot/initrd-2.6.32-431.20.5.el6.x86_64kdump.img
No module ktap-79390 found for kernel 2.6.32-431.20.5.el6.x86_64, aborting.
Failed to run mkdumprd
Starting kdump: [FAILED]
Resolving The Problem
You can configure kdump to ignore the module not in the default path.
Edit the /etc/sysconfig/kdump file and add "--allow-missing"
to MKDUMPRD_ARGS.
For example, if the parameter is set to:
MKDUMPRD_ARGS=""
change it to:
MKDUMPRD_ARGS="--allow-missing"
Example after setting that parameter:
[root@db_server~]# service kdump restart
Stopping kdump: [ OK ]
Detected change(s) the following file(s):
/etc/kdump.conf
Rebuilding /boot/initrd-2.6.32-431.20.5.el6.x86_64kdump.img
WARNING: No module ktap-79390 found for kernel 2.6.32-431.20.5.el6.x86_64,
continuing anyway
Starting kdump: [ OK ]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21978357