sslcert

Le 21/01/2011 00:14, dOCtoR MADneSs a écrit :

Le 20/01/2011 23:13, Henrik Størner a écrit :

In <user-76277bbce9e1@xymon.invalid> dOCtoR MADneSs <user-d54077869176@xymon.invalid> writes:

You presume right. Both toto and tata reports their own IP reported.

OK, we need some debug data. Could you run - on the Xymon server doing your
network tests - these two commands:

   xymoncmd xymonnet --debug --no-update tata toto > tt.txt 2>&1

and either post the tt.txt file, or send it directly to me if you don't
want to post such data publicly ? Feel free to anonymize any IP's
and/or hostnames, as long as you do so consistently - e.g. replace
the first octet of all IP's with "000".


Regards,
Henrik

Hi,

Thank you, in looking in the debug file, I found the reason. In fact,
toto points to the tata IP, because of domain... so I changed the name
to FQDN and used an alias. I(ll check tomorrow night if it's OK. I
ignored the fact that xymon doesn't care about IP provided in hosts.cfg
hence my error.

I confirm that changing the host name tata to the FQDN solves the
problem. Combining CLIENT: and HOST: makes everything looking like it
should, and everything run fine