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?
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska