Xymon Mailing List Archive search

Whoops ! bb failed to send message - timeout

4 messages in this thread

list Mark Whalley · Mon, 9 Nov 2009 02:28:24 -0500 ·
Hi xymon/hobbit group

 
Over the past couple of days, I have been trying to set up a xymon with
some success.

 
My setup so far.  I have xymon 4.3.0.0 beta2 installed and running on a
Fedora 11 Virtual Machine (VMWare server 1.0.9) on a Windows XP laptop.
This xymon server appears to be working correctly with it monitoring
itself (bbgen, bbtest, conn, cpu etc) and happily doing connectivity
tests to some remote linux/aix servers that I have access to at work.
So far, so good.

 
I now want to do some client monitoring.  Initially starting with the
in-built monitoring tools (cpu, disk etc), then to develop some of my
own scripts (korn/born shell) to monitor my Ingres installations.  To
start off, I have installed xymon client on another laptop which is also
running Fedora 11 (on bare metal rather than via a VM).  Although the
xymon server is happily pinging the client and showing green on the
current status, I do not seem to be able to get it to display any of the
other data.

 
On checking the client, I am getting "Whoops ! bb failed to send message
- timeout" every 5 minutes within hobbitclient.log.

 
On further checking, I have found that although I can telnet and ping
from the server to the client, the client is unable to even ping the
server (via IP address) - it just hangs.

 
Server to Client:

[xymon at beziers etc]$ ping 192.168.1.69

PING 192.168.1.69 (192.168.1.69) 56(84) bytes of data.

64 bytes from 192.168.1.69: icmp_seq=1 ttl=128 time=5.74 ms

64 bytes from 192.168.1.69: icmp_seq=2 ttl=128 time=1.41 ms

64 bytes from 192.168.1.69: icmp_seq=3 ttl=128 time=2.42 ms

 
Client to Server:

[xymon at lecroisic client]$ ping 192.168.174.129

PING 192.168.174.129 (192.168.174.129) 56(84) bytes of data.

 
Thinking it might be a firewall issue, I have temporarily disabled all
firewall protection on both client and server, and even disabled the
firewall on Windows XP (within which the VMawre Server is running the
xymon server) - but with no success.

 
This unfortunately is where my networking knowledge fails me (and thus
my plea for help!) and a Google search has not given me any clues (that
I can understand).  

Any thoughts?

 
Regards

Mark
list Phil Meech · Mon, 9 Nov 2009 08:39:54 +0000 ·
Hi Mark,

I presume both laptops are on the same lan?  What are the subnet masks of
the Xymon server and client - also probably worth advising whether the VM
host resides on the same subnet as the client laptop?  I'm guessing it could
be a mask issue...

Cheers,
Phil

2009/11/9 Mark Whalley <user-7d9dd9a0eac7@xymon.invalid>
quoted from Mark Whalley
 Hi xymon/hobbit group


Over the past couple of days, I have been trying to set up a xymon with
some success.


My setup so far.  I have xymon 4.3.0.0 beta2 installed and running on a
Fedora 11 Virtual Machine (VMWare server 1.0.9) on a Windows XP laptop.
This xymon server appears to be working correctly with it monitoring itself
(bbgen, bbtest, conn, cpu etc) and happily doing connectivity tests to some
remote linux/aix servers that I have access to at work.  So far, so good.


I now want to do some client monitoring.  Initially starting with the
in-built monitoring tools (cpu, disk etc), then to develop some of my own
scripts (korn/born shell) to monitor my Ingres installations.  To start off,
I have installed xymon client on another laptop which is also running Fedora
11 (on bare metal rather than via a VM).  Although the xymon server is
happily pinging the client and showing green on the current status, I do not
seem to be able to get it to display any of the other data.


On checking the client, I am getting “Whoops ! bb failed to send message –
timeout” every 5 minutes within hobbitclient.log.


On further checking, I have found that although I can telnet and ping from
the server to the client, the client is unable to even ping the server (via
IP address) – it just hangs.


Server to Client:

[xymon at beziers etc]$ ping 192.168.1.69

PING 192.168.1.69 (192.168.1.69) 56(84) bytes of data.

64 bytes from 192.168.1.69: icmp_seq=1 ttl=128 time=5.74 ms

64 bytes from 192.168.1.69: icmp_seq=2 ttl=128 time=1.41 ms

64 bytes from 192.168.1.69: icmp_seq=3 ttl=128 time=2.42 ms


Client to Server:

[xymon at lecroisic client]$ ping 192.168.174.129

PING 192.168.174.129 (192.168.174.129) 56(84) bytes of data.


Thinking it might be a firewall issue, I have temporarily disabled all
firewall protection on both client and server, and even disabled the
firewall on Windows XP (within which the VMawre Server is running the xymon
server) – but with no success.


This unfortunately is where my networking knowledge fails me (and thus my
plea for help!) and a Google search has not given me any clues (that I can
understand).

Any thoughts?


Regards

Mark
list Oyvind Bjorge · Mon, 9 Nov 2009 09:44:49 +0100 ·
On one of my xymon clients, I have a scheduled job that runs every 5 min.
This is a perl script, and one of the first tings it does is to log that it has started.
It is therefor not likely that this crashes before this logging.
The log shows that some of the times it is not executed. This happens approx 10% of the times.

Anyone that have some ide of why this is happening?

Øyvind
list Rolf Schrittenlocher · Mon, 09 Nov 2009 09:55:26 +0100 ·
Does the client log say anything about it (LOG defined in clientlaunch.cfg)?
quoted from Oyvind Bjorge
On one of my xymon clients, I have a scheduled job that runs every 5 min.

This is a perl script, and one of the first tings it does is to log 
that it has started.

It is therefor not likely that this crashes before this logging.

The log shows that some of the times it is not executed. This happens 
approx 10% of the times.

 
Anyone that have some ide of why this is happening?

 
Øyvind
-- 

Mit freundlichen Gruessen
Rolf Schrittenlocher

HeBIS-IT, Senckenberganlage 31, 60054 Frankfurt
Tel: (XX) XX - XXX XXXXX   Fax: (XX) XX XXX XXXXX
LBS: user-1e39a1813094@xymon.invalid
Persoenlich: user-ea9d95bffcf0@xymon.invalid