[hobbit] monitoring of server itself

[Kauffman, Tom]

If the package(s) you are installing are properly prepared, the client code will be in /usr/lib/hobbit/client. The server startup will automatically start the client IF the client is installed on the system.

I am confused by the placement in /usr/lib; this doesn't look anything like the Linux Filesystem Hierarchy standard was followed.

-----Original Message-----
From: Johan Booysen [mailto:johan at matrix-data.co.uk]
Sent: Tuesday, August 12, 2008 7:51 AM
To: hobbit at hswn.dk
Subject: RE: [hobbit] monitoring of server itself

Ok, so I created a brand new virtual machine (RHEL5) and installed only the hobbit rpm (not the hobbit-client rpm), and it monitors itself (with no configuration changes made at all).

But this doesn't work on a physical server.

Any ideas why?

-----Original Message-----
From: Johan Booysen [mailto:johan at matrix-data.co.uk]
Sent: 12 August 2008 10:35
To: hobbit at hswn.dk
Subject: RE: [hobbit] monitoring of server itself

I spoke too soon.  Damn.  So annoying.

-----Original Message-----
From: Johan Booysen [mailto:johan at matrix-data.co.uk]
Sent: 12 August 2008 10:24
To: hobbit at hswn.dk
Subject: RE: [hobbit] monitoring of server itself

Heeheehee - I just copied over the following from the test lab server to the production server, and now the server is monitoring itself without hobbit-client being installed:

/usr/lib/hobbit/server/etc
/var/lib/hobbit

I have no idea why, but will try to figure out exactly what I did.

:)

-----Original Message-----
From: Johan Booysen [mailto:johan at matrix-data.co.uk]
Sent: 12 August 2008 09:17
To: hobbit at hswn.dk
Subject: RE: [hobbit] monitoring of server itself

Oh dear - I'm installing hobbit using the rpms which I included in a local yum repository.

When trying to install hobbit-client on the server, the result is:

yum install hobbit-client
Loading "security" plugin
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package hobbit-client.i386 0:4.2.0-1 set to be updated
--> Processing Conflict: hobbit conflicts hobbit-client
--> Processing Conflict: hobbit-client conflicts hobbit
--> Finished Dependency Resolution
Error: hobbit conflicts with hobbit-client
Error: hobbit-client conflicts with hobbit

:(

I guess I'm just going to have to take another real good look at the test lab server and see what I did to get it to monitor itself without having the client installed.  I knew I should have written it down as I went along!!

-----Original Message-----
From: Johan Booysen [mailto:johan at matrix-data.co.uk]
Sent: 12 August 2008 09:12
To: hobbit at hswn.dk
Subject: RE: [hobbit] monitoring of server itself

Thanks for the replies to my question.

That's kinda weird because on my test lab server I most definitely did not install the client - I just double-checked, and it monitored itself quite happily...

Strange, but there you go.

-----Original Message-----
From: McDonald, Dan [mailto:Dan.McDonald at austinenergy.com]
Sent: 11 August 2008 18:21
To: hobbit at hswn.dk
Subject: Re: [hobbit] monitoring of server itself

On Mon, 2008-08-11 at 17:18 +0100, Johan Booysen wrote:
> I've now installed hobbit on the production server, and added the
> clients.  Everything looks ok, but the server (defined by default as
> localhost in bb-hosts) does not seem to monitor its own cpu, disk,
> memory, ports and processes.
>
>
>
> I'm pretty sure my test lab server monitored those by default.  Or is
> there anything specific one should do on the server itself?  I may
> have confused myself...
>

You need to install (and start) the client on the server.

Check ghosts to see if it is trying to report a different name...

>
>
> Thanks.
>
>
--
Daniel J McDonald, CCIE #2495, CISSP #78281, CNX Austin Energy http://www.austinenergy.com

CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.