Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolution
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 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.
Signature · 1 line
Denys
Quoted 5 lines · Denys Dmytriyenko
Has anyone ever seen this error message:
ERROR: blah-blah
do_package: Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolutionI'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.
Quoted 4 lines
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.
Signature · 1 line
Denys
Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Denys Dmytriyenko
Has anyone ever seen this error message:
ERROR: blah-blah
do_package: Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolution
Quoted 15 lines
Quoted 2 lines
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.Quoted 7 lines
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.
Cheers,
Richard
Quoted 31 lines · Richard Purdie
Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Denys Dmytriyenko
Has anyone ever seen this error message:
ERROR: blah-blah
do_package: Can NOT get PRAUTO, exception [Errno -3] Temporary failure in name resolutionQuoted 15 lines
Quoted 2 lines
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.Quoted 7 lines
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?
Quoted 8 lines
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...
Signature · 1 line
Denys