Xymon Mailing List Archive search

problems on server

3 messages in this thread

list Longina Przybyszewska · Tue, 4 Apr 2006 14:06:04 +0200 (CEST) ·
I have some problems with hobbitd_client on server (sparc/solaris9).

1. hobbit client  wouldn't  launch from hobbit server's hobbitlaunch- I got "fatal signal caught, treminating with code 134".

I tried to start it from init.d insted of - from client's hobbitlaunch  and it works.

On the display, hobbitd_client stays blinking red. How can I get rid of that?

2. bbd is constantly PURPLE
In bb-services, it is defined as:
[bbd]
    send "dummy"
    port 1984
so in fact it tests hobbitd-but why it is purple?
Hobbitd is OK.

Regards
Longina
--
Longina Przybyszewska, system programmer
Dept. of Math. & Comp. Sci. - IMADA
University of Southern Denmark, Odense
Campusvej 55,DK-5230 Odense M, Denmark

tel: +XX XXXX XXXX - http://www.imada.sdu.dk         email: user-db0a93c0e294@xymon.invalid
--
list Henrik Størner · Tue, 4 Apr 2006 15:14:10 +0200 ·
quoted from Longina Przybyszewska
On Tue, Apr 04, 2006 at 02:06:04PM +0200, Longina Przybyszewska wrote:
I have some problems with hobbitd_client on server (sparc/solaris9).

1. hobbit client  wouldn't  launch from hobbit server's hobbitlaunch- 
I got "fatal signal caught, treminating with code 134".

I tried to start it from init.d insted of - from client's 
hobbitlaunch  and it works.
Somehow I doubt that it works. hobbitd_client is fed via a mechanism
involving semaphores and shared memory, so it should really run from
hobbitlaunch to make sure you have various permissions set right.

Which version is this ? 4.1.2p1, or one of the snapshots ?
Have you looked at the logfiles, or tried running the hobbitd_client
core-dump through gdb as described in the "Known Problems" doc ?
http://www.hswn.dk/hobbit/help/known-issues.html#bugreport
quoted from Longina Przybyszewska
On the display, hobbitd_client stays blinking red. How can I get rid 
of that?
http://www.hswn.dk/hobbit/help/hobbit-tips.html#droptest
quoted from Longina Przybyszewska
2. bbd is constantly PURPLE
In bb-services, it is defined as:
[bbd]
   send "dummy"
   port 1984
so in fact it tests hobbitd-but why it is purple?
Hobbitd is OK.
Because the bbd network test is not being executed for this host. Check
your bb-hosts file, it must have a "bbd" tag defined for your hobbit
server.


Henrik
list Longina Przybyszewska · Wed, 5 Apr 2006 12:36:26 +0200 (CEST) ·
quoted from Henrik Størner
On Tue, 4 Apr 2006, Henrik Stoerner wrote:
1. hobbit client  wouldn't  launch from hobbit server's hobbitlaunch-
I got "fatal signal caught, treminating with code 134".

I tried to start it from init.d insted of - from client's
hobbitlaunch  and it works.
Somehow I doubt that it works. hobbitd_client is fed via a mechanism
involving semaphores and shared memory, so it should really run from
hobbitlaunch to make sure you have various permissions set right.
client runs from client/bin/hobbitlaunch insted of 
server/bin/hobbitlaunch, I have commented out [hobbitclient] from 
server/etc/hobbitlaunch.cfg

It seems to work, I got disk/mem/proc reports, but of course 
hobbitd_client is blinking RED. 
quoted from Henrik Størner
Which version is this ? 4.1.2p1, or one of the snapshots ?
Have you looked at the logfiles, or tried running the hobbitd_client
core-dump through gdb as described in the "Known Problems" doc ?
http://www.hswn.dk/hobbit/help/known-issues.html#bugreport
this is the 4.1.2p1, on sparc/Solaris9
here output from gdb:
---
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you 
are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for 
details.
This GDB was configured as "sparc-sun-solaris2.9"...
Core was generated by `hobbitd_client --debug'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/local/lib/libpcre.so.0...done.
Loaded symbols for /usr/local/lib/libpcre.so.0
Reading symbols from /usr/lib/libresolv.so.2...done.
Loaded symbols for /usr/lib/libresolv.so.2
Reading symbols from /usr/lib/libsocket.so.1...done.
Loaded symbols for /usr/lib/libsocket.so.1
Reading symbols from /usr/lib/libnsl.so.1...done.
Loaded symbols for /usr/lib/libnsl.so.1
Reading symbols from /usr/lib/libc.so.1...done.
Loaded symbols for /usr/lib/libc.so.1
Reading symbols from /usr/lib/libdl.so.1...done.
Loaded symbols for /usr/lib/libdl.so.1
Reading symbols from /usr/lib/libmp.so.2...done.
Loaded symbols for /usr/lib/libmp.so.2
Reading symbols from 
/usr/platform/SUNW,UltraAX-i2/lib/libc_psr.so.1...done.
Loaded symbols for /usr/platform/SUNW,UltraAX-i2/lib/libc_psr.so.1
#0  0xff1a04f8 in _libc_kill () from /usr/lib/libc.so.1
(gdb) bt
#0  0xff1a04f8 in _libc_kill () from /usr/lib/libc.so.1
#1  0xff136d18 in abort () from /usr/lib/libc.so.1
#2  0x0001e978 in sigsegv_handler (signum=0) at sig.c:57
#3  <signal handler called>
(gdb)
quoted from Henrik Størner
---
On the display, hobbitd_client stays blinking red. How can I get rid
of that?
Ee. Doesn' work:

/server/bin/bb 127.0.0.1 "drop saileri.imada.sdu.dk  hobbitd_client"

hobbitd_client is still blinking RED :( 
quoted from Henrik Størner
http://www.hswn.dk/hobbit/help/hobbit-tips.html#droptest
2. bbd is constantly PURPLE
In bb-services, it is defined as:
[bbd]
   send "dummy"
   port 1984
so in fact it tests hobbitd-but why it is purple?
Hobbitd is OK.
Because the bbd network test is not being executed for this host. Check
your bb-hosts file, it must have a "bbd" tag defined for your hobbit
server.
No, there is not! ('cat bb-hosts | grep bbd' no output)
But during hobbit server installation, there was old bb directory, and bbd 
running - which has been deleted and stopped since then.
quoted from Longina Przybyszewska

Longina

--
Longina Przybyszewska, system programmer
Dept. of Math. & Comp. Sci. - IMADA
University of Southern Denmark, Odense
Campusvej 55,DK-5230 Odense M, Denmark

tel: +XX XXXX XXXX - http://www.imada.sdu.dk         email: 
user-db0a93c0e294@xymon.invalid
--