[hobbit] purple clients problem

Longina Przybyszewska longina at imada.sdu.dk
Thu Dec 29 15:01:28 CET 2005


I have it as well defined as WorkDir: /opt/hobbit/data/rrd
in /etc/mrtg.cfg.

The point is, that clients turn on purple after reboot.
Now it drives me crazy, because more and more worksations stay PURPLE.
It can't be mrtg problem - there are some machines which stay GREEN.

I started bb on the PURPLE client in debugging mode.
It seems that on the client is everything OK:

fra hobbitclient.log
----
2005-12-29 14:55:23 Transport setup is:
2005-12-29 14:55:23 bbdportnumber = 1984
2005-12-29 14:55:23 bbdispproxyhost = NONE
2005-12-29 14:55:23 bbdispproxyport = 0
2005-12-29 14:55:23 Recipient listed as '130.225.128.14'
2005-12-29 14:55:23 Standard BB protocol on port 1984
2005-12-29 14:55:23 Will connect to address 130.225.128.14 port 1984
2005-12-29 14:55:23 Connect status is 0
2005-12-29 14:55:23 Sent 12003 bytes
2005-12-29 14:55:23 Closing connection
----

How kan I debug server side to see where is the black whole for all the 
client information?

Longina

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

tel: +45 6550 2359 - http://www.imada.sdu.dk         email: longina at imada.sdu.dk
--

On Wed, 28 Dec 2005, Rich Smrcina wrote:

> Check your MRTG configuration.  It can not write to a file due to a 
> permission problem.  I think I have mine writing to a directory that the 
> hobbit user owns (eg: /home/hobbit/...).
>
> Longina Przybyszewska wrote:
>> 
>> I have a problem with clients turning purple after reboot.
>> Client processes run, tmp/msg.txt is updated on client.
>> Display shows GREEN on conn|info|trends, and PURPLE on the rest  - 
>> cpu|disk|memory|procs.
>> 
>> I set debug option on hobbit client in hobbitlaunch.cfg -
>> but I don't quite understand output in clientdata.log:
>> 
>> CMD hobbitd_channel --channel=client --log=$BBSERVERLOGS/clientdata.log 
>> --debug hobbitd_client
>> 
>> from hobbitlaunch.log  on the server
>> ------
>> 2005-12-28 14:10:31 Task mrtg terminated, status 13
>> 2005-12-28 14:14:21 hobbitlaunch starting
>> 2005-12-28 14:14:21 Loading tasklist configuration from 
>> /opt/hobbit/server/etc/hobbitlaunch.cfg
>> 2005-12-28 14:14:21 Loading hostnames
>> 2005-12-28 14:14:21 Loading saved state
>> 2005-12-28 14:14:21 Setting up network listener on 0.0.0.0:1984
>> 2005-12-28 14:14:21 Setting up signal handlers
>> 2005-12-28 14:14:21 Setting up hobbitd channels
>> 2005-12-28 14:14:21 Setting up logfiles
>> ERROR: writing /etc/mrtg.ok.ok: Permission denied at 
>> /usr/local/bin/../lib/mrtg2/MRTG_lib.pm line 1477.
>> 2005-12-28 14:14:27 Task mrtg terminated, status 13
>> ERROR: writing /etc/mrtg.ok.ok: Permission denied at 
>> /usr/local/bin/../lib/mrtg2/MRTG_lib.pm line 1477.
>> 2005-12-28 14:19:28 Task mrtg terminated, status 13
>> ------
>> 
>> from clientdata.log
>> ------
>> 2005-12-28 14:14:11 Semaphore wait aborted: Interrupted system call
>> 2005-12-28 14:14:26 Setting up client channel (id=7)
>> 2005-12-28 14:14:26 calling ftok('/opt/hobbit/server',7)
>> 2005-12-28 14:14:26 ftok() returns: 0x7004344
>> 2005-12-28 14:14:26 shmget() returns: 0x1712
>> -----
>> 
>> What test should I make to find out what is wrong?
>> 
>> Thanks in advance for any ideas!
>> 
>> 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: +45 6550 2359 - http://www.imada.sdu.dk         email: 
>> longina at imada.sdu.dk
>> -- 
>> 
>> To unsubscribe from the hobbit list, send an e-mail to
>> hobbit-unsubscribe at hswn.dk
>> 
>> 
>
> -- 
> Rich Smrcina
> VM Assist, Inc.
> Main: (262)392-2026
> Cell: (414)491-6001
> Ans Service:  (360)715-2467
> rich.smrcina at vmassist.com
>
> Catch the WAVV!  http://www.wavv.org
> WAVV 2006 - Chattanooga, TN - April 7-11, 2006
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
>
>



More information about the Xymon mailing list