Yeah, in --debug gmond is chirping happily about processing messages,
but the XML port is closed... I dont see any error messages about
this.

In Ganglia 2.5.x you could put hostnames in the trusted hosts (its a
simple libc lookup to do the transformation to IP - I believe I did it
once before, but dont remember the code exactly). I know people still
have trusted_hosts with names, since they are easier to deal with than
IPs, and Apache allows them in ACLs.

Other than that, its nice how g3 works seamlessly with the (relatively
unchanged) gmetad and webfrontend. I think the new config file format
is more confusing than say a <Apache Directive> option1, option2, ...
</Apache Directive> httpd.conf style, but it may be because I'm new to
it :).

-Dave

On 4/15/05, Matt Massie <[EMAIL PROTECTED]> wrote:
> i'm not sure if you can use a hostname as part of a CIDR.  we could
> modify the code to allow for that when you are dealing with hosts (mask=32).
> 
> if you change the grid.rocksclusters.org to 198.202.74.160, i think
> you'll be in business.
> 
> there should be an error message though.  have you tried to run gmond in
> debug mode?
> 
> -matt
> 
> Federico D. Sacerdoti wrote:
> > Very strange... I see the silent failures even with SElinux turned off.
> >
> > Put this at the end of your gmond.conf file, and it just causes gmond
> > to fall on its face. It may be something I'm doing over here (I hope
> > it is!)
> >
> > tcp_accept_channel {
> >         port = "8649"
> >         acl {
> >                 default="deny"
> >                 access {
> >                         ip="grid.rocksclusters.org"
> >                         mask=32
> >                         action="allow"
> >                 }
> >         }
> > }
> >
> > -Federico
> 
> --
> PGP fingerprint 'A7C2 3C2F 8445 AD3C 135E F40B 242A 5984 ACBC 91D3'
> 
>     They that can give up essential liberty to obtain a little
>        temporary safety deserve neither liberty nor safety.
>    --Benjamin Franklin, Historical Review of Pennsylvania, 1759
> 
> 
>

Reply via email to