Solved

Error message in /var/log/syslog, what does it mean and does it require any action

Posted on 2008-10-18
4
264 Views
Last Modified: 2013-12-16
The error message in /var/log/syslog is: "modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.4.27-2-386/modules.dep".

It sounds like a warning message, but what exactly does it mean and does it require action on my part. It appears a few times a day in the logfile on a very busy production server.
0
Comment
Question by:Xyptilon2
  • 2
  • 2
4 Comments
 
LVL 77

Expert Comment

by:arnold
ID: 22749070
This means that the modules.conf file has been updated but the modules.dep (module dependencies have not)  i.e. someone manually modified the modules.conf file.
It is possible that you updated a system module that did not require an update of the module.dep file rare but possible.

Was an update applied, kernel?
If an update was applied and if everything is running ok, you can just execute touch /lib/modules/2.4.27-2-386/modules.dep to avoid seeing this error notice until the next update.
0
 
LVL 13

Author Comment

by:Xyptilon2
ID: 22752927
Non-kernel updates are applied weekly, however kernel updates are less frequent. I'm pretty sure the modules.conf file was not modified manually, at least not by a human being. Perhaps by another update process?

What triggers this error message, it appears at different times in the syslog file.
0
 
LVL 77

Accepted Solution

by:
arnold earned 250 total points
ID: 22753348
When you say that the error appears at different times, do the times correspond to a particular event i.e. a USB device attached?
Try running modprobe -l to see whether the error message appears.
It could very well occur when a specific access is attempted by the kernel that relies on a module.  There is likely an application that is running that every so often probes to see whether there are any changes in attached devices/components.
0
 
LVL 13

Author Comment

by:Xyptilon2
ID: 22755056
modprobe -l prints out a list, but does not trigger the notification on the console, nor  does it log anything into /var/log/syslog

I have 'touched' the file as you suggested and the warning message seems to be gone "for now". I'm going to see how this develops. Thanks for the information.
0

Featured Post

Master Your Team's Linux and Cloud Stack!

The average business loses $13.5M per year to ineffective training (per 1,000 employees). Keep ahead of the competition and combine in-person quality with online cost and flexibility by training with Linux Academy.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The purpose of this article is to demonstrate how we can use conditional statements using Python.
Google Drive is extremely cheap offsite storage, and it's even possible to get extra storage for free for two years.  You can use the free account 15GB, and if you have an Android device..when you install Google Drive for the first time it will give…
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

786 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question