yemi- i'm sorry but i think i might have led you astray. i've thought about this more and realized.. gmond uses multicast loopback to get it's own data. the means if you set up gmond as _both_ "deaf" and "mute", it will do nothing accept collect metric information and never send it or save it.
it would take some minor code changes to make gmond work in simultaneous "deaf" and "mute" mode. i'm sorry but ganglia 2.x relies on multicast for efficient group messaging. we are definitely going to remove the reliance on multicast (only) in the future but i know that doesn't help you now. can you try setting your multicast group to "127.0.0.1" and running without "deaf" and "mute" mode set and see what happens? i doubt it will work but it's worth a try (i think you'll get an error message that 127.0.0.1 is not a valid multicast address). let me know what happens. -matt On Wed, 2004-01-28 at 17:31, Adesanya, Adeyemi wrote: > > if you hate multicast altogether for some reason, you can get > > around that too. > > > > set every gmond that you have to be both "deaf" and "mute". > > then every gmond running on every host will only know about > > itself. then use gmetad to pull all the data for your > > cluster together (gmetad uses a TCP connection to the data > > port of each gmond). you will need to manually specify every > > host in your cluster in the /etc/gmetad.conf as a data source. > > > > hope this helps. > > > > good luck! > > -matt > > > > Matt, > > I just tried setting my gmond to both "deaf" and "mute". No joy....my gmetad > only appears to get data from the gmond when "deaf" and "mute" are both off. > Is anyone successfully using the technique described by Matt? I must be > screwing up somewhere. > > ---- > Yemi -- mobius strippers never show you their backside pgp fingerprint A7C2 3C2F 8445 AD3C 135E F40B 242A 5984 ACBC 91D3
signature.asc
Description: This is a digitally signed message part
