calculation of memory and swap
Hi all,
we are using solaris zones. I know, memory and swap is a bit triggy on zones, but I have a case where I think data is correct but the interpretation made by xymon (4.3.7) is wrong. The zone is restricted up to 17 Gb swap and 8.5 Gb memory.
This is was the client collects [memory] 0 0 0 4430008 9320720 4403 39524 0 0 0 0 0 0 0 0 0 4752 113338 6142 1 3 96 [swap] total: 1745856k bytes allocated + 10589520k reserved = 12335376k used, 4441840k available [swaplist] swapfile dev swaplo blocks free /dev/swap 4294967295,4294967295 16 4194288 702832
This is what xymon is presenting as result after interpretation:
Physical -971M 8192M -11% Swap 1646M 2047M 80%
My idea is that values larger than 10 Gb are calculated the wrong way (because all zones using total memory less than 10 Gb are presented correctly). But I cannot find the place to fix this. Any ideas or hints?
Thanks, Rolf
-- Mit freundlichen Gruessen Rolf Schrittenlocher
Lokales Bibliothekssystem Frankfurt Senckenberganlage 31, 60054 Frankfurt Tel: (49) 69 - 798 28908 Fax: (49) 69 798 28817 LBS: lbs-f at mlist.uni-frankfurt.de Persoenlich: schritte at ub.uni-frankfurt.de
On 19 September 2013 17:38, Rolf Schrittenlocher < schritte at ub.uni-frankfurt.de> wrote:
My idea is that values larger than 10 Gb are calculated the wrong way (because all zones using total memory less than 10 Gb are presented correctly). But I cannot find the place to fix this. Any ideas or hints?
Perhaps it's not a special case for >10G, but perhaps it's an overflow at 8G, so that anything larger than that goes negative. I'm guessing 8G (rather than 10G) would be the threshold, as it's a power of two. Are you able to reduce the zone's RAM allocation to a little greater, and then a little less than 8G to see if this is the case? Or do you have examples of correctly displayed values greater than 8G and less that 10G? By 8G, I mean exactly 2^33=8589934592 (or perhaps one less).
J
Upgrading to the 4.3.10 client fixed out oddball negative memory reports, which we had on servers with more than 128G RAM
On Sep 19, 2013, at 9:06 PM, Jeremy Laidman <jlaidman at rebel-it.com.au> wrote:
On 19 September 2013 17:38, Rolf Schrittenlocher <schritte at ub.uni-frankfurt.de> wrote:
My idea is that values larger than 10 Gb are calculated the wrong way (because all zones using total memory less than 10 Gb are presented correctly). But I cannot find the place to fix this. Any ideas or hints?
Perhaps it's not a special case for >10G, but perhaps it's an overflow at 8G, so that anything larger than that goes negative. I'm guessing 8G (rather than 10G) would be the threshold, as it's a power of two. Are you able to reduce the zone's RAM allocation to a little greater, and then a little less than 8G to see if this is the case? Or do you have examples of correctly displayed values greater than 8G and less that 10G? By 8G, I mean exactly 2^33=8589934592 (or perhaps one less).
J
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Hi Betsy and Jeremy,
no, I don't have an example for the test you asked for, Jeremy. We'll follow Betsy's hint and upgrade to 4.3.10
thank you for helping, Rolf
Upgrading to the 4.3.10 client fixed out oddball negative memory reports, which we had on servers with more than 128G RAM
On Sep 19, 2013, at 9:06 PM, Jeremy Laidman <jlaidman at rebel-it.com.au <mailto:jlaidman at rebel-it.com.au>> wrote:
On 19 September 2013 17:38, Rolf Schrittenlocher <schritte at ub.uni-frankfurt.de <mailto:schritte at ub.uni-frankfurt.de>> wrote:
My idea is that values larger than 10 Gb are calculated the wrong way (because all zones using total memory less than 10 Gb are presented correctly). But I cannot find the place to fix this. Any ideas or hints?Perhaps it's not a special case for >10G, but perhaps it's an overflow at 8G, so that anything larger than that goes negative. I'm guessing 8G (rather than 10G) would be the threshold, as it's a power of two. Are you able to reduce the zone's RAM allocation to a little greater, and then a little less than 8G to see if this is the case? Or do you have examples of correctly displayed values greater than 8G and less that 10G? By 8G, I mean exactly 2^33=8589934592 (or perhaps one less).
J
Xymon mailing list Xymon at xymon.com <mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon
-- Mit freundlichen Gruessen Rolf Schrittenlocher
Lokales Bibliothekssystem Frankfurt Senckenberganlage 31, 60054 Frankfurt Tel: (49) 69 - 798 28908 Fax: (49) 69 798 28817 LBS: lbs-f at mlist.uni-frankfurt.de Persoenlich: schritte at ub.uni-frankfurt.de
Hi all,
seems I don't understand xymoncmd correctly. Could anyone please provide an example how to do an ldap test with xymoncmd?
kind regards Rolf
ldap is loaded: xymoncmd xymonnet --version 2013-09-25 09:29:39 Using default environment file /opt/hebis/xymon-4.3.7/server/etc/xymonserver.cfg xymonnet version 4.3.7 SSL library : OpenSSL 0.9.8p 16 Nov 2010 LDAP library: OpenLDAP 20416
-- Mit freundlichen Gruessen Rolf Schrittenlocher
Lokales Bibliothekssystem Frankfurt Senckenberganlage 31, 60054 Frankfurt Tel: (49) 69 - 798 28908 Fax: (49) 69 798 28817 LBS:lbs-f at mlist.uni-frankfurt.de Persoenlich:schritte at ub.uni-frankfurt.de
participants (3)
-
betsy.schwartz＠gmail.com
-
jlaidman＠rebel-it.com.au
-
schritte＠ub.uni-frankfurt.de