Hobbit client 4.2 running in local mode - FILE, LOG and DIR tests
Hi again
I'm using a Hobbit 4.2 client (from latest snapshot) with the "--local" flag in ~client/etc/clientlaunch.cfg
Here's my ~client/etc/localclient.cfg :
DEFAULT UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97 CLOCK 3600 PROC snmpd 1 1 yellow PROC /usr/sbin/apache2 10 50 red PORT "LOCAL=%([.:]80)$" state=LISTEN TEXT=HTTP PORT "LOCAL=%([.:]22)$" state=ESTABLISHED max=20 color=yellow TRACK=ssh "TEXT=SSH logins" DIR /home/hobbituser red SIZE<10000 FILE /var/log/apache2/access_log red SIZE<100M LOG /var/log/apache2/error_log WARNING COLOR=yellow
Everything works but the FILE, DIR and LOG tests. I get "The client did not report any logfile data" and "No files checked".
I saw that commentary :
#NB: The directories you wish to monitor must be listed in a "dir:..."
entry in the client-local.cfg file, in order for the client to
report any data about them.
As I understand, a client in local mode sends directy its statuses to the Hobbit server, but it seems that some configuration has still to be made on the server...
Henrik, could you change this behaviour, so that a client in local mode doesn't need configuration on the server ? I'd really appreciate, as it will allow us to upgrade from Big Brother Unix client to Hobbit client.
Another thing, I keep getting every 5 minutes this error message in ~client/logs/hobbitclient.log :
2006-06-27 15:20:08 Failed to get a message, terminating
And the clientupdate command doesn't return anything :
$ ~client/bin/clientupdate --level
$
Thanks !
--
Frédéric Mangeant
Steria EDC Sophia-Antipolis
On Tue, Jun 27, 2006 at 03:30:41PM +0200, Fr?d?ric Mangeant wrote:
Hi again
I'm using a Hobbit 4.2 client (from latest snapshot) with the "--local" flag in ~client/etc/clientlaunch.cfg
Everything works but the FILE, DIR and LOG tests. I get "The client did not report any logfile data" and "No files checked".
I saw that commentary :
#NB: The directories you wish to monitor must be listed in a "dir:..."
entry in the client-local.cfg file, in order for the client to
report any data about them.
As I understand, a client in local mode sends directy its statuses to the Hobbit server, but it seems that some configuration has still to be made on the server...
The local-mode client is not very well documented.
Your FILE, DIR and LOG checks fail because the client-side utilities don't know what to check. Normally they would receive this information from the Hobbit server and store it locally in the $BBTMP/logfetch.$MACHINEDOTS.cfg directory. But since you're running in local mode that does not happen, and the end result is that you have none of these checks active.
So what you need to do basically is to put the "dir:..." etc lines
into the file ~hobbit/client/tmp/logfetch.uname -n.cfg
I'd really appreciate, as it will allow us to upgrade from Big Brother Unix client to Hobbit client.
I'm trying to make the local-mode client so difficult to configure that you'll just give up and use the server-side config :-))
Another thing, I keep getting every 5 minutes this error message in ~client/logs/hobbitclient.log :
2006-06-27 15:20:08 Failed to get a message, terminating
Hmm ... it's hobbitd_client complaining. Don't know quite why, I'll see if I can work it out.
And the clientupdate command doesn't return anything :
$ ~client/bin/clientupdate --level
It shouldn't, unless you have configured a "clientversion:..." setting in the client-local.cfg file (in your case: the ~hobbit/client/tmp/logfetch.HOSTNAME.cfg file). But if you don't want to fetch the client configuration from the server, I really wonder why you'd want to fetch the whole client package remotely ... ?
Regards, Henrik
Henrik Stoerner a écrit :
The local-mode client is not very well documented. Your FILE, DIR and LOG checks fail because the client-side utilities don't know what to check. Normally they would receive this information from the Hobbit server and store it locally in the $BBTMP/logfetch.$MACHINEDOTS.cfg directory. But since you're running in local mode that does not happen, and the end result is that you have none of these checks active.
So what you need to do basically is to put the "dir:..." etc lines into the file ~hobbit/client/tmp/logfetch.
uname -n.cfg
Thanks, it works.
Now I have another question :-)
My main idea is to deploy the Hobbit client (in local mode) by providing tar files for every Unix flavor, with the less configuration possible on the Hobbit server. Would it be possible to either :
- handle the content of the ~client/etc/localclient.cfg file, including DIR, FILE and LOG when running in local mode, or
- handle ~client/tmp/logfetch.localhost.cfg instead of
~client/tmp/logfetch.
uname -n.cfg ?
I'm trying to make the local-mode client so difficult to configure that you'll just give up and use the server-side config :-))
I'd like to use it, but people here have been using Big Brother clients (ie. locally confugured) for years...
It shouldn't, unless you have configured a "clientversion:..." setting in the client-local.cfg file (in your case: the ~hobbit/client/tmp/logfetch.HOSTNAME.cfg file). But if you don't want to fetch the client configuration from the server, I really wonder why you'd want to fetch the whole client package remotely ... ?
I was just trying this feature...
Regards,
--
Frédéric Mangeant
Steria EDC Sophia-Antipolis
On Tue, Jun 27, 2006 at 04:16:39PM +0200, Frédéric Mangeant wrote:
My main idea is to deploy the Hobbit client (in local mode) by providing tar files for every Unix flavor, with the less configuration possible on the Hobbit server. Would it be possible to either :
- handle the content of the ~client/etc/localclient.cfg file, including DIR, FILE and LOG when running in local mode, or
No, because the localclient.cfg file allows for regular expressions to define filenames.
- handle ~client/tmp/logfetch.localhost.cfg instead of ~client/tmp/logfetch.
uname -n.cfg ?
This one is fairly simple: Change the LOGFETCHCFG setting in ~hobbit/client/hobbitclient.sh - the default is LOGFETCHCFG=$BBTMP/logfetch.$MACHINEDOTS.cfg
Regards, Henrik
participants (2)
-
frederic.mangeant＠steria.com
-
henrik＠hswn.dk