I ran through the series of uname & hostname commands you suggest, and all appear to return correct values on both dev-1-dist1 and dev-1-dist2.
I'm not sure how these commands are relevant, though. uname & hostname will report the name of the local machine, but my problem seems to be gmond on dev-1-dist1 not reporting a hostname for dev-1- dist2, even though reverse DNS for dev-1-dist2's IP address appears to be set up correctly. If this has been addressed in the archives, could someone steer me towards some relevant posts? I've been looking but not found anything yet. thanks, alex On Aug 2, 2010, at 9:29 AM, Peter Senna Tschudin wrote: > Hi Alex, > > Setting up hostname and domain is not a simple task because there is > more than one way of doing it. > > To check your hostname and domain, you need to run: > > uname -n > hostname -a > hostname -s > hostname -d > hostname -f > hostname > > If all these commands return the correct values, then the hostname and > domain are configured correctly. > > Source: > http://www.debianadmin.com/change-hostname-or-server-name-of-a-linux-machine.html > > Peter > > > > On Mon, Aug 2, 2010 at 11:19 AM, Alex Dean <[email protected]> wrote: >> >> On Jul 30, 2010, at 11:27 AM, Rick Cobb wrote: >> >>> It'll do a reverse lookup on the IP address the metric packet came >>> from. Names in the configuration files are irrelevant; if, for >>> example, your packet is routed on a different interface than you >>> expect, the host will be named after whatever you've named that >>> interface. >> >> gmond on dev-1-dist1 shows <HOST NAME="10.0.3.31"> rather than <HOST >> NAME="dev-1-dist2.meteostar.local">. >> When I log into dev-1-dist1 and do a reverse lookup on 10.0.3.31 as >> the user running gmond, I get 'dev-1-dist2.meteostar.local'. >> >> -bash-3.2$ hostname >> dev-1-dist1.meteostar.local >> -bash-3.2$ dig -x 10.0.3.31 +short >> dev-1-dist2.meteostar.local. >> >> If gmond should display the results of a reverse-lookup, I'm not sure >> why the IP address continues to appear in the gmond XML. These >> machines have only a single IP address & ethernet interface (aside >> from the local loopback) so I don't think it's a question of packets >> traveling a different route. >> >>> >>> There are a number of email threads about this in the archives; the >>> mcast_bind parameter can be helpful, as can making sure your hosts >>> are routing the way you expect them to. >>> >> >> Thanks. I've tried several searches and not found anything relevant. >> Do you recall subject lines or dates for the posts you were >> thinking of? >> >> The machines are using unicast not multicast. >> >> alex >> >> ------------------------------------------------------------------------------ >> The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://p.sf.net/sfu/dev2dev-palm >> _______________________________________________ >> Ganglia-general mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/ganglia-general >> > > > > -- > Peter Senna Tschudin > [email protected] > gpg id: 48274C36 > ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
