logfile monitoring with client side configuration?
Hi,
I just installed the new 4.2-beta server and client. It seems that the logfile monitoring is not working when I install a hobbit client with client side configuration.
On the client I ran "./configure --client" and selected client side configuration. The clientlaunch.cfg looks like this:
[client] ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh --local ...
On the server I specified three logfiles to monitor in the client-local.cfg:
[my.client.hostname] log:/var/log/messages:10240 log:/var/log/dsmsched.log:10240 log:/var/log/dsmerror.log:10240
But nothing happens. The logfiles are not touched and there's no logfetch.cfg file in the client's tmp directory. When I configure the client with server side configuration it works.
Can I use logfile monitoring with client side configuration?
-- Regards,
Dirk Kastens
On Tue, Jun 06, 2006 at 05:52:39PM +0200, Dirk Kastens wrote:
On the server I specified three logfiles to monitor in the client-local.cfg:
[my.client.hostname] log:/var/log/messages:10240 log:/var/log/dsmsched.log:10240 log:/var/log/dsmerror.log:10240
But nothing happens. The logfiles are not touched and there's no logfetch.cfg file in the client's tmp directory. When I configure the client with server side configuration it works.
Can I use logfile monitoring with client side configuration?
You can, but it requires a different configuration. And that isn't described anywhere, sorry.
The stuff you put into client-local.cfg on the Hobbit server is never transferred to the client when you're running with client- side configuration. So you need to take that, and put it into $BBHOME/tmp/logfetch.HOSTNAME.cfg (which is a stupid location, when you're running in client-side config mode - I'll change that to go into $BBHOME/etc/logfetch.cfg)
You need to setup the equivalent of the hobbit-clients.cfg file on the client, in $BBHOME/etc/localclient.cfg
With those two things in place, all of the client features should work.
Regards, Henrik
participants (2)
-
Dirk.Kastens@uni-osnabrueck.de
-
henrik@hswn.dk