Rrd removes all non-letters.
From: Jeremy Ruffer [mailto:jeremy.ruffer at gmail.com] Sent: Thursday, December 01, 2016 10:37 AM To: Root, Paul T Cc: xymon Subject: Re: [Xymon] rrd files not getting created.
You have ucf_threads in the test and ucfthreads in the .cfg
HTH
Jeremy
On 1 Dec 2016 15:55, "Root, Paul T" <Paul.Root at centurylink.com<mailto:Paul.Root at centurylink.com>> wrote: Where do I go look to figure out why the rrd file is not getting created?
I have a script that produces output like this with a test name of ‘ucf’:
green
ucf_threads : 14
And that is all I’m sending currently. At this point, it’s a simulated script and then number is between 1-100.
In xymonserver.cfg I have
TEST2RRD=”….,ucf=ncv” NCV_ucf="ucfthreads:GAUGE"
I have two servers. My production, and a test server, with this config, and the test server briefly created the rrd, then I renamed the test (from myg to ucf), c hanged the TEST2RRD and NCV_myg to NCV_ucf.
I’ve restarted xymon completely, and killed the xymond_rrd processes. Nothing shows up in rrd_status.log or rrd_data.log
All the machines are CentOS 6 running xymon 4.3.21. We have successfully got custom graphs working in the past, but no luck at this point. Ultimately, I believe the script will live on a RedHat 7 client. The xymon server will remain CentOS 6 for the forseeable future.
Paul.
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.
Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon 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.