[Xymon] Whoops ! Failed to load current Xymon status, (Cannot resolve hostname)
Jerry Shenk
jerryshenk at gmail.com
Tue Jun 11 20:45:57 CEST 2024
RESOLVED:
After all that cleanup in the prior email, I went down a level to /etc and
did the same grep. I found /etc/defaults/xymon-client and it had reference
to 10.118.15.13 - I removed that and now things are working perfectly.
On Tue, Jun 11, 2024 at 12:36 PM Jerry Shenk <jerryshenk at gmail.com> wrote:
> Here's a bit more info. In the original email, I quoted a part of the log
> that indicated that communication was blocked to 127.0.0.1 and
> 10.118.15.13. 127.0.0.1 is obviously localhost and that makes sense.
> 10.118.15.13 is one of the test hosts that I was monitoring. There should
> be no attempts to communicate with that host over port 1984 but, it seems
> like that is what is failing. So, I removed all reference to 10.118.15.13
> from all the cfg files. Then I went to /usr/lib/xymon and did "grep -R
> 10.118.15.13 *" and didn't find anything. Well, originally I did find
> references in log directories and tmp directories that I cleaned out. With
> the xymon daemon stopped (service xymon stop), I ran that grep again and
> got nothing. Then, I started the xymon daemon up, did the grep and
> immediately there were references to 10.118.15.13. Where else could xymon
> be picking up this IP address?
>
>
> this is the result of "grep -R 10.118.15.13 from /var/lib/xymon":
>
> client/logs/xymonclient.log:2024-06-11 18:20:51.742811 -> Recipient
> '127.0.0.1, 10.118.15.13', timeout 15
>
> client/logs/rrd-status.log:2024-06-11 18:20:53.518567 -> Recipient
> '127.0.0.1, 10.118.15.13', timeout 15
>
> client/logs/alert.log:2024-06-11 18:20:53.518402 -> Recipient '127.0.0.1,
> 10.118.15.13', timeout 15
>
> client/logs/rrd-data.log:2024-06-11 18:20:53.526419 -> Recipient
> '127.0.0.1, 10.118.15.13', timeout 15
>
> client/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/0 Jun 11 14:43
> (10.118.15.13)
>
> client/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/1 Jun 11 14:43
> (10.118.15.13)
>
> client/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/2 Jun 11 14:44
> (10.118.15.13)
>
> client/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/3 Jun 11 14:44
> (10.118.15.13)
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp 0 1
> 10.100.10.219:46176 10.118.15.13:1984 SYN_SENT
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61061 SYN_RECV
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:22
> 10.118.15.13:42294 ESTABLISHED
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:22
> 10.118.15.13:42238 ESTABLISHED
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:60972 TIME_WAIT
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61034 TIME_WAIT
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61033 TIME_WAIT
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61035 FIN_WAIT2
>
> client/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:60971 TIME_WAIT
>
> server/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/0 Jun 11 14:43
> (10.118.15.13)
>
> server/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/1 Jun 11 14:43
> (10.118.15.13)
>
> server/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/2 Jun 11 14:44
> (10.118.15.13)
>
> server/tmp/msg.ma-mrtgmon.txt.14273:monitor pts/3 Jun 11 14:44
> (10.118.15.13)
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp 0 1
> 10.100.10.219:46176 10.118.15.13:1984 SYN_SENT
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61061 SYN_RECV
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:22
> 10.118.15.13:42294 ESTABLISHED
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:22
> 10.118.15.13:42238 ESTABLISHED
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:60972 TIME_WAIT
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61034 TIME_WAIT
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61033 TIME_WAIT
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:61035 FIN_WAIT2
>
> server/tmp/msg.ma-mrtgmon.txt.14273:tcp6 0 0 10.100.10.219:80
> <http://10.100.10.219/> 10.118.15.13:60971 TIME_WAIT
>
> root at ma-mrtgmon:/usr/lib/xymon#
>
>
>
>
>
> On Tue, Jun 11, 2024 at 11:11 AM Jerry Shenk <jerryshenk at gmail.com> wrote:
>
>> yes, it's a new installation and that is exactly what it sounds like.
>> The error says "Cannot determine IP address of message recipient
>> (127.0.0.1)". How can that be?....that's the localhost and, that's the
>> only xymon computer. I can ping 127.0.0.1 and connect to port 1984 and, I
>> can even connect using bb and pull hostinfo (/usr/lib/xymon/server/bb
>> --debug 10.100.10.219 hostinfo). That command also works using 127.0.0.1
>> and ma-mrtgmon (the name of the xymon server).
>>
>> On Tue, Jun 11, 2024 at 12:07 PM Josh Luthman <
>> josh at imaginenetworksllc.com> wrote:
>>
>>> Is this a new installation?
>>>
>>> Sounds like your client is trying to send it to a name that it can not
>>> resolve.
>>>
>>> On Tue, Jun 11, 2024 at 10:58 AM Jerry Shenk <jerryshenk at gmail.com>
>>> wrote:
>>>
>>>> I'm installing a new Xymon system on Ubunto 24 LTS. Things seem like
>>>> they are running but, the only host any "dots" is the xymon host itself.
>>>> When I add other hosts to the hosts.cfg file, they show up but only have a
>>>> dash instead of the green, yellow, or red dot.
>>>>
>>>> If I tail /var/log/xymon/xymongen.log, I get the following error
>>>> repeatedly.
>>>>
>>>> 2024-06-11 14:10:42.740606 Whoops ! Failed to send message (Cannot
>>>> resolve hostname)
>>>>
>>>> 2024-06-11 14:10:42.740701 -> Cannot determine IP address of message
>>>> recipient 127.0.0.1,
>>>>
>>>> 2024-06-11 14:10:42.740708 -> Recipient '127.0.0.1, 10.118.15.13',
>>>> timeout 15
>>>>
>>>> 2024-06-11 14:10:42.740713 -> 1st line: 'xymondboard
>>>> fields=hostname,testname,color,flags,lastchange,logtime,validtiacktime,disabletime,sender,cookie,line1,acklist
>>>> '
>>>>
>>>> 2024-06-11 14:10:42.740735 xymond status-board not available, code 2
>>>>
>>>> 2024-06-11 14:10:42.740740 Failed to load current Xymon status,
>>>> aborting page-update
>>>>
>>>>
>>>> I'm not sure how relevant this is but, I've used bb to connect to both
>>>> local host (127.0.0.1) and the actual IP address and if I pass hostinfo
>>>> option, I get a list of hosts the same as the web site shows. If I pass
>>>> the option config (/usr/lib/xymon/server/bb 127.0.0.1 'config') there is a
>>>> 15 second delay and then a "Whoops ! Failed to send message (timeout)"
>>>> error.
>>>>
>>>>
>>>> ReplyForward
>>>> Add reaction
>>>>
>>>> _______________________________________________
>>>> Xymon mailing list
>>>> Xymon at xymon.com
>>>> http://lists.xymon.com/mailman/listinfo/xymon
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20240611/7eb638f3/attachment.htm>
More information about the Xymon
mailing list