My last servers installed with Debian wheezy or Ubuntu precise has started to show a yellow alarm at libs with message:
*One of /proc/config.gz and /boot/config-3.2.0-4-amd64 was not found, cannot check kernel uptodateness *
However
ls -l /boot/config-3.2.0-4-amd64 -rw-r--r-- 1 root root 129065 Jun 9 15:47 /boot/config-3.2.0-4-amd64
A search at Google shows me several xymon monitor with the same yellow alarm active but I can found references about it.
Any comments will be appreciated.
Regards, Rodolfo Pilas
I saw those messages on my system as well. I just modified the script to ignore them. I think they are created when the kernel is compiled to let the user know what was the kernel was compiled with. There is likely a config-x.y.z-aa-arch for every kernel you have installed. I'd have to look at it again but it might be easy enough to modify it to use "config-uname -r" to have it look for the config of the running kernel. Regardless, I don't think they're useful to monitor.
=G=
From: Xymon [xymon-bounces at xymon.com] on behalf of Rodolfo Pilas [r at pil.as] Sent: Tuesday, July 23, 2013 7:20 PM To: xymon at xymon.com Subject: [Xymon] libs: cannot check kernel uptodateness
My last servers installed with Debian wheezy or Ubuntu precise has started to show a yellow alarm at libs with message:
One of /proc/config.gz and /boot/config-3.2.0-4-amd64 was not found, cannot check kernel uptodateness
However
ls -l /boot/config-3.2.0-4-amd64 -rw-r--r-- 1 root root 129065 Jun 9 15:47 /boot/config-3.2.0-4-amd64
A search at Google shows me several xymon monitor with the same yellow alarm active but I can found references about it.
Any comments will be appreciated.
Regards, Rodolfo Pilas
You are right Galen.
The libs monitor compares /proc/config.gz and with /boot/config-$(uname -r) but the first file do not exist in Debian (ref: http://wiki.debian.org/KernelFAQ#Misc_FAQ )
The compare of running kernel and installed kernel is doing form a previous if condition, then the solution is to remove the find code /proc/config.gz at /usr/lib/hobbit/client/ext/libs
50,61d49
< my $curconfig = "/proc/config.gz";
< my $instconfig = "/boot/config-$current";
<
< if (-e $curconfig and -e $instconfig) {
< system "zdiff -q $curconfig $instconfig > /dev/null";
< if ($? >> 8 != 0) {
< $bb->color_line ('yellow', "Machine should be rebooted, kernel configs $curconfig and $instconfig differ\n\n");
< }
< } else {
< $bb->color_line ('clear', "One of $curconfig and $instconfig was not found, cannot check kernel uptodateness\n\n");
< }
<
Henrik the file /usr/lib/hobbit/client/ext/libs is into the hobbit-plugins debian package http://packages.debian.org/sid/hobbit-plugins
and the libs script starts:
Copyright (C) 2005, 2006, 2007, 2008 Peter Palfrader <peter at palfrader.org>
Porting to hobbit Copyright (C) 2007 Christoph Berg <myon at debian.org>
Copyright (C) 2011 Axel Beckert <abe at debian.org>
Thank you guys!
Rodolfo Pilas http://www.pilas.net @ysidorito
El martes, 23 julio 2013 a las 23:31 , Galen Johnson escribió:
I saw those messages on my system as well. I just modified the script to ignore them. I think they are created when the kernel is compiled to let the user know what was the kernel was compiled with. There is likely a config-x.y.z-aa-arch for every kernel you have installed. I'd have to look at it again but it might be easy enough to modify it to use "config-
uname -r" to have it look for the config of the running kernel. Regardless, I don't think they're useful to monitor.=G=
From: Xymon [xymon-bounces at xymon.com (mailto:xymon-bounces at xymon.com)] on behalf of Rodolfo Pilas [r at pil.as (mailto:r at pil.as)] Sent: Tuesday, July 23, 2013 7:20 PM To: xymon at xymon.com (mailto:xymon at xymon.com) Subject: [Xymon] libs: cannot check kernel uptodateness
My last servers installed with Debian wheezy or Ubuntu precise has started to show a yellow alarm at libs with message:
One of /proc/config.gz and /boot/config-3.2.0-4-amd64 was not found, cannot check kernel uptodateness
However
ls -l /boot/config-3.2.0-4-amd64
-rw-r--r-- 1 root root 129065 Jun 9 15:47 /boot/config-3.2.0-4-amd64A search at Google shows me several xymon monitor with the same yellow alarm active but I can found references about it.
Any comments will be appreciated.
Regards,
Rodolfo Pilas
On 24-07-2013 01:20, Rodolfo Pilas wrote:
My last servers installed with Debian wheezy or Ubuntu precise has started to show a yellow alarm at libs with message:
/One of /proc/config.gz and /boot/config-3.2.0-4-amd64 was not found, cannot check kernel uptodateness
Is this in a "libs" status column ? That one is not a standard Xymon test, I think it comes from one of the Debian add-on checks.
So you really should report it as a Debian bug.
Regards, Henrik
participants (3)
-
Galen.Johnson@sas.com
-
henrik@hswn.dk
-
r@pil.as