Re: [hobbit] purple clients problem

[Longina Przybyszewska <longina (at) imada.sdu.dk>]

hi again,
I did the test, and I could see that the purple machines were not polled 
by the server!
So, I made another test, where in  bb-hosts file were _only _ servers 
and purple worksations . All  purple workstations turned green now.
The one failed to show (cpu|disk|memory|procs) -  and only showed green on 
network tests (conn|info|trends).
Hobbitlaunch run on that workstation, and pickuped data to ../tmp/msg.txt
regularly.

Now, I am back to my big bb-hosts file with about 80 computers - and 
about 25 workstations stopped  to show (cpu|disk|memory|procs).
They are not polled by a server. They pickup data to ../tmp/msg.txt
regularly and say that they contact the server  and everything is OK.

hobbitd_client runs with --debug option, and the clientdata.log says:
----
2006-01-09 11:35:17 Semaphore wait aborted: Interrupted system call
2006-01-09 11:35:49 Setting up client channel (id=7)
2006-01-09 11:35:49 calling ftok('/opt/hobbit/server',7)
2006-01-09 11:35:49 ftok() returns: 0x7004344
2006-01-09 11:35:49 shmget() returns: 0x1A32
2006-01-09 11:52:20 Semaphore wait aborted: Interrupted system call
2006-01-09 11:52:45 Setting up client channel (id=7)
2006-01-09 11:52:45 calling ftok('/opt/hobbit/server',7)
2006-01-09 11:52:45 ftok() returns: 0x7004344
2006-01-09 11:52:45 shmget() returns: 0x1A96
----

Server is a sparc/Solaris9.
Could it be resource/timing problem on the server?


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
--

On Thu, 29 Dec 2005, Henrik Stoerner wrote:

> On Thu, Dec 29, 2005 at 03:01:28PM +0100, Longina Przybyszewska wrote:
> > 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?
>
> On the server, login as the hobbit user and run
>    bbcmd hobbitd_channel --channel=client cat
>
> When the client sends a message, you should see it dumped to the screen.
> If it does, then at least the client message arrives OK on the Hobbit
> server, and the server recognizes the client hostname OK.
>
> If you don't see any such message, then the hostname that the client
> reports is not listed in bb-hosts - you can see the "ghost" hostname
> in the status for the hobbit servers' "hobbitd" column.
>
> The first line you see when dumping the client message should look like
> this:
>   @@client#24|1135865239.108541|127.0.0.1|localhost|linux
> where "localhost" is the hostname, and "linux" is the operating system
> that the client reports. The OS must be one of the recognized OS'es:
> solaris, sunos, linux, aix, hp-ux, freebsd etc.
>
> If you get that far and still haven't found the problem, add the "--debug"
> option to the hobbitd_client command in hobbitlaunch.cfg, and check the
> clientdata.log logfile for any errors.
>
>
> Regards,
> Henrik
>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe (at) hswn.dk