To be perfectly honest, I just upgraded to 4.3.18 on March 27th from 4.3.13 on the server side, and cannot be positive that it was working in 4.3.18. I certainly didn't notice that it wasn't working.
I can say that it was working in 4.3.13.
There is no hosts.cfg entry on the server side.
Thanks,
John
Upcoming PTO:
John Rothlisberger
IT Strategy, Infrastructure & Security - Technology Growth Platform
TGP for Business Process Outsourcing
Accenture
XXX.XXX.XXXX office
-----Original Message-----
From: J.C. Cleaver [mailto:user-87556346d4af@xymon.invalid]
Sent: Tuesday, April 07, 2015 12:29 PM
To: Andy Smith; Rothlisberger, John R.
Subject: Re: [Xymon] Summary for remotes in 4.3.19 not working
On Tue, April 7, 2015 7:47 am, Andy Smith wrote:
On 7 April 2015 at 04:43, J.C. Cleaver <user-87556346d4af@xymon.invalid>
wrote:
On Mon, April 6, 2015 6:53 am, user-7adce57665bb@xymon.invalid
wrote:
Is there anyone else having trouble with the summary function in
4.3.19?
From my remote server I am getting the following errors in
display.log:
2015-04-06 14:40:15.860975 Whoops ! Failed to send message
(Connection
failed)
2015-04-06 14:40:15.861020 -> Could not connect to Xymon
daemon at N.N.N.N:1984 (Connection refused)
2015-04-06 14:40:15.861026 -> Recipient 'N.N.N.N', timeout 15
2015-04-06 14:40:15.861032 -> 1st line: 'summary
summary.Remotes.MyRemoteSite red https://my.url.com/MyRemoteSite/
Mon
Apr
6 14:40:15 2015'
My hosts.cfg file looks like:
summary Remotes.MyRemoteSite 63.240.185.103
https://my.url.com/MyRemoteSite/
I have 4 servers that I just upgraded to 4.3.19 and all were a mix
from
4.3.18 to 4.3.0 and all worked fine prior to the upgrade.
I am able to telnet to N.N.N.N:1984 from my remote sites. I do
not
have
any firewalls running on my main server.
Ideas?
Hmm. I'm not aware of anything that would have changed in this
regard, especially in a way that would have looked like a
communications issue.
Can you verify with a 'ping' and 'dummy' message that normal
connectivity from those boxes work normally?
If so, can you run xymongen with --debug enabled? There should be an
init_sum section and a segment near the end showing it being sent
off.
Regards,
-jc
I can repeat this, it is something on the server side. It was last
seen working here on 4.3.13.
In a lab I have 3 servers, 2 on Solaris (4.3.4 & 4.3.19) and 4.3.19
on
CentOS 5. I am sending the summary from the CentOS server to both of
the Solaris servers. The hosts.cfg on the CentOS server contains
:-
summary builds.centos63_i686 192.168.2.124 http://192.168.2.61/xymon/
summary builds.centos63_i686 192.168.2.122 http://192.168.2.61/xymon/
This is appearing correctly on 4.3.4 (192.168.2.122), but missing
completely on 4.3.19 (192.168.2.124)
Here is a clue, checking xymondboard on each Solaris server from the
CentOS server :-
$ xymon 192.168.2.122 "xymondboard test=centos63_i686"
summary|builds.centos63_i686|green||0|1428398444|1428400244|0|0|192.16
summary|8.2.61||green
http://192.168.2.61/xymon/ Tue Apr 7 10:20:05 2015
$ xymon 192.168.2.124 "xymondboard
test=centos63_i686"
|builds.centos63_i686|green||1428387271|1428398444|1428400244|0|0|192.
|168.2.61||green
http://192.168.2.61/xymon/ Tue Apr 7 10:20:05 2015
(note the missing "summary" psuedo hostname field stored on 4.3.19).
--
Andy
Gotcha.
Can you give your server-side hosts.cfg line for this?
John: Was your previous direct server version 4.3.18, or were you
running an older version than that?
-jc
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
www.accenture.com