NOPROPYELLOW ignored for one test
I'm having problems with NOPROPYELLOW but only for one test. It seems to completely ignore just that one.
Factors:
- NOPROPYELLOW is successfully being applied to other tests.
- There is no change when this is the only NOPROPYELLOW host or one of many.
- There is no change if I use NOPROPYELLOW:+mycustomtest or NOPROPYELLOW:mycustomtest.
- I am not using --nopropyellow option to xymongen.
- It fails when used on the .default. or the specific host line (or both).
- This test is run on one host which reports on behalf of many others.
- I've verified that the test name is correct using xymondboard. sudo -u xymon xymoncmd xymon localhost "xymondboard test=mycustomtest"
Any suggestions for my next step in debugging? Dave
On 9/18/2018 2:51 PM, Dave "doughnut" Fogarty wrote:
- There is no change if I use NOPROPYELLOW:+mycustomtest or NOPROPYELLOW:mycustomtest.
Sounds to me like it doesn't know about mycustomtest, or doesn't consider it be a valid name, or isn't finding a match with the messages received.
Have you tried a shorter name? Are you doing it all lower-case? Have you tried gratuitously defining mycustomtest in protocols.cfg?
Do things because you should, not just because you can.John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska
Well, "mycustomtest" is actually "chksum" and it's not a network test, so protocols.cfg is not going to help.
Since I can use "chksum" to accurately select it with xymondboard, I am sure I have a valid name to that point. The NOPROPYELLOW is the only place having issues.
D
On Tue, 18 Sep 2018, John Thurston wrote:
On 9/18/2018 2:51 PM, Dave "doughnut" Fogarty wrote:
- There is no change if I use NOPROPYELLOW:+mycustomtest or NOPROPYELLOW:mycustomtest.
Sounds to me like it doesn't know about mycustomtest, or doesn't consider it be a valid name, or isn't finding a match with the messages received.
Have you tried a shorter name? Are you doing it all lower-case? Have you tried gratuitously defining mycustomtest in protocols.cfg?
Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
I understand that it isn't a xymonnet test, and that protocols.cfg shouldn't play into it. My hypothesis was that nopropyellow was taking its list of legit targets from those found in protocols.cfg. Not that xymonnet was somehow in play.
Does it misbehave with nopropred, or only with nopropyellow?
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska
On 9/18/2018 4:51 PM, Dave "doughnut" Fogarty wrote:
Well, "mycustomtest" is actually "chksum" and it's not a network test, so protocols.cfg is not going to help.
Since I can use "chksum" to accurately select it with xymondboard, I am sure I have a valid name to that point. The NOPROPYELLOW is the only place having issues.
participants (2)
-
doughnut＠doughnut.net
-
john.thurston＠alaska.gov