Xymon Mailing List Archive search

TS - hobbitd_client RED

2 messages in this thread

list Tom Schmitt · Wed, 6 Feb 2013 10:11:40 -0700 ·
I am continuing to have a problem on my production system:  CentOS with
Xymon 4.3.0-0.beta2

I am getting the hobbitd_client ICON and the message says:

 
-          Program crashed

-          Fatal signal caught!

 
Does anyone have an idea where to look to correct this problem?

I cannot find anything in the 'Client data' link.

 
I have 2 servers: monitorp and monitor2.

Monitor2 watches monitor2 and begins alerting if monitorp does not
answer a ping.

I also did the following thinking that I might have a corrupted client
program.

-          I copies the /home/xymon/client/bin directory from monitor2
-> monitorp

-          I restarted the client on monitorp

-          Still have the same problem

 
You cannot DISABLE the ICON.

You can drop the ICON but it comes right back from the client on the
primary Xymon server.

 
Thanks,

 
Tom Schmitt

Senior IT Staff - R&D

L-3 Communication Systems West

640 North 2200 West    P.O. Box 16850

Salt Lake City, UT  XXXXX

Phone (XXX) XXX-XXXX

Cell      (XXX) XXX-XXXX

eFax    (XXX) XXX-XXXX

            \\\\||////

               \ ~  ~ /  

               | @  @ |

--oOo---(_)---oOo--

Have A Nice Day !

 
It is not necessary to change.

Survival is not mandatory.

        -- W. Edwards Deming
list Japheth Cleaver · Wed, 6 Feb 2013 17:40:56 -0000 (UTC) ·
quoted from Tom Schmitt
I am continuing to have a problem on my production system:  CentOS with
Xymon 4.3.0-0.beta2

I am getting the hobbitd_client ICON and the message says:


-          Program crashed

-          Fatal signal caught!


Does anyone have an idea where to look to correct this problem?
That's a message that will get sent out if a program crashes out; it's set
up by the signal handler within most of the xymon binaries.

In this case, looking in the hobbitd_client log in /var/log/hobbit (or
wherever you're setting it in hobbitlaunch.cfg (?) might reveal something.
If it's happenning more intermittently, try adding --debug to the options
to see if there's (perhaps) a specific message that's causing the fault.

HTH,

-jc