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
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
On Fri, Mar 13, 2015 at 4:13 PM, J.C. Cleaver <user-87556346d4af@xymon.invalid>
wrote:
On Fri, March 13, 2015 12:43 pm, Josh Luthman wrote:
I have a new machine running Centos 6.6 that for the life of me I can not
get started. I compiled 4.3.17 and 4.3.18 to see if it was a bug. With
both versions I get the same results.
I've got it narrowed down to the point where is definitely a
machine/client
problem. With tcpdump I've shown that there are no packets being
generated
after the (Xymon) client is started. I can ping the server and create a
handshake (telnet) to 1984 on the server.
ps running: http://pastebin.com/8sbjyzRs
At this time SElinux is flat out disabled
$ sestatus
SELinux status: disabled
Host is just one IP, to rule out DNS problems.
$ head `pwd`/xymonclient.cfg
# Environment settings for the Xymon client.
XYMSRV="1.1.1.1" # IP address of the Xymon server
Any suggestions would be very much appreciated and welcomed!
Can you add --debug (or send a -USR2) to both xymonlaunch and the 'xymon'
call in xymonclient.sh?
Curious if it's a launch problem or a transmission issue.
HTH,
-jc