On 22 August 2013 08:52, Galen Johnson <user-87f955643e3d@xymon.invalid> wrote:
On my client, I have XYMSRV="127.0.0.1" and I've commented out the
"DISABLE" in clientlaunch.cfg. I'm seeing content in the
/tmp/msg.myhost.txt file that looks like what I would expect.
Good. I'm assuming you commented out "DISABLED" in the [msgcache] section
of clientlaunch.cfg and not somewhere else. At that stage, you should be
able to connect from the Xymon server to the client on port 1984 (eg with
"telnet client.host.name 1984", perhaps sending it a "pullclient" command
also). If this works, then the msgcache process is most likely ready for
use.
On the server, I've added "pulldata" to the entry in etc/hosts.cfg, edited
the etc/tasks.cfg to comment out "DISABLE"
Again, "DISABLED" in the [xymonfetch] section?
and set the server IP to my server's IP as well as tried 127.0.0.1.
This is the default, so you can leave out the "--server=127.0.0.1" if you
want.
I see the following in my log:
Which log?
2013-08-21 18:38:06 Whoops ! Failed to send message (Connection failed)
2013-08-21 18:38:06 -> Could not connect to Xymon daemon at 10.40.1.39:1984(Connection refused)
2013-08-21 18:38:06 -> Recipient '10.40.1.39', timeout 15
2013-08-21 18:38:06 -> 1st line: 'config hosts.cfg'
2013-08-21 18:38:06 Cannot load hosts.cfg from xymond, code 5
2013-08-21 18:38:06 Failed to load from xymond, reverting to file-load
This implies that the logs are on the Xymon server (10.40.1.39?), but the
xymond daemon is not running, or at least not on port 1984. Make sure you
can do "telnet 10.40.1.39 1984" on the Xymon server.
2013-08-21 18:38:06 Connection lost during connect/write to
10.40.1.39:1984 (req 2): Connection refused
Ah, this message only comes from xymonfetch. So it looks like xymonfetch
is unable to send messages into xymond on port 1984.
J