[OE-core] Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolution

Denys Dmytriyenko denis at denix.org
Thu Jul 14 03:04:24 UTC 2016


On Mon, Jul 11, 2016 at 09:32:09AM +0100, Richard Purdie wrote:
> On Sun, 2016-07-10 at 18:10 -0400, Denys Dmytriyenko wrote:
> > On Sun, Jul 10, 2016 at 05:35:59PM -0400, Denys Dmytriyenko wrote:
> > > Has anyone ever seen this error message:
> > > 
> > > ERROR: blah-blah do_package: Can NOT get PRAUTO, exception [Errno 
> > > -3] Temporary failure in name resolution
> > > 
> > > I'm using centralized PR Service over the network on a local
> > > subnet. I just 
> > 
> > Oh, forgot to mention - this seems to be intermittent, as it works
> > fine now. 
> > Trying to prevent it from happening again in the future.
> > 
> > 
> > > got this message on 2 different machines for 3 separate packages.
> > > Should I be 
> > > worried about it? Should I look into networking HW issues or into
> > > PR server 
> > > instance or something else? Should I switch over to using IP
> > > address instead 
> > > of FQDN and even more - use static IP? Any best practices? Thanks.
> 
> Failure in name resolution sounds like something went odd with the
> network setup. It would be the host networking stack and the general
> network setup that would be responsible for that rather than bitbake
> specifically.
> 
> I assume you're using a FQDN which needs DNS resolution from a remote
> DNS server? Any local caching of DNS?
> 
> It does sound like the DNS server became unreachable for a short period
> and there wasn't a local cache. Its also possible we resolve the name
> often enough (in many different processes) to trigger some kind of
> repeat lookup protection on a DNS server if you have a more paranoid
> security setup.
> 
> A static IP, or a static entry in hosts would likely work around the
> issue, or simply using an IP address.

Thanks, Richard! I will look into setting a static IP and/or hosts entry to 
avoid any potential DNS resolution issues in the future...

-- 
Denys



More information about the Openembedded-core mailing list