[hobbit] Client Data not showing up

Snyder, Howard HS3082 at att.com
Thu Feb 7 18:07:49 CET 2008


Here are the contents of the log files:
more clientlaunch.log
2008-02-07 07:34:05 hobbitlaunch starting
2008-02-07 07:34:05 Loading tasklist configuration from /export/home/hobbit/client/etc/clientlaunch.cfg

Contents of /export/home/hobbit/client/etc/clientlaunch.cfg:
more /export/home/hobbit/client/etc/clientlaunch.cfg
#
# The clientlaunch.cfg file is loaded by "hobbitlaunch".
# It controls which of the Hobbit client-side modules to run, 
# (both the main client "hobbitclient.sh" and any client-side
# extensions); how often, and with which parameters, options 
# and environment variables.
#
# Note: On the Hobbit *server* itself, this file is normally 
#       NOT used. Instead, both the client- and server-tasks
#       are controlled by the hobbitlaunch.cfg file.
#

# msgcache is used for passive clients, that cannot connect
# directly to the Hobbit server. This is not the default
# setup, so this task is normally disabled.
[msgcache]
        DISABLED
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/bin/msgcache --no-daemon --pidfile=$HOBBITCLIENTHOME/logs/msgcache.pid
        LOGFILE $HOBBITCLIENTHOME/logs/msgcache.log

# The main client task
[client]
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh --local
        LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
        INTERVAL 5m

# ORCA data collector. This is an experimental add-on module,
# the data sent by this module are not processed by Hobbit 4.2.
[orcadata]
        DISABLED
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/bin/orcahobbit --orca=/usr/local/orca/orcallator
        LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
        INTERVAL 5m


more hobbitclient.log
2008-02-07 07:34:12 Failed to get a message, terminating

Results of the bb test.
./bb --debug 10.184.16.150 ping
2008-02-07 12:02:33 Transport setup is:
2008-02-07 12:02:33 bbdportnumber = 1984
2008-02-07 12:02:33 bbdispproxyhost = NONE
2008-02-07 12:02:33 bbdispproxyport = 0
2008-02-07 12:02:33 Recipient listed as '10.184.16.150'
2008-02-07 12:02:33 Standard BB protocol on port 1984
2008-02-07 12:02:33 Will connect to address 10.184.16.150 port 1984
2008-02-07 12:02:33 Connect status is 0
2008-02-07 12:02:33 Sent 4 bytes
2008-02-07 12:02:33 Read 14 bytes
hobbitd 4.2.0
2008-02-07 12:02:33 Closing connection

Thank you,
Howard Snyder
hs3082 at att.com  
SR Network Control Engineer
Network Services
404-531-5325
 
This email, and any attachments, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. It is the property of Cingular Wireless and its Affiliates. If you are not the intended recipient of this email, you are hereby notified that any dissemination, distribution or copying of this email, any attachments thereto, and any use of the information contained is strictly prohibited. If you have received this email in error, please notify me at 404.531.5325 and permanently delete the original and any copy thereof.
 
For login requests and password resets, you will need to open a request on the "My Logins" website:

https://nslogins.edc.cingular.net/login.cfm?CFID=13246&CFTOKEN=41726264

For OSS problems:
DL-MNOC-OSS Adjunct
DL-MNOC-OSS Siemens
DL-MNOC-OSS Nortel
DL-MNOC-OSS Nokia
DL-MNOC-OSS Lucent
DL-MNOC-OSS Ericsson





-----Original Message-----
From: Henrik Stoerner [mailto:henrik at hswn.dk] 
Sent: Thursday, February 07, 2008 11:30 AM
To: hobbit at hswn.dk
Subject: Re: [hobbit] Client Data not showing up

On Thu, Feb 07, 2008 at 09:59:34AM -0500, Snyder, Howard wrote:
> 
> Trying 10.184.16.150...
> Connected to 10.184.16.150.
> Escape character is '^]'.
> Connection to 10.184.16.150 closed by foreign host.

There should be a delay (about 30 seconds, if memory serves me right)
before the connection is closed - that is how long Hobbit will wait for
data to be sent from the client.

The "bb" utility from the Hobbit client really is the best way to do the
connection test - run
   bb IP-OF-HOBBIT-SERVER ping
and it should respond with the version number of your Hobbit server. Add
a --debug option just after the "bb" command for some more detail.

If you can connect, but the bb-ping test fails, then there are a couple
of possibilities:

1) The IP-address you're using is wrong
2) There's a firewall or proxy which blocks port 1984
3) The Hobbit daemon restricts what IP-adresses it will talk to
   (the --status-senders option to hobbitd in hobbitlaunch.cfg)

Probably something else I just cannot think of right now ...



Regards,
Henrik


To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk





More information about the Xymon mailing list