On Fri, February 12, 2016 1:47 pm, John Thurston wrote:
I'm having difficulty with xymongrep, and it isn't related to 4.3.25
because I see the same behavior on 4.3.22.
If I use the command:
~/server/bin/xymongrep --debug --hosts=./server/etc/hosts.cfg *
I get
7667 2016-02-12 12:37:15.937475 Loading host configuration from
./server/etc/hosts.cfg
7667 2016-02-12 12:37:15.937872 Opening file ./server/etc/hosts.cfg
7667 2016-02-12 12:37:15.939296 Opening file ./server/etc//retired_hosts
7667 2016-02-12 12:37:15.939637 Opening file
./server/etc//external_hosts
I can't get it to kick back anything. I've tried prefixing it with
xymoncmd, using --test-untagged, naming specific tests.
The undocumented --no-down causes it to
12870 2016-02-12 12:44:53.038374 Connect status is 0
12870 2016-02-12 12:44:53.038414 Sent 52 bytes
12870 2016-02-12 12:44:53.044933 Read 8192 bytes
12870 2016-02-12 12:44:53.044985 Read 13829 bytes
12870 2016-02-12 12:44:53.045010 Closing connection
Does xymongrep work for anyone else?
Hi,
It looks like it's successfully reading the config files and/or getting
current data from xymond.
Have you tried escaping the '*'? It's possible your shell is eating it off
the command line.
For the specific tests, remember that this will only work for tests
actually specified in hosts.cfg (and includes).... "xymongrep conn" or
"xymongrep disk" won't work since those tests aren't proscribed in the
config. (For something similar, you can run a xymondboard command by hand
though...)
HTH,
-jc
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska