All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolution
Date: Wed, 13 Jul 2016 23:04:24 -0400	[thread overview]
Message-ID: <20160714030424.GF8521@denix.org> (raw)
In-Reply-To: <1468225929.28829.71.camel@linuxfoundation.org>

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


      reply	other threads:[~2016-07-14  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 21:35 Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolution Denys Dmytriyenko
2016-07-10 22:10 ` Denys Dmytriyenko
2016-07-11  8:32   ` Richard Purdie
2016-07-14  3:04     ` Denys Dmytriyenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160714030424.GF8521@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.