Xymon to monitor HP OpenVMS

Resending, seems your mail is only accepting 100kb below.

From: Leus Jr, Jose
Sent: Sunday, November 26, 2017 10:09 AM
To: Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
Cc: David Boyer <user-a6c09f28d9d2@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Xymon to monitor HP OpenVMS

Thanks a lot Jeremy for helping me out on this. Here’s the snapshot of the cpu graph.

    [cid:image004.jpg at 01D3669E.D73A3B60]

I’m looking forward for the integration of other OPENVMS resources to Xymon.
At this time, below are the only resources I was able to monitor.
[cid:image005.jpg at 01D3669E.D73A3B60]

Sincerely,
Leus

From: Jeremy Laidman [mailto:user-71895fb2e44c@xymon.invalid]
Sent: Sunday, November 26, 2017 10:02 AM
To: Leus Jr, Jose <user-b46c364676ee@xymon.invalid<mailto:user-b46c364676ee@xymon.invalid>>
Cc: David Boyer <user-a6c09f28d9d2@xymon.invalid<mailto:user-a6c09f28d9d2@xymon.invalid>>; xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Xymon to monitor HP OpenVMS

Just to close this case, in case it helps others using OpenVMS, it turns out the client was an old BB client, which sent its CPU status message with "Up since <date>" rather than "up: <days> days". The difference is that the Xymon CPU status message parsing code expects "up: " (lower-case "up", colon, space). The script that generates the status message was adjusted, and the RRD file came into existence.

In summary, there were some stale rrdctl files being used by Xymon, causing the original error message in the Apache logs. But the client was also not 100% compatible with Xymon. Both now fixed.

J