minor bug report

Since this report is parsed on the server (we're using "centralized"
configuration), I don't think the client version makes a difference. The
server is 4.3.3. I'm not sure what the client is, I didn't install it and
there is not an obvious way of determining what version it is. That it
dates from the "Hobbit" days is all I can tell by looking at it.

I could use the perl scriptlet, but I'm monitoring a couple hundred of
these boxes, I would rather fix it in once in a centralized location. Also,
shouldn't this scriptlet go in the "top" section?

Thanks,
Larry Barber


On Mon, Nov 7, 2011 at 8:42 AM, Scott Pfister <user-3f57de7c453d@xymon.invalid> wrote:

You didn't specify what verison of the client you are running on SLES.
This might have been fixed in newer clients.   In any event the problem is
that under SLES, the uptime command shows

‘day’ for uptime > 24 hours && <48 hours; eg, 1 day

‘days’ for uptime > 48 hours; eg 3 day*s*


The server is looking for ‘days’


You can modify  the [uptime] section in
~hobbit/client/bin/hobbitclient-linux.sh and added a perl

Command to change ‘ day ‘ to  ‘ days ‘.


echo "[uptime]"

uptime | perl -pe "s/^(.*) day (.*)/\1 days \2/"


On Mon, Nov 7, 2011 at 9:19 AM, Larry Barber <user-6ef9c2864140@xymon.invalid> wrote:

SuSE systems report uptime as being up "1 day" rather than "1 days" as
other Linuxes do. This seems to cause Xymon to skip the trends graphing
during the period from 24 to 48 hours after a machine has been rebooted. No
big deal, but one of my administrators is rather anally retentive about
that sort of thing,

Sample from the top of "top" on a SuSE box:

top - 08:15:59 up 1 day, 12:40,  0 users,  load average: 0.48, 0.97, 0.84
Tasks:  57 total,   1 running,  56 sleeping,   0 stopped,   0 zombie
Cpu(s):  5.0%us,  1.0%sy,  0.0%ni, 91.8%id,  1.6%wa,  0.1%hi,  0.2%si,  0.3%st


Mem:   2047752k total,  2038620k used,     9132k free,    98792k buffers
Swap:   514696k total,      488k used,   514208k free,   630832k cached


Thanks,
Larry Barber