On 9/9/2016 8:37 PM, Foster Patch wrote:
Should I replace this:
CMD xymonnet --report --ping --checkresponse --timelimit=75 --dns-timeout=5
With this
CMD xymonnet --report --ping --checkresponse --dns-timeout=5 --timelimit=75
Or should I add an additional line to what you put in?
You should change your existing line to:
CMD env TASKSLEEP=75 xymonnet --report --ping --checkresponse --dns-timeout=5
That should immediately take effect for you. You can leave the "--timelimit=75" at the end, but you'll get a warning to the error log on each run.
-jc
-----Original Message-----
From: J.C. Cleaver [mailto:cleaver at terabithia.org] Sent: Friday, September 9, 2016 11:30 PM To: Foster Patch <Foster.Patch at accuweather.com> Cc: Xymon Mailing List <xymon at xymon.com> Subject: Re: [Xymon] xymonnet alarm (with patch)
Patch now included.
-jc
On Fri, September 9, 2016 8:11 pm, J.C. Cleaver wrote:
On Thu, September 8, 2016 11:51 am, Foster Patch wrote:
Hello,
I added what you recommended, but the alarm still exists. Here is the tasks.cfg section: [xymonnet] ENVFILE /usr/lib/xymon/server/etc/xymonserver.cfg NEEDS xymond CMD xymonnet --report --ping --checkresponse --dns-timeout=5 --timelimit=75 LOGFILE $XYMONSERVERLOGS/xymonnet.log INTERVAL 1m
The xymonnet alarm now says under Error output: Unknown option –timelimit=75 – try –help
Any suggestions?
Foster
Hi Foster,
Unfortunately, I can confirm that this is a bug in how that option is processed. As a workaround, you can lie to xymonnet about what interval it's been told to run (from xymonlaunch) at with:
CMD env TASKSLEEP=75 xymonnet --report --ping --checkresponse --dns-timeout=5
This should result in what you want.
The following patch should fix it for you, and this will be in the next version.
HTH, -jc