xymon for AIX

list Oliver
Thu, 19 May 2016 16:41:32 -0400
Message-Id: <CAOAEFMW2t+8SPaBvAH1NcmwSM2qG1tH3xiQA8=NRzH1AJUKk=user-4e0f9cdb28f9@xymon.invalid>

What is the output from:
client$ telnet 172.31.2.131 1984

On Thu, May 19, 2016 at 3:31 PM, Wonder fo <user-8a0f7702e6b1@xymon.invalid> wrote:

The client and server are both inside the firewall sitting on the local
network. No issue with either end points to reach one another in terms of
routing.  The standard monitoring attributes like conn, info,ssh,trends
serving through the server for the client page works, but I can't seem to
get the *cpu,disk, memory* status from the client to the server to
report.

xymonclient.log from the client host is consistently throwing "Whoops !
Failed to send message (timeout)"


*bbd* <http://stlxymon01/xymon-cgi/columndoc.sh?bbd>; *clientlog*
<http://stlxymon01/xymon-cgi/columndoc.sh?clientlog>; *conn*
<http://stlxymon01/xymon-cgi/columndoc.sh?conn>; *cpu*
<http://stlxymon01/xymon-cgi/columndoc.sh?cpu>; *disk*
<http://stlxymon01/xymon-cgi/columndoc.sh?disk>; *files*
<http://stlxymon01/xymon-cgi/columndoc.sh?files>; *http*
<http://stlxymon01/xymon-cgi/columndoc.sh?http>; *info*
<http://stlxymon01/xymon-cgi/columndoc.sh?info>; *inode*
<http://stlxymon01/xymon-cgi/columndoc.sh?inode>; *memory*
<http://stlxymon01/xymon-cgi/columndoc.sh?memory>; *msgs*
<http://stlxymon01/xymon-cgi/columndoc.sh?msgs>; *ports*
<http://stlxymon01/xymon-cgi/columndoc.sh?ports>; *procs*
<http://stlxymon01/xymon-cgi/columndoc.sh?procs>; *ssh*
<http://stlxymon01/xymon-cgi/columndoc.sh?ssh>; *trends*
<http://stlxymon01/xymon-cgi/columndoc.sh?trends>; *xymond*
<http://stlxymon01/xymon-cgi/columndoc.sh?xymond>; *xymongen*
<http://stlxymon01/xymon-cgi/columndoc.sh?xymongen>; *xymonnet*
<http://stlxymon01/xymon-cgi/columndoc.sh?xymonnet>;
  server [image: bbd:green:15d02h36m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=bbd>; [image:
clientlog:green:172.31.2.131]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=clientlog>; [image:
conn:green:14d22h02m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=conn>; [image:
cpu:green:6d02h08m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=cpu>; [image:
disk:green:6d03h03m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=disk>; [image:
files:clear:6d03h03m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=files>; [image:
http:green:2d00h06m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=http>; [image:
info:green:172.31.2.131]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=info>; [image:
inode:green:6d03h03m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=inode>; [image:
memory:green:6d03h03m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=memory>; [image:
msgs:green:6d03h03m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=msgs>; [image:
ports:green:6d02h40m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=ports>; [image:
procs:green:3d05h33m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=procs>; [image:
ssh:green:8d22h29m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=ssh>; [image:
trends:green:172.31.2.131]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=trends>; [image:
xymond:green:1d23h14m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=xymond>; [image:
xymongen:green:9d23h50m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=xymongen>; [image:
xymonnet:green:20h22m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=stlxymon01.huttig.com&SERVICE=xymonnet>;
ADMIN *conn* <http://stlxymon01/xymon-cgi/columndoc.sh?conn>; *info*
<http://stlxymon01/xymon-cgi/columndoc.sh?info>; *ssh*
<http://stlxymon01/xymon-cgi/columndoc.sh?ssh>; *trends*
<http://stlxymon01/xymon-cgi/columndoc.sh?trends>;
  client [image: conn:green:10d20h30m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=aixadm.huttig.com&SERVICE=conn>; [image:
info:green:172.31.0.13]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=aixadm.huttig.com&SERVICE=info>; [image:
ssh:green:10d20h30m]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=aixadm.huttig.com&SERVICE=ssh>; [image:
trends:green:172.31.0.13]
<http://stlxymon01/xymon-cgi/svcstatus.sh?HOST=aixadm.huttig.com&SERVICE=trends>;


On Wed, May 18, 2016 at 5:19 PM, Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
wrote:

On Thu, 19 May 2016, 07:27 Wonder fo <user-8a0f7702e6b1@xymon.invalid> wrote:

Hi Stef,

Your last tip was helpful to get through with the hump on getting the
AIX client compiled and initial install.

...

 Will connect to address 172.31.2.131 port 1984

9568302 2016-05-18 15:59:14.134814 Closing connection
2016-05-18 15:59:14.134870 Whoops ! Failed to send message (timeout)
2016-05-18 15:59:14.135049 ->
2016-05-18 15:59:14.135099 ->  Recipient '172.31.2.131', timeout 15
2016-05-18 15:59:14.135185 ->  1st line: 'test'

It looks like a connectivity problem. Timeouts are usually caused by
something n the path between the end points, invariably either a routing
problem or a firewall problem. Note that a firewall can be on either host
(eg iptables, ipfw, pf, etc).

Check that you can ping from client to server. If so, routing is ok. Then
check that you can telnet to the server on port 1984. If not, suspect a
firewall.

J