Pkg problem after upgrading from 9.3 to 10.3

[Matthew Seaman]

On 18/12/2016 22:38, francesco scaglione wrote:
> On Sun, 18 Dec 2016 17:59:47 +0000
> Matthew Seaman <matthew at FreeBSD.org> wrote:
> 
>> On 18/12/2016 17:30, francesco scaglione wrote:
>>> On Sun, 18 Dec 2016 17:06:29 +0000
>>> Matthew Seaman <matthew at FreeBSD.org> wrote:  
>>
>>>> This sounds like a problem with the DNS -- although why should this
>>>> affect you after upgrading to 10.x?  Did you switch to enabling the
>>>> local_unbound service when you upgraded?  
>>>
>>> Uhm, I don't think so... I just answered "y" to a few "does this
>>> look reasonable to you" questions. How could I check this?  
>>
>> Do you have:
>>
>>    local_unbound_enable="YES"
>>
>> in /etc/rc.conf?
> 
> Not now, no; was it there in 9.3?

No -- local_unbound was new in 10.0

>>>> What does this DNS query return for you?
>>>>
>>>>   % dig IN SRV _http._tcp.pkg.freebsd.org
>>>>
>>>> That should give you a list of download sites with
>>>> 'pkgmir.geo.freebsd.org' marked as the highest priority.
>>>> Connecting to this repo by name will automatically direct you to
>>>> the closest package mirror to your location.  That's
>>>> pkg0.bme.freebsd.org for people in Europe.  
>>>
>>> Right, I've tried first with dig:
>>>
>>> $ dig IN SRV _http._tcp.pkg.freebsd.org
>>> dig: not found  
>>
>> Heh.  Yes, dig is no longer in the base system in 10.x.  I reflexively
>> install bind-tools nowadays.
>>
>>> and then with drill:
>>>
>>> $ drill IN SRV _http._tcp.pkg.freebsd.org
>>> Warning: Could not create a resolver structure: Could not open the
>>> files ((null)) Try drill @localhost if you have a resolver running
>>> on your machine.  
>>
>> OK, this isn't good.  I suspect this is the cause of your problems.
>>
>> Try this.
>>
>>    # sysrc local_unbound_enable=YES
>>    # service local_unbound setup
>>    # service local_unbound start
> 
> # sysrc local_unbound_enable=YES
> local_unbound_enable: NO -> YES
> 
> # service local_unbound setup
> Performing initial setup.
> Extracting forwarders from /etc/resolv.conf.
> /usr/sbin/local-unbound-setup: cannot open /etc/resolv.conf: No such
> file or directory
> 

Yeah -- that's the smoking gun as to why pkg(8) was having problems.
You didn't have /etc/resolv.conf or anything set up so your system could
do DNS lookups.

> No forwarders found in resolv.conf, unbound will recurse.

This means that local_unbound will do all the work of DNS lookups
itself, rather than handing the task off to the resolvers provided by
your ISP (the 'forwarders' it mentions.)

It's 6 of one and half-a-dozen of the other as to whether it's better to
have forwarders or just have local_unbound recurse for itself.

> /var/unbound/lan-zones.conf created
> /var/unbound/control.conf created
> /var/unbound/unbound.conf created
> /etc/resolvconf.conf created
> /usr/sbin/local-unbound-setup: cannot open /etc/resolv.conf: No such
> file or directory
> /etc/resolv.conf created
> 
> # service local_unbound start
> Starting local_unbound.
> 
>> and try again with drill(1).  If there is still no joy, let us know
>> what the contents of /etc/resolv.conf and /var/unbound/forward.conf
>> are.
> 
> # drill IN SRV _http._tcp.pkg.freebsd.org
> Error: error sending query: No (valid) nameservers defined in the
> resolver

Curious.  This should work if the local_unbound service is up and running.

> But at least, now I have:
> 
> #pkg update
> Updating FreeBSD repository catalogue...
> Fetching meta.txz: 100%    944 B   0.9kB/s    00:01    
> Fetching packagesite.txz: 100%    6 MiB   2.0MB/s    00:03    
> Processing entries: 100%
> FreeBSD repository update completed. 25735 packages processed.
> 
> # pkg upgrade
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up-to-date.
> All repositories are up-to-date.
> Checking for upgrades (0 candidates): 100%
> Processing candidates (0 candidates): 100%
> Checking integrity... done (0 conflicting)
> Your packages are up to date.
> 
> Should I be happy with that or shall I dig further?

So, enabling local_unbound has meant that you can successfully do DNS
lookups now.  You don't *have* to do anything more.  It does, however,
seem you somehow mislaid the configuration that you must have been using
with 9.x --- entirely up to you if you can recover what that was or if
you'ld prefer to revert back to that.

	Cheers,

	Matthew


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 931 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20161219/31fc5f1e/attachment.sig>