Looks like the system program reporting memory back to xymon is not providing it in the format that xymon is expecting. And so the Total memory is running into the percentage (23%), so xymon is parsing it wrong.

That would be in the xymonclient script (xymonclient-hpux.sh?) I don't remember enough HP-UX to even know what reports memory. Does it use 'vmstat'?

Oh, so I found an old Solaris xymon client package with the xymonclient-hp-ux.sh, it doesn't look like what your output is:

echo "[memory]"

$XYMONHOME/bin/hpux-meminfo

From Earl Flack http://lists.xymon.com/archive/2010-December/030100.html

FREE=/usr/sbin/swapinfo |grep ^memory |awk {'print $4'} FREEREPORT=echo $FREE / 1024 |/usr/bin/bc TOTAL=/usr/sbin/swapinfo |grep ^memory |awk {'print $2'} TOTALREPORT=echo $TOTAL / 1024 |/usr/bin/bc echo Total:$TOTALREPORT echo Free:$FREEREPORT echo "[swapinfo]" /usr/sbin/swapinfo -tm

But that might just be a formatting issue.

'Swapinfo' might be the command we are looking for.

What do you have in the script?

From: Xymon <xymon-bounces at xymon.com> On Behalf Of Hershman, Rick Sent: Thursday, October 04, 2018 11:41 AM To: xymon at xymon.com Cc: gjohnson at trantor.org Subject: Re: [Xymon] [hobbit] Out of range memory report HP-UX MEM is RED and reporting incorrectly,

I receive RED on MEM column, after just getting a "NEW-ancient" client HP-UX server loaded into xymon: I also as noted below>> have the threshold set to 101 >Like so: MEMPHYS 100 101 in file = analysis.cfg (and xymon still shows RED)

Can I : A. Make it green or B. Just make it vanish. Thanks- Rick.Hershman at Centurylink.com<mailto:Rick.Hershman at Centurylink.com>

This fellow below: (Galen Johnson gjohnson at trantor.org <mailto:xymon%40xymon.com?Subject=Re%3A%20%5Bhobbit%5D%20Out%20of%20range%20memory%20report&In-Reply-To=%3C44D1F913.9090706%40trantor.org%3E> ) says: I've usually just gone in and tweaked the scripts when that would happen. How can I "go in and tweaked the scripts" ?

How can I make the MEM no longer report RED via > tweaked the scripts ? how exactly does this get done ? Or any other way to make the memory column on Xymon GUI from RED be GREEN ?

PROBLEM I encounter:

[cid:image003.png at 01D45BD9.7EADB090]

Thu Oct 4 17:26:07 GMT 2018 - Memory CRITICAL Memory Used Total Percentage [red]Physical 18446744073709537464M 2040M18446744073709550923% [green]Swap 52468M 65245M 80%

Xymon forum encountered this in the past:

http://lists.xymon.com/archive/2006-August/008347.html

On Thu, Aug 03, 2006 at 11:37:02AM +0100, Colin Spargo wrote:

I got this in the "memory" column for a Solaris 8 host this morning, which caused it to go red (even though i have the threshold set to 101).

Thu Aug 3 09:11:17 BST 2006 - Memory CRITICAL Memory Used Total Percentage red Physical 4294955003M 131072M 4294967287% green Swap 40973M 144024M 28%

That physical memory calculation is obviously incorrect!

It sounds to me like vmstat is reporting the total memory as "real + disk"...which I believe is what the 4th column shows (I don't have a solaris server where I'm currently at to confirm). So, while hobbit keys on the physical (real) memory to determine the memory, it's keying on a computed value to do the differential. I've seen this under HPUX and linux on occasion for the memory tests for BB. I've usually just gone in and tweaked the scripts when that would happen.

=G=

Rick.Hershman at Centurylink.com<mailto:Rick.Hershman at Centurylink.com> Cell = 1 720 988 7452 Home = 1 321 802 3619

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.