On Fri, March 13, 2015 1:25 pm, Josh Luthman wrote:
I assume you mean runclient.sh?
If so I edited start:
$XYMONCLIENTHOME/bin/xymonlaunch
--config=$XYMONCLIENTHOME/etc/clientlaunch.cfg
--log=$XYMONCLIENTHOME/logs/clientlaunch.log
--pidfile=$XYMONCLIENTHOME/logs/clientlaunch.$MACHINEDOTS.pid --debug
But I'm not sure what "xymon call" you're referring to?
logs/clientlaunch.log:
2015-03-13 16:24:03 xymonlaunch starting
2015-03-13 16:24:03 Loading tasklist configuration from
/home/shire/./etc/client
launch.cfg
2016 2015-03-13 16:24:03 Opening file /home/shire/./etc/clientlaunch.cfg
2016 2015-03-13 16:24:03
2016 2015-03-13 16:24:03 Starting tasklist scan
2016 2015-03-13 16:24:03 About to start task client
2017 2015-03-13 16:24:03 client -> Loading environment from
/home/shire/./etc/xy
monclient.cfg area
2017 2015-03-13 16:24:03 Opening file /home/shire/./etc/xymonclient.cfg
2017 2015-03-13 16:24:03 client -> Assigning stdout/stderr to log
'/home/shire/.
/logs/xymonclient.log'
2016 2015-03-13 16:24:08
2016 2015-03-13 16:24:08 Starting tasklist scan
2016 2015-03-13 16:24:08 Task client active with PID 2017
2016 2015-03-13 16:24:12
2016 2015-03-13 16:24:12 Starting tasklist scan
2016 2015-03-13 16:24:17
2016 2015-03-13 16:24:17 Starting tasklist scan
2016 2015-03-13 16:24:22
2016 2015-03-13 16:24:22 Starting tasklist scan
2016 2015-03-13 16:24:27
2016 2015-03-13 16:24:27 Starting tasklist scan
Well, that's good. It means the client task is getting launched properly.
the "xymon call" is actually "$XYMON $XYMSRV..." in what should be
/home/shire/./bin/xymonclient.sh, based on what the output here. You'd
want to change that to "$XYMON --debug $XYMSRV..."
After that, can you run the following?
/home/shire/./bin/xymoncmd --env=/home/shire/./etc/xymonclient.cfg sh -x
/home/shire/./bin/xymonclient.sh
That should give us more indication of where we're failing.
HTH,
-jc