xymonlaunch is not updating after the first update
Hi All, migrating from bb to xymon to which the bbclient updates fine back to the xymon server. However once I stop the bb client
and start the xymon client it seems the xymonlaunch is not updating after the first update. So after 30 mins client tests will purple.
I have run a tcpdump on the client and no traffic on port 1984 is seen after the first update. Also tested external script bb-ntp on the client
to which it behalves the same.
Please help
Regards
Mark
This e-mail, including any attachments to it, may contain confidential and/or personal information. If you have received this e-mail in error, you must not copy, distribute, or disclose it, use or take any action based on the information contained within it. Please notify the sender immediately by return e-mail of the error and then delete the original e-mail.
The information contained within this e-mail may be solely the opinion of the sender and may not necessarily reflect the position, beliefs or opinions of the organisation on any issue. This email has been swept for the presence of computer viruses known to the organisation’s anti-virus systems.
On Fri, Jan 20, 2012 at 10:39 AM, Mark Falzon <Mark.Falzon at salmat.com.au> wrote:
and start the xymon client it seems the xymonlaunch is not updating after the first update. So after 30 mins client tests will purple.
How do you know the first update is working?
Have you checked for clues in the logfiles xymonclient.log and clientlaunch.log?
Try running the client script manually (as the xymon user), perhaps like so:
$ sudo -u xymon ~xymon/client/bin/xymoncmd $ $XYMONHOME/bin/xymonclient.sh
and see if you get any errors. Check that you're creating a non-empty file in $XYMONTMP called "msg.<hostname>.txt".
Try running the following (as the xymon user) and look for problems:
$ $XYMON --debug $XYMSRV "@" < $XYMONTMP/msg.$MACHINEDOTS.txt
J
How do you know the first update is working? After running ~xymon/client/runclient.sh I run a tcpdump and can see a flow of packets and tests are green. I don't see any packets sent after this.
Have you checked for clues in the logfiles xymonclient.log and clientlaunch.log? Don't see any errors in both logs
Running both xymoncmd and xymon runs without errors. It just seems like the xymonlaunch is not updating every x interval.
19635 2012-01-20 11:41:31 Transport setup is: 19635 2012-01-20 11:41:31 xymondportnumber = 1984 19635 2012-01-20 11:41:31 xymonproxyhost = NONE 19635 2012-01-20 11:41:31 xymonproxyport = 0 19635 2012-01-20 11:41:31 Recipient listed as '10.101.64.25' 19635 2012-01-20 11:41:31 Standard protocol on port 1984 19635 2012-01-20 11:41:31 Will connect to address 10.101.64.25 port 1984 19635 2012-01-20 11:41:31 Connect status is 0 19635 2012-01-20 11:41:31 Sent 11772 bytes 19635 2012-01-20 11:41:31 Sent 9156 bytes 19635 2012-01-20 11:41:31 Sent 15696 bytes 19635 2012-01-20 11:41:31 Sent 11323 bytes 19635 2012-01-20 11:41:31 Read 41 bytes log:/var/log/messages:10240 ignore MARK
regards
Mark -----Original Message----- From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Friday, 20 January 2012 11:04 AM To: Mark Falzon Cc: Xymon at xymon.com Subject: Re: [Xymon] xymonlaunch is not updating after the first update
On Fri, Jan 20, 2012 at 10:39 AM, Mark Falzon <Mark.Falzon at salmat.com.au> wrote:
and start the xymon client it seems the xymonlaunch is not updating after the first update. So after 30 mins client tests will purple.
How do you know the first update is working?
Have you checked for clues in the logfiles xymonclient.log and clientlaunch.log?
Try running the client script manually (as the xymon user), perhaps like so:
$ sudo -u xymon ~xymon/client/bin/xymoncmd $ $XYMONHOME/bin/xymonclient.sh
and see if you get any errors. Check that you're creating a non-empty file in $XYMONTMP called "msg.<hostname>.txt".
Try running the following (as the xymon user) and look for problems:
$ $XYMON --debug $XYMSRV "@" < $XYMONTMP/msg.$MACHINEDOTS.txt
J
This e-mail, including any attachments to it, may contain confidential and/or personal information. If you have received this e-mail in error, you must not copy, distribute, or disclose it, use or take any action based on the information contained within it. Please notify the sender immediately by return e-mail of the error and then delete the original e-mail.
The information contained within this e-mail may be solely the opinion of the sender and may not necessarily reflect the position, beliefs or opinions of the organisation on any issue. This email has been swept for the presence of computer viruses known to the organisation’s anti-virus systems.
On Fri, Jan 20, 2012 at 12:06 PM, Mark Falzon <Mark.Falzon at salmat.com.au> wrote:
How do you know the first update is working? After running ~xymon/client/runclient.sh I run a tcpdump and can see a flow of packets and tests are green. I don't see any packets sent after this.
I see, so presumably, after running this again manually you'd get an update.
It just seems like the xymonlaunch is not updating every x interval.
Yes, seems like it. Is "xymonlaunch" running?
Maybe add "--verbose" or "--debug" to the command-line that runs xymonlaunch (in runclient.sh). Then have another look at the logs.
J
Adding --debug gives the following every 5 seconds.
18307 2012-01-23 10:19:41 Starting tasklist scan 18307 2012-01-23 10:19:46 18307 2012-01-23 10:19:46 Starting tasklist scan 18307 2012-01-23 10:19:51 18307 2012-01-23 10:19:51 Starting tasklist scan 18307 2012-01-23 10:19:56 18307 2012-01-23 10:19:56 Starting tasklist scan
Adding --verbose give the following only
2012-01-23 10:22:29 xymonlaunch starting 2012-01-23 10:22:29 Loading tasklist configuration from /home/xymon/client/etc/clientlaunch.cfg 2012-01-23 10:22:29 Task client started with PID 18539 2012-01-23 10:22:29 Task ntp started with PID 18540
Cheers
-----Original Message----- From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Friday, 20 January 2012 3:12 PM To: Mark Falzon Cc: Xymon at xymon.com Subject: Re: [Xymon] xymonlaunch is not updating after the first update
On Fri, Jan 20, 2012 at 12:06 PM, Mark Falzon <Mark.Falzon at salmat.com.au> wrote:
How do you know the first update is working? After running ~xymon/client/runclient.sh I run a tcpdump and can see a flow of packets and tests are green. I don't see any packets sent after this.
I see, so presumably, after running this again manually you'd get an update.
It just seems like the xymonlaunch is not updating every x interval.
Yes, seems like it. Is "xymonlaunch" running?
Maybe add "--verbose" or "--debug" to the command-line that runs xymonlaunch (in runclient.sh). Then have another look at the logs.
J
This e-mail, including any attachments to it, may contain confidential and/or personal information. If you have received this e-mail in error, you must not copy, distribute, or disclose it, use or take any action based on the information contained within it. Please notify the sender immediately by return e-mail of the error and then delete the original e-mail.
The information contained within this e-mail may be solely the opinion of the sender and may not necessarily reflect the position, beliefs or opinions of the organisation on any issue. This email has been swept for the presence of computer viruses known to the organisation’s anti-virus systems.
On Mon, Jan 23, 2012 at 10:27 AM, Mark Falzon <Mark.Falzon at salmat.com.au> wrote:
Adding --verbose give the following only
2012-01-23 10:22:29 xymonlaunch starting 2012-01-23 10:22:29 Loading tasklist configuration from /home/xymon/client/etc/clientlaunch.cfg 2012-01-23 10:22:29 Task client started with PID 18539 2012-01-23 10:22:29 Task ntp started with PID 18540
Yup, looks like it's starting them only once, exactly as you have described. Very peculiar. Is it possible that the clientlaunch.cfg file has a typo that is being interpreted as a very large INTERVAL? Can you post the relevant sections?
J
participants (2)
-
jlaidman@rebel-it.com.au
-
Mark.Falzon@salmat.com.au