Hi,
Currently in the process of setting up a new Xymon installation based on Solaris 10 x86.
We’ve managed to compile and setup the server and clients fine, clients are reporting into the main Xymon server without issue. We have however got stuck on one problem.
When trying to auto-update the clients with a new version of the client it fails. See below:
$ ./clientupdate --update=client_v3 2011-12-06 11:03:59 Whoops ! Failed to send message (Connection failed) 2011-12-06 11:03:59 -> connect to Xymon daemon at 127.0.0.1:1984 failed (Connection refused) 2011-12-06 11:03:59 -> Recipient '127.0.0.1', timeout 15 2011-12-06 11:03:59 -> 1st line: 'download client_v3.tar' 2011-12-06 11:03:59 Cannot fetch new client tarfile: Status 5 tar: blocksize = 0
The client is however connecting to the Xymon server and sending alerts without issue.
When I run the same command on the Xymon server to update its client, it works fine.
I’m assuming it’s failing because it’s trying to contact 127.0.0.1, however I can’t see where it’s getting this address from?! When the client was compiled we gave the IP address of the Xymon server.
When I run a strings on the clientupdate binary I can see the following entry hardcoded?!
XYMONSERVERIP
127.0.0.1
Any help would be greatly appreciated.
Adam
On 06-12-2011 12:14, Adam Bml wrote:
We’ve managed to compile and setup the server and clients fine, clients are reporting into the main Xymon server without issue. We have however got stuck on one problem.
When trying to auto-update the clients with a new version of the client it fails. See below:
$ ./clientupdate --update=client_v3 2011-12-06 11:03:59 Whoops ! Failed to send message (Connection failed) 2011-12-06 11:03:59 -> connect to Xymon daemon at 127.0.0.1:1984 2011-12-06 11:03:59 -> Recipient '127.0.0.1', timeout 15 [snip] I’m assuming it’s failing because it’s trying to contact 127.0.0.1, however I can’t see where it’s getting this address from?! When the client was compiled we gave the IP address of the Xymon server.
"clientupdate" expects to run with the full set of Xymon client environment variables defined - it will then pickup the XYMONSERVERIP that you have configured in the xymonclient.cfg file.
Usually, "clientupdate" is run as part of the normal client run-cycle, so this has already been defined by xymonlaunch.
To test this by hand, try prefixing the command with "xymoncmd". Like:
xymoncmd clientupdate --update=client_v3That should work.
Regards, Henrik
participants (2)
-
adambml1＠gmail.com
-
henrik＠hswn.dk