On 3/31/06, David Gilmore <david at stenhouseconsulting.com> wrote:
I was thinking of monitoring employee laptops, and maybe even desktops, with hobbit. I added a group to my hosts file with the DIAL tag, created a line in the hosts file 0.0.0.0 mylaptop.mydomain.local # noping. I then installed a client on the laptop and just set it to monitor the basics (CPU, Disk, Memory). I then shut down the laptop and took it home. Thirty minutes later I checked my hobbit pages from my home desktop and saw that the status of the client was set to purple. I obviously misunderstood the functionality of the DIALUP tag. Is it possible to monitor a device that would only check in a couple of times a day? I know I could set specific alerts thresholds for the laptop, but was hoping there might be a "universal" solution.
Maybe the "noping" is the problem (I'd check, but I'm not in work right now :>). Certainly the boxes I tag with "dialup" go clear when the ping check fails, not purple.
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
Ping has remained clear, but CPU, Disk, Memory, etc went purple.
Dave
-----Original Message----- From: hobbit-return-6178-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-6178-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Rob MacGregor Sent: Friday, March 31, 2006 5:03 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Monitoring a laptop
On 3/31/06, David Gilmore <david at stenhouseconsulting.com> wrote:
I was thinking of monitoring employee laptops, and maybe even desktops, with hobbit. I added a group to my hosts file
with the DIAL
tag, created a line in the hosts file 0.0.0.0 mylaptop.mydomain.local
noping. I then installed a client on the laptop and just
set it to monitor the basics (CPU, Disk, Memory). I then shut down the laptop and took it home. Thirty minutes later I checked my hobbit pages from my home desktop and saw that the status of the client was set to purple. I obviously misunderstood the functionality of the DIALUP tag. Is it possible to monitor a device that would only check in a couple of times a day? I know I could set specific alerts thresholds for the laptop, but was hoping there might be a "universal" solution.
Maybe the "noping" is the problem (I'd check, but I'm not in work right now :>). Certainly the boxes I tag with "dialup" go clear when the ping check fails, not purple.
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
On 3/31/06, David Gilmore <david at stenhouseconsulting.com> wrote:
Ping has remained clear, but CPU, Disk, Memory, etc went purple.
Version of hobbit? What OS are you running on? Exact line out of the hosts file?
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
4.1.2p1
Windows XP Pro using BB 1.08d client
Group Dialup 0.0.0.0 dsgtp43.stenhouse.local # noping
Dave
-----Original Message----- From: hobbit-return-6180-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-6180-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Rob MacGregor Sent: Friday, March 31, 2006 6:07 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Monitoring a laptop
On 3/31/06, David Gilmore <david at stenhouseconsulting.com> wrote:
Ping has remained clear, but CPU, Disk, Memory, etc went purple.
Version of hobbit? What OS are you running on? Exact line out of the hosts file?
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
On 4/1/06, David Gilmore <david at stenhouseconsulting.com> wrote:
4.1.2p1
Windows XP Pro using BB 1.08d client
Group Dialup 0.0.0.0 dsgtp43.stenhouse.local # noping
You're missing the dialup tag after the host, try:
0.0.0.0 dsgtp43.stenhouse.local # dialup
(what you've got will define a group with a name "Dialup" AFAIK)
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
Rob,
Thanks. Just made the change.
Dave
-----Original Message----- From: hobbit-return-6184-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-6184-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Rob MacGregor Sent: Saturday, April 01, 2006 3:13 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Monitoring a laptop
On 4/1/06, David Gilmore <david at stenhouseconsulting.com> wrote:
4.1.2p1
Windows XP Pro using BB 1.08d client
Group Dialup 0.0.0.0 dsgtp43.stenhouse.local # noping
You're missing the dialup tag after the host, try:
0.0.0.0 dsgtp43.stenhouse.local # dialup
(what you've got will define a group with a name "Dialup" AFAIK)
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
Ok, so that did work as planned, however, bbtest is yellow with the following
Error output: bbtest-net: Cannot resolve IP for host dsgtp43.stenhouse.local
Dave
-----Original Message----- From: hobbit-return-6184-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-6184-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Rob MacGregor Sent: Saturday, April 01, 2006 3:13 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Monitoring a laptop
On 4/1/06, David Gilmore <david at stenhouseconsulting.com> wrote:
4.1.2p1
Windows XP Pro using BB 1.08d client
Group Dialup 0.0.0.0 dsgtp43.stenhouse.local # noping
You're missing the dialup tag after the host, try:
0.0.0.0 dsgtp43.stenhouse.local # dialup
(what you've got will define a group with a name "Dialup" AFAIK)
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
On 4/2/06, David Gilmore <david at stenhouseconsulting.com> wrote:
Ok, so that did work as planned, however, bbtest is yellow with the following
Error output: bbtest-net: Cannot resolve IP for host dsgtp43.stenhouse.local
Can you normally do a lookup for it when it's offline (that is, do you use dynamic DNS for these hosts)?
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
I'll have to give that a try today. I believe the Hobbit box is configured to use the Windows DC for DNS. If it is then that could either be the problem, or the resolution. Since the Windows DC would have the last DHCP address cached in DNS it should provide resolution.
Being a Unix/Linux newbie I need to spend some more time with the MAN pages and figure out the little quirks.
Dave
-----Original Message----- From: hobbit-return-6205-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-6205-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Rob MacGregor Sent: Monday, April 03, 2006 2:11 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Monitoring a laptop
On 4/2/06, David Gilmore <david at stenhouseconsulting.com> wrote:
Ok, so that did work as planned, however, bbtest is yellow with the following
Error output: bbtest-net: Cannot resolve IP for host dsgtp43.stenhouse.local
Can you normally do a lookup for it when it's offline (that is, do you use dynamic DNS for these hosts)?
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
On 4/3/06, David Gilmore <david at stenhouseconsulting.com> wrote:
I'll have to give that a try today. I believe the Hobbit box is configured to use the Windows DC for DNS. If it is then that could either be the problem, or the resolution. Since the Windows DC would have the last DHCP address cached in DNS it should provide resolution.
Any DHCP client should release it's lease on exit (ie shutdown). This means that in a dynamic DNS setup (which you probably have) you'll find that once the client shuts down the name stops being resolvable.
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
I set it up to monitor a second laptop, collected some data, and then shut down the laptop. I have not received any bbtest errors related to the second test unit yet. I also checked the DNS setting on the Hobbit server. It was checking the W2k3 DC first, then a OS X server second. I removed the OS X server and have not seen anymore errors about resolving for my laptop.
Dave
-----Original Message----- From: hobbit-return-6222-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-6222-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Rob MacGregor Sent: Monday, April 03, 2006 2:36 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Monitoring a laptop
On 4/3/06, David Gilmore <david at stenhouseconsulting.com> wrote:
I'll have to give that a try today. I believe the Hobbit box is configured to use the Windows DC for DNS. If it is then that could either be the problem, or the resolution. Since the Windows DC would have the last DHCP address cached in DNS it should provide resolution.
Any DHCP client should release it's lease on exit (ie shutdown). This means that in a dynamic DNS setup (which you probably have) you'll find that once the client shuts down the name stops being resolvable.
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
You probably need to remove the noping, dialup will make the network tests go clear if they fail, but for disk, etc. to go clear, I _think_ they require the ping test to fail, not be clear all the time.
Thanks, Larry Barber
On 3/31/06, David Gilmore <david at stenhouseconsulting.com> wrote:
Ping has remained clear, but CPU, Disk, Memory, etc went purple.
Dave
-----Original Message----- From: hobbit-return-6178-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-6178-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Rob MacGregor Sent: Friday, March 31, 2006 5:03 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Monitoring a laptop
On 3/31/06, David Gilmore <david at stenhouseconsulting.com> wrote:
I was thinking of monitoring employee laptops, and maybe even desktops, with hobbit. I added a group to my hosts file
with the DIAL
tag, created a line in the hosts file 0.0.0.0 mylaptop.mydomain.local
noping. I then installed a client on the laptop and just
set it to monitor the basics (CPU, Disk, Memory). I then shut down the laptop and took it home. Thirty minutes later I checked my hobbit pages from my home desktop and saw that the status of the client was set to purple. I obviously misunderstood the functionality of the DIALUP tag. Is it possible to monitor a device that would only check in a couple of times a day? I know I could set specific alerts thresholds for the laptop, but was hoping there might be a "universal" solution.
Maybe the "noping" is the problem (I'd check, but I'm not in work right now :>). Certainly the boxes I tag with "dialup" go clear when the ping check fails, not purple.
-- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (3)
-
david＠stenhouseconsulting.com
-
lebarber＠gmail.com
-
rob.macgregor＠gmail.com