The script itself doesn't have SSH commands to my knowledge. The one SSH
command is in hosts.cfg and that's just to pull named.stats.
Correct. The script takes the command as specified, replaces the the
substitutable parameters by their values, executes the resulting command
and catches the resulting standard output.
I did test this in (Xymon user)'s shell, it worked as expected. I could
also grab the named.stats file.
So, manually it works but when invoked from the script it does not? Are
there any messages in the logfile?
Regards,
Wim Nelis.
On Wed, Sep 21, 2016 at 4:41 PM, William Pechter <user-01a56b68d7d6@xymon.invalid>
wrote:
Josh Luthman wrote:
https://wiki.xymonton.org/doku.php/monitors:retds
Has anyone installed this recently? I went through the instructions but
I think my first snag is the lack of SSH to grab the named.stats file.
Watching tcpdump on the client I get no 22/tcp traffic from the Xymon
server.
My host entry (IP host and user changed):
192.168.1.100 foobar.imaginenetworksllc.com <
http://foobar.imaginenetworksllc.com>; # dns RNAMED:"cmd(ssh -T username@%{H}
2>/dev/null),statsfile(named.stats)" TRENDS:*,bindstats
I do have an SSH trust but it's not getting that far, Xymon isn't
attempting to SSH at all.
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
First thought is to try to do the ssh command in the scripts manually as
the Xymon user and see if it's wanting to update the known_hosts or
waiting for someone to accept the remote key... etc.
I know it's kind of an obvious thing and you might have checked it but
I've seen fun with ssh scripts like that which timeout waiting for user
intervention.
After a manual run it's good to go for the rest of the life or until
modified.
Bill
--
Digital had it then. Don't you wish you could buy it now!
pechter-at-gmail.com http://xkcd.com/705/
*The NLR disclaimer is valid for NLR e-mail messages.*
This message is only meant for providing information. Nothing in this
e-mail message amounts to a contractual or legal commitment on the part of
the sender.
This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message. Sender accepts
no liability for damage of any kind resulting from the risks inherent in
the electronic transmission of messages.