Running logfetch 'by hand'
list Andrew Jackson
Hi, First, thanks for hobbit. It is making my life much easier. I'm trying to run logfetch by hand as it were. It takes two files logfetch.<machine>.cfg and logfetch.<machine>.status as arguments. I can see that logfetch.<machine>.cfg is generated when you submit data to the hobbit server but I can't find out where the logfetch.<machine>.status file is generated. Any help gratefully received! Thank Andy J. . This email is only intended for the person to whom it is addressed and may contain confidential information. If you have received this email in error, please notify the sender and delete this email which must not be copied, distributed or disclosed to any other person. Unless stated otherwise, the contents of this email are personal to the writer and do not represent the official view of Ordnance Survey. Nor can any contract be formed on Ordnance Survey's behalf via email. We reserve the right to monitor emails and attachments without prior notice. Thank you for your cooperation. Ordnance Survey Romsey Road Southampton SO16 4GU Tel: XXX XXXX XXXX http://www.ordnancesurvey.co.uk
list Andrew Jackson
Hi, Just thought I'd raise this up again. What I am trying to do is monitor a few machines outside our firewall. I am firing off hobbitclient-<OS>.sh using ssh from the hobbit server then submitting the output from the hobbit server like the suggestion in the discussion on agentless clients. Unlike the agentless client example I have installed the hobbit client on the target machine and fire off the hobbitclient-<OS>.sh by using a command associated with the ssh key being used for access. In the agentless client discussion the output from the data submission which is used as the configuration file for logfetch is discarded. I can see it being generated in hobbitclient.sh when the client submits it's own data. I know I would have to get this file back to the client if I wanted log monitoring on my systems outside the firewall. What I can't find is where the logfetch status file (second argument for logfetch in hobbitclient-<OS>.sh) comes from or is updated. I'm probably being stupid but I have looked through the scripts fairly carefully and can't find any reference to the logfetch status file except the environment variable giving it's path. Is there anyone who can point me in the right direction for the logfetch status file or should I resign myself to not having log monitoring on machines outside my firewall. Thanks again Andy J.
▸
From: Andrew Jackson [mailto:user-04af723659f5@xymon.invalid] Sent: 08 September 2006 11:29 To: user-ae9b8668bcde@xymon.invalid Subject: [hobbit] Running logfetch 'by hand' Hi, First, thanks for hobbit. It is making my life much easier. I'm trying to run logfetch by hand as it were. It takes two files logfetch.<machine>.cfg and logfetch.<machine>.status as arguments. I can see that logfetch.<machine>.cfg is generated when you submit data to the hobbit server but I can't find out where the logfetch.<machine>.status file is generated. Any help gratefully received! Thank Andy J. . This email is only intended for the person to whom it is addressed and may contain confidential information. If you have received this email in error, please notify the sender and delete this email which must not be copied, distributed or disclosed to any other person. Unless stated otherwise, the contents of this email are personal to the writer and do not represent the official view of Ordnance Survey. Nor can any contract be formed on Ordnance Survey's behalf via email. We reserve the right to monitor emails and attachments without prior notice. Thank you for your cooperation. Ordnance Survey Romsey Road Southampton SO16 4GU Tel: XXX XXXX XXXX http://www.ordnancesurvey.co.uk . This email is only intended for the person to whom it is addressed and may contain confidential information. If you have received this email in error, please notify the sender and delete this email which must not be copied, distributed or disclosed to any other person. Unless stated otherwise, the contents of this email are personal to the writer and do not represent the official view of Ordnance Survey. Nor can any contract be formed on Ordnance Survey's behalf via email. We reserve the right to monitor emails and attachments without prior notice. Thank you for your cooperation. Ordnance Survey Romsey Road Southampton SO16 4GU Tel: XXX XXXX XXXX http://www.ordnancesurvey.co.uk
list Henrik Størner
(this message was eaten by my spamfilter for some odd reason)
▸
On Mon, Sep 11, 2006 at 12:38:16PM +0100, Andrew Jackson wrote:Just thought I'd raise this up again. What I am trying to do is monitor a few machines outside our firewall. I am firing off hobbitclient-<OS>.sh using ssh from the hobbit server then submitting the output from the hobbit server like the suggestion in the discussion on agentless clients. Unlike the agentless client example I have installed the hobbit client on the target machine and fire off the hobbitclient-<OS>.sh by using a command associated with the ssh key being used for access. In the agentless client discussion the output from the data submission which is used as the configuration file for logfetch is discarded. I can see it being generated in hobbitclient.sh when the client submits it's own data. I know I would have to get this file back to the client if I wanted log monitoring on my systems outside the firewall. What I can't find is where the logfetch status file (second argument for logfetch in hobbitclient-<OS>.sh) comes from or is updated.
The second file is maintained by logfetch itself. It contains the locations into the various logfiles that logfetch has processed in earlier runs. Instead of ssh'ing into the box, perhaps you could use the msgcache/hobbitfetch utilities ? That lets you run the normal client on a box together with msgcache, and then hobbitfetch contacts the client to pick up the data. Log monitoring does work normally with that setup. Regards, Henrik
list Andrew Jackson
Thanks Henrik, I'll look at msgcache/hobbitfetch. I got the logfetch going at the end of last week after leaving it for a while. The info I needed was, of course, in the man page. I was trying to think of a nice way to say that 'I'm stupid and should have read the man page' to close the question when I picked up your reply Monday morning. I've obviously been fighting unix systems far too long and should take up knitting. Thanks again. Andy J.
▸
-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: 08 October 2006 11:09
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Running logfetch 'by hand'
(this message was eaten by my spamfilter for some odd reason)
On Mon, Sep 11, 2006 at 12:38:16PM +0100, Andrew Jackson wrote:Just thought I'd raise this up again. What I am trying to do is monitor a few machines outside our firewall. I am firing off hobbitclient-<OS>.sh using ssh from the hobbit server then submitting the output from the hobbit server like the suggestion in the discussion on agentless clients. Unlike the agentless client example I have installed the hobbit client on the target machine and fire off the hobbitclient-<OS>.sh by using a command associated with the ssh key being used for access. In the agentless client discussion the output from the data submission which is used as the configuration file for logfetch is discarded. I can see it being generated in hobbitclient.sh when the client submits it's own data. I know I would have to get this file back to the client if I wanted log monitoring on my systems outside the firewall. What I can't find is where the logfetch status file (second argument for logfetch in hobbitclient-<OS>.sh) comes from or is updated.
The second file is maintained by logfetch itself. It contains the locations into the various logfiles that logfetch has processed in earlier runs. Instead of ssh'ing into the box, perhaps you could use the msgcache/hobbitfetch utilities ? That lets you run the normal client on a box together with msgcache, and then hobbitfetch contacts the client to pick up the data. Log monitoring does work normally with that setup. Regards, Henrik . This email is only intended for the person to whom it is addressed and may contain confidential information. If you have received this email in error, please notify the sender and delete this email which must not be copied, distributed or disclosed to any other person. Unless stated otherwise, the contents of this email are personal to the writer and do not represent the official view of Ordnance Survey. Nor can any contract be formed on Ordnance Survey's behalf via email. We reserve the right to monitor emails and attachments without prior notice. Thank you for your cooperation. Ordnance Survey Romsey Road Southampton SO16 4GU Tel: XXX XXXX XXXX http://www.ordnancesurvey.co.uk