[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SV: [xymon] Xymon reports excessive memory usage on 1 SLES 11 host
- To: xymon (at) xymon.com
- Subject: Re: SV: [xymon] Xymon reports excessive memory usage on 1 SLES 11 host
- From: Vernon Everett <everett.vernon (at) gmail.com>
- Date: Wed, 15 Dec 2010 11:16:46 +0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Oue8pKvBTWAVBZG+yKCikaKi1M2VBvqAsL4/bcpR3do=; b=ZFh9aZ+6mvryyRZyeNSbQmiJMGxR48vSINtshOvLefCe+teRw+91+GhAw/4A+l+hLr 6v2uVwxsrlS8qz/YhDha9AKyP5/rYd9mHq3V0ehCC/9gK+9k44YbKvT4r/vmE5i6OaK+ 6a8oUUzhF1D2iRXsZtuXB8sVRTWYHa7kLfWoA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=lzBWF9DeGQedEU5n8gD8fuPb02+UKYNf5Hs2Lo+y7BT2tQcTxfgd90NAMx3VX4xKVg MxaLgXO8OpSPdaR1QPC5shEB0uwTqNJvADx9PfRIw3jhjLhFF0ZiI5bJZIOu8tJHk/31 DuOeLfEnqgzNCd0qNBD3Mhz8KEF/+yxAs08w4=
- References: <3BD667CCFBD0D04CA2BC3D57D01B64264CA04A5F38 (at) HORMXB103VM1.onerm.dk> <ie7fmf$ndc$1 (at) voodoo.hswn.dk> <3BD667CCFBD0D04CA2BC3D57D01B64264CA04A5F83 (at) HORMXB103VM1.onerm.dk> <ie8njq$c4e$1 (at) voodoo.hswn.dk> <8D17C43B4F1AC3498DE039AEA93812906C9B50C940 (at) VA3DIAXVS051.RED001.local> <ie8oqi$c4e$2 (at) voodoo.hswn.dk> <8D17C43B4F1AC3498DE039AEA93812906C9B50C942 (at) VA3DIAXVS051.RED001.local>
Not much point in doing memory monitoring on a Solaris sparse zone.
Might as well put a check in the client script to not collect memory info
for a sparse zone with capped memory.
See here for more info.
http://www.xymon.com/archive/2010/02/msg00213.html
Regards
Vernon
On Wed, Dec 15, 2010 at 6:11 AM, Tim McCloskey <tm (at) freedom.com> wrote:
> Henrik,
>
> Thanks for the speedy answer. I had seen this in fun in
> hobbitd/client/$clients.c. You must enjoy porting that part of the project
> each time some OS makes a change :)
>
> Trivia:
> On Solaris 10 zones prtconf can get the installed "Memory size:" But
> anything further (like prtdiag) will fail.
>
> System Configuration: Sun Microsystems i86pc
> Memory size: 32768 Megabytes
> System Peripherals (Software Nodes):
>
> prtconf: devinfo facility not available
>
>
>
> Regards,
>
> Tim
>
>
> ________________________________________
> From: Henrik Størner [henrik (at) hswn.dk]
> Sent: Tuesday, December 14, 2010 1:50 PM
> To: xymon (at) xymon.com
> Subject: Re: SV: [xymon] Xymon reports excessive memory usage on 1 SLES 11
> host
>
> On Tue, 14 Dec 2010 13:42:21 -0800, Tim McCloskey wrote:
>
> > What does the Solaris client use to get this data? vmstat? (free is not
> > a native solaris tool).
>
> Each OS has their own way of reporting memory utilisation - it is
> completely non-standard, and the one part of the Xymon client that
> requires the most code for each new OS!
>
> Specifically for Solaris, Xymon uses prtconf to determine how
> much memory is installed, and vmstat to determine how much is
> being used. "swap -s" was used for determining how much swap was
> being used, but earlier today I committed an update so we will
> now use "swap -l" instead.
>
>
>
> Regards,
> Henrik
>
> To unsubscribe from the xymon list, send an e-mail to
> xymon-unsubscribe (at) xymon.com
>
>
>
>
>
> To unsubscribe from the xymon list, send an e-mail to
> xymon-unsubscribe (at) xymon.com
>
>
>