To stay updated on your favorite discussions, please create an account or log in. Then, click the Bookmark icon to subscribe and receive notifications.

CentOS 5 install of f-secure linux security 9.11 -- missing kernel headers?

Valerie
Valerie MyAccount Posts: 5 Security Scout

When I run fsav-config, I get the following error:

 

Your system is not able to compile kernel modules.
Following items are missing: kernel headers,
Install the missing items, then re-run this script
Installation finished.

*** NOTE *** NOTE *** NOTE *** NOTE *** NOTE *** NOTE *** NOTE ***

FSAV kernel driver failed to compile.
Please fix the errors printed above, then run as root:
/opt/f-secure/fsav/bin/fsav-compile-drivers
Without kernel drivers the realtime protection features will not work!
After drivers have been successfully compiled, restart daemons with command:
/etc/init.d/fsma stop ; /etc/init.d/fsma start

*** NOTE *** NOTE *** NOTE *** NOTE *** NOTE *** NOTE *** NOTE ***

Starting some of F-Secure Linux Security modules (/etc/init.d/fsma start)

To configure the product, please run /opt/f-secure/fsav/fsav-config.

If you want to completely disable some of the product modules, please
run /opt/f-secure/fsav/sbin/fschooser.

 

I checked around and saw the recommendation in the pre-installation guide  to issue the command:

 

yum install gcc glibc-devel glibc-headers kernel-devel

 

So I've done that.

 

I see in installation troubleshooting, the recommendation to 

 

You may need to install required kernel modules manualy if you forgot to use Software Installation Mode and
the system is not working properly or in large installations when some hosts do not include development tools
or kernel source.
Make sure that the running kernel version is the same as the version of the kernel sources installed. The
kernel configuration must also be the same. On some distributions, such as older SUSE distributions, you
may need to go to /usr/src/linux and run the following commands before the kernel sources match the
installed kernel: make cloneconfig make modules_prepare

 

But I don't HAVE a /usr/src/linux directory.  I do have /usr/src/kernels, but attempting to execute the above commands there results in

 

sb11:/usr/src/kernels # make cloneconfig
make: *** No rule to make target `cloneconfig'. Stop.
sb11:/usr/src/kernels #

 

I'm feeling at a loss here -- any words of wisdom?

 

 

 

Comments

  • Valerie
    Valerie MyAccount Posts: 5 Security Scout

    Thank you, that was indeed the issue. Yum update made it possible to run  /opt/f-secure/fsav/bin/fsav-compile-drivers, and now I've got full functionality.

This discussion has been closed.

Categories