minor bug report
list Larry Barber
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
list Scott Pfister
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
list Larry Barber
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
list Thomas R. Brand
It would be nice to be able to fix it in one location; however, the script that generates the data [hobbitclient-linux.sh] runs on the client so it has to be fixed there. Without this change on the client side, the correct information does not get to the server so there isn't anything to 'fix' on the server side. NB: I had to make this change on 7300 clients . . . )
▸
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Larry Barber
Sent: Monday, November 07, 2011 10:13 AM
To: Scott Pfister
Cc: xymon at xymon.com
Subject: Re: [Xymon] 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<mailto: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 days
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<mailto: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
list Henrik Størner
▸
On 07-11-2011 15:19, Larry Barber 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.
Could you send me the output from http://your.xymon.server/xymon-cgi/svcstatus.sh?CLIENT=your.host.name&SECTION=uptime
Sample from the top of "top" on a SuSE box:
Nice, but that's not what Xymon uses. Regards, Henrik
list Henrik Størner
▸
On 07-11-2011 17:06, Brand, Thomas R. wrote:
It would be nice to be able to fix it in one location; however, the script that generates the data [hobbitclient-linux.sh] runs on the client so it has to be fixed there.
[...]
NB: I had to make this change on 7300 clients . . . )
You should have asked here first - I hope you had some way of doing it automatically. Yes, the data is generated by the client script. But that doesn't mean the Xymon server cannot be changed to parse the client-side output correctly. So it is indeed possible to fix it on the Xymon server - it already accomodates the amazingly varied forms of reporting "uptime" that various Unix'es use. Regards, Henrik
list Larry Barber
Here you go: [uptime] 10:47am up 1 day 15:12, 1 user, load average: 0.72, 0.81, 0.88 and from one that has been up for more than 2 days: [uptime] 10:47am up 8 days 10:17, 1 user, load average: 0.05, 0.38, 0.72
▸
Thanks,
Larry Barber
On Mon, Nov 7, 2011 at 10:48 AM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:
On 07-11-2011 15:19, Larry Barber 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.
Could you send me the output from http://your.xymon.server/** xymon-cgi/svcstatus.sh?CLIENT=**your.host.name&SECTION=uptime<http://your.xymon.server/xymon-cgi/svcstatus.sh?CLIENT=your.host.name&SECTION=uptime>;
▸
Sample from the top of "top" on a SuSE box:Nice, but that's not what Xymon uses. Regards, Henrik ______________________________**
Xymon at xymon.com<
list Janford Hof
Hi, new to the community-have posted my question on the portal this morning. But thought I'd see if anyone is able to run more than one bb-hosts file on a Linux server (so that there would be 3 Hobbits for one IP, somehow-I don't see how it could be done, though). We can't go VM as our bandwidth woulnd't handle it. Not sure if management wants separate instances (prod, OR, stage) showing on the Main Page, so I'm researching bb-alias, etc, but I don't understand exactly if it can be done or not. I would supppose that the /etc file would also have to somehow aliased? Any help or a definitive answer, like yes, it can be done or no, it is impractical, would be appreciated. Thanks...
▸
-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner
Sent: Monday, November 07, 2011 11:51 AM
To: xymon at xymon.com
Subject: Re: [Xymon] minor bug report
On 07-11-2011 17:06, Brand, Thomas R. wrote:It would be nice to be able to fix it in one location; however, the script that generates the data [hobbitclient-linux.sh] runs on the client so it has to be fixed there.
[...]
NB: I had to make this change on 7300 clients . . . )
You should have asked here first - I hope you had some way of doing it automatically. Yes, the data is generated by the client script. But that doesn't mean the Xymon server cannot be changed to parse the client-side output correctly. So it is indeed possible to fix it on the Xymon server - it already accomodates the amazingly varied forms of reporting "uptime" that various Unix'es use. Regards, Henrik
Confidentiality Notice: This message (including any attachments) contains privileged and confidential information intended for a specific purpose, and is protected by law. If you are not the intended recipient, please notify the sender and permanently delete this message and any attachments immediately. Any disclosure, dissemination, distribution, or copying of this message, or the taking of any action based on it, is strictly prohibited. You should not retain, copy or use this message or any attachments for any purpose, nor disclose all or any part of the contents to any other person.