On 1 August 2012 23:30, Joseph Acquisto <user-8f41a3273532@xymon.invalid> wrote:
I can see tcpdump tell me the source is still the original for the new
server. ??
Try running the xymonnet command from the command-line with the
"--no-update" switch, perhaps specifying a stripped-down hosts.cfg with
only one host and test that is failing. For example:
sudo -u xymon xymoncmd
echo "10.1.1.1 name-of-host # ssh" $HOSTSCFG > /tmp/hosts.cfg
HOSTSCFG=/tmp/hosts.cfg xymonnet --report --noping \
--no-update --source-ip=10.2.2.2
Never saw this before. Interesting. I presume the first ip should be that
of the xymon host?
No, the target host.
The sudo part did not work for me. Used su.
OK
No "bind". Did find that xymonnet was not found, had to specify the full
path to it.
Still, no bind. But, lots of open "errors". File not found at
/home/xymon/server/tmp/
Perhaps after doing "su" to the xymon user, you need to run "xymoncmd"
before running the commands. That's why xymonnet wasn't found.
J