David Gore (v965-3670)
Enhanced Technology Support (ETS)
Network Management Systems (NMS)
IMPACT Transport Team Lead - SCSA, SCNA
Page: 1-800-PAG-eMCI pin 1406090
Vnet: 965-3676
*e-mail via SUSE Linux 9.3 and other open source tools.
Henrik Stoerner wrote:
On Thu, Apr 27, 2006 at 10:36:37PM +0000, David Gore wrote:
You definitely need to update the client. I'm really sorry about that,
but back in August last year I had no idea how to do the log-file
stuff, so the old client simply doesn't provide the data needed for
the log- and file-monitoring.
Ok, is there some minimum number of files I can update like only the binaries bb and hobbitlaunch?
~hobbit/client/bin/* and ~hobbit/client/runclient.sh - i.e. all of the
programs.
Henrik
Well, it is going to be very painful to update hundreds of hosts. Regardless, I have created a new instance and just modified the new instance with our previous changes. I still cannot get LOGS to work FILES. I can get to work, but perhaps I found a bug? Here is the entry:
client-local.cfg:file:/opt/app/apache/logs/access-test.log
hobbit-clients.cfg: FILE /opt/app/apache/logs/access-test.log size<2000000 COLOR=red
Here is the result when alarming:
/opt/app/apache/logs/access-test.log
File is missing
And when you click the link:
ERROR: Value too large for defined data type
I am trying to test for a file size greater than 2G. It would be very nice if the size could be represented in kilobytes, megabytes and gigabytes. K, M, and G.
Here is a LOG entry that fails (none work):
client-local.cfg:log:/opt/app/apache/logs/error-test.log:10240
hobbit-clients.cfg: LOG /opt/app/apache/logs/error-test.log MATCH="%Segmentation Fault" COLOR=red
The documentation appears out of date from your e-mail on the April 24th 21:09 GMT?