From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Greylist: delayed 3600 seconds by postgrey-1.34 at layers.openembedded.org; Sun, 10 Jul 2016 23:11:12 UTC Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by mail.openembedded.org (Postfix) with ESMTP id D060A65D00 for ; Sun, 10 Jul 2016 23:11:12 +0000 (UTC) Received: from vz-proxy-m006.mx.aol.com ([64.236.83.10]) by vms173019.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0OA400IXDDM9NF90@vms173019.mailsrvcs.net> for openembedded-core@lists.openembedded.org; Sun, 10 Jul 2016 17:10:57 -0500 (CDT) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=Nc0brD34 c=1 sm=1 tr=0 a=pKq81LsWol7b8sI3Hpopew==:117 a=kj9zAlcOel0A:10 a=cAmyUtKerLwA:10 a=0qdUnEcgA0krgYN-DTgA:9 a=CjuIK1q_8ugA:10 Received: by 100.15.86.14 with SMTP id 79fc306b; Sun, 10 Jul 2016 22:10:57 GMT Received: by gandalf.denix.org (Postfix, from userid 1000) id 887121620AC; Sun, 10 Jul 2016 18:10:56 -0400 (EDT) Date: Sun, 10 Jul 2016 18:10:56 -0400 From: Denys Dmytriyenko To: openembedded-core@lists.openembedded.org Message-id: <20160710221056.GD8521@denix.org> References: <20160710213559.GC8521@denix.org> MIME-version: 1.0 In-reply-to: <20160710213559.GC8521@denix.org> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolution X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 23:11:13 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline 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. -- Denys