[App_rpt-users] rpt_extnodes not updating...

Ramesh Dhami (VA3UV) Ramesh at va3uv.com
Sat Aug 22 16:53:41 UTC 2009


Stephen Rodgers wrote:

> rpt_extnodes-temp should never show up. And the fact that it is 0 length
>  indicates that it is likely that the resolver on your node may be
> inoperative. Check to make sure FQDN's resolve on these systems.
> 

<-- Hi Steve;  Node 2200 is in a hospital DC, using their DNS; I just 
logged in and ping'd a few FQDN's and they all resolved perfectly.

Further, after posting my note this morning, I went into the rpt.conf 
file on 2200 and added 2461 to the list of nodes that are allowed to 
connect - i.e., a manual entry at the bottom of the file, and used the 
FQDN for 2461 (not the IP addr), and after that I was able to 
successfully connect 2461 to 2200.

So I don't think it is a DNS issue... esp., since Jon (RQ) is seeing 
this issue independently on a couple of his nodes.

Cheers,

Ramesh.



More information about the App_rpt-users mailing list