Hi Henrik
Sorry to ask this directly, hopefully you can help me. I have asked this of the group a couple of times but have not had a suitable answer back.
I am trying to use the output received from hobbitd when issuing the bb ghostlist command. The command reports correctly, but after modifying the bb-hosts file, ghostlist continues to report ghosts. I need to do a full restart of hobbit to get hobbitd reporting correctly.
I started digging through the source tonight but I have to admit that I just can't understand C well enough. hobbitd knows the bb-hosts file has been updated because the host appears on the webpage, but ghostlist still reports it incorrectly.
Is a restart the only way to resolve this? Could I HUP a process to fix it?
Many thanks
Phil
-- Tel: 0400 466 952 Fax: 0433 123 226 email: philwild AT gmail.com
Could it be that the clients are reporting as a name different than the name you have in the bb-hosts file?
If yes, then check out the CLIENT: directive for the bb-hosts file. I have had this happen to me a couple times.
Phil Wild wrote:
Hi Henrik
Sorry to ask this directly, hopefully you can help me. I have asked this of the group a couple of times but have not had a suitable answer back.
I am trying to use the output received from hobbitd when issuing the bb ghostlist command. The command reports correctly, but after modifying the bb-hosts file, ghostlist continues to report ghosts. I need to do a full restart of hobbit to get hobbitd reporting correctly.
I started digging through the source tonight but I have to admit that I just can't understand C well enough. hobbitd knows the bb-hosts file has been updated because the host appears on the webpage, but ghostlist still reports it incorrectly.
Is a restart the only way to resolve this? Could I HUP a process to fix it?
Many thanks
Phil
No, The name is the same. A full restart of hobbit resolves the issue until a new ghost comes along. Once that is added in, the same thing happens once again until another restart is performed.
Phil
2008/5/24 Bill Arlofski <waa-hobbitml at revpol.com>:
Could it be that the clients are reporting as a name different than the name you have in the bb-hosts file?
If yes, then check out the CLIENT: directive for the bb-hosts file. I have had this happen to me a couple times.
Phil Wild wrote:
Hi Henrik
Sorry to ask this directly, hopefully you can help me. I have asked this of the group a couple of times but have not had a suitable answer back.
I am trying to use the output received from hobbitd when issuing the bb ghostlist command. The command reports correctly, but after modifying the bb-hosts file, ghostlist continues to report ghosts. I need to do a full restart of hobbit to get hobbitd reporting correctly.
I started digging through the source tonight but I have to admit that I just can't understand C well enough. hobbitd knows the bb-hosts file has been updated because the host appears on the webpage, but ghostlist still reports it incorrectly.
Is a restart the only way to resolve this? Could I HUP a process to fix it?
Many thanks
Phil
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Tel: 0400 466 952 Fax: 0433 123 226 email: philwild AT gmail.com
On Fri, May 23, 2008 at 10:06:59PM +0800, Phil Wild wrote:
I am trying to use the output received from hobbitd when issuing the bb ghostlist command. The command reports correctly, but after modifying the bb-hosts file, ghostlist continues to report ghosts. I need to do a full restart of hobbit to get hobbitd reporting correctly.
hobbitd reloads the bb-hosts file every 10 minutes, or if you send a HUP signal to the hobbitd process. Hosts will remain on the ghostlist until no reports have been received with ghost hostname for 10 minutes.
So if you have a ghost reporting at 12:00, and you modify the bb-hosts file at 12:01, then the host reports again at 12:05, the bb-hosts file is reloaded at 12:11, and the ghost entry expires at 12:15. So it may take up to 15 minutes before the ghostlist entry disappears.
I started digging through the source tonight but I have to admit that I just can't understand C well enough. hobbitd knows the bb-hosts file has been updated because the host appears on the webpage, but ghostlist still reports it incorrectly.
Note: the fact that the host appears on the webpage does NOT mean hobbitd knows about it. The webpage is generated by another task, and until hobbitd learns about the new hostname, it will just show up with no status columns.
Regards. Henrik
On Mon, May 26, 2008 at 7:30 AM, Henrik Stoerner <henrik at hswn.dk> wrote:
On Fri, May 23, 2008 at 10:06:59PM +0800, Phil Wild wrote:
I am trying to use the output received from hobbitd when issuing the bb ghostlist command. The command reports correctly, but after modifying the bb-hosts file, ghostlist continues to report ghosts. I need to do a full restart of hobbit to get hobbitd reporting correctly.
hobbitd reloads the bb-hosts file every 10 minutes, or if you send a HUP signal to the hobbitd process. Hosts will remain on the ghostlist until no reports have been received with ghost hostname for 10 minutes.
So if you have a ghost reporting at 12:00, and you modify the bb-hosts file at 12:01, then the host reports again at 12:05, the bb-hosts file is reloaded at 12:11, and the ghost entry expires at 12:15. So it may take up to 15 minutes before the ghostlist entry disappears.
I started digging through the source tonight but I have to admit that I just can't understand C well enough. hobbitd knows the bb-hosts file has been updated because the host appears on the webpage, but ghostlist still reports it incorrectly.
Note: the fact that the host appears on the webpage does NOT mean hobbitd knows about it. The webpage is generated by another task, and until hobbitd learns about the new hostname, it will just show up with no status columns.
I did this just one time:
server/bin/bb localhost "status server,domain,com.bogus green date"
server.domain.com has never have existed in my bb-hosts file. It showed up in the Ghost Clients web page for 5 minutes. It also showed up in the ghostlist generated via this command:
server/bin/bb localhost ghostlist
Several days later, the above command was still showing this:
server.domain.com|127.0.0.1|1211218983This was with the Jan 25 2008 4.3.0 snapshot.
Ralph Mitchell
Hi Henrik/Ralph,
On my system running 4.2 with all in one patch...
./server/bin/bb 10.1.50.4 ghostlist bar|10.1.50.4|1211944491 ho|10.1.50.4|1211944491 hum|10.1.50.4|1211944491 zulu.XXXX.com.au|10.1.50.4|1211944491
So all the above is good....
Just to clarify, hosts bar, ho, hum and zulu are all sending a message to hobbitd every five minutes. Only one test is being sent, this is a test titled alerts. There is no cpu, memory or any other test being sent.
And just to confirm, grep zulu ./server/etc/bb-hosts returns nothing...
I then add the following line to bb-hosts
0.0.0.0 zulu.XXXX.com.au
grep zulu ./server/etc/bb-hosts now returns 0.0.0.0 zulu.XXXX.com.au
I now wait >10 minutes (only because I am trying to multi-task other work)... The host appears on the bb.html page and I can see a yellow dot for the test that is being sent every five minutes to trigger it as a ghost... I can click on the dot and see the message, including an rrd graph of the data received. So far so good...
I now run...
./server/bin/bb 10.1.50.4 hobbitdboard | grep zulu zulu.XXXX.com.au|trends|green||0|0|0|0|0||0| zulu.XXXX.com.au|info|green||0|0|0|0|0||0| zulu.XXXX.com.au|conn|green|OrdAstLe|1211945995|1211946296|1211948096|0|0| 10.1.50.4|-1|green <!-- [flags:OrdAstLe] --> Wed May 28 11:44:55 2008 conn ok zulu.XXXX.com.au|alerts|yellow||1211945994|1211946295|1211948095|0|0| 10.1.50.4|82688|yellow Wed May 28 11:44:55 WST 2008
So from the above, I would assume that it would now no longer be listed as a ghost...
Just to be sure, I will wait another >15 minutes.... And then...
./server/bin/bb 10.1.50.4 ghostlist bar|10.1.50.4|1211946596 ho|10.1.50.4|1211946596 hum|10.1.50.4|1211946596 zulu.XXXX.com.au|10.1.50.4|1211945699
It is still there...
I give it another 10 minutes and then I restart hobbit
su - hobbit -c "/opt/hobbit/server/hobbit.sh restart"
wait 10 minutes...
And re-run
./server/bin/bb 10.1.50.4 ghostlist bar|10.1.50.4|1211947632 ho|10.1.50.4|1211947632 hum|10.1.50.4|1211947632 zulu has gone...
This email is long enough, but if I now reverse the process and remove zulu from the bb-hosts file, zulu will never become a ghost again until after the next restart, even though hobbitdboard no longer shows it in its list.
Can I assume this is a bug/feature?
Cheers
Phil
2008/5/28 Ralph Mitchell <ralphmitchell at gmail.com>:
On Mon, May 26, 2008 at 7:30 AM, Henrik Stoerner <henrik at hswn.dk> wrote:
On Fri, May 23, 2008 at 10:06:59PM +0800, Phil Wild wrote:
I am trying to use the output received from hobbitd when issuing the bb ghostlist command. The command reports correctly, but after modifying the bb-hosts file, ghostlist continues to report ghosts. I need to do a full restart of hobbit to get hobbitd reporting correctly.
hobbitd reloads the bb-hosts file every 10 minutes, or if you send a HUP signal to the hobbitd process. Hosts will remain on the ghostlist until no reports have been received with ghost hostname for 10 minutes.
So if you have a ghost reporting at 12:00, and you modify the bb-hosts file at 12:01, then the host reports again at 12:05, the bb-hosts file is reloaded at 12:11, and the ghost entry expires at 12:15. So it may take up to 15 minutes before the ghostlist entry disappears.
I started digging through the source tonight but I have to admit that I just can't understand C well enough. hobbitd knows the bb-hosts file has been updated because the host appears on the webpage, but ghostlist still reports it incorrectly.
Note: the fact that the host appears on the webpage does NOT mean hobbitd knows about it. The webpage is generated by another task, and until hobbitd learns about the new hostname, it will just show up with no status columns.
I did this just one time:
server/bin/bb localhost "status server,domain,com.bogus green
date"server.domain.com has never have existed in my bb-hosts file. It showed up in the Ghost Clients web page for 5 minutes. It also showed up in the ghostlist generated via this command:
server/bin/bb localhost ghostlist
Several days later, the above command was still showing this:
server.domain.com|127.0.0.1|1211218983This was with the Jan 25 2008 4.3.0 snapshot.
Ralph Mitchell
-- Tel: 0400 466 952 Fax: 0433 123 226 email: philwild AT gmail.com
participants (4)
-
henrik＠hswn.dk
-
philwild＠gmail.com
-
ralphmitchell＠gmail.com
-
waa-hobbitml＠revpol.com