Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 657620 - emerge --sync => gpg: keyserver refresh failed: No such file or directory (due to missing /etc/resolv.conf)
Summary: emerge --sync => gpg: keyserver refresh failed: No such file or directory (du...
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
Depends on:
Blocks: 650144
  Show dependency tree
Reported: 2018-06-08 18:53 UTC by Arsen Shnurkov
Modified: 2021-06-07 08:59 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Arsen Shnurkov 2018-06-08 18:53:48 UTC
when i do "emerge --sync"

it says:

OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://
gpg: keyserver refresh failed: No such file or directory

see also:

Reproducible: Always
Comment 1 Zac Medico gentoo-dev 2018-06-08 19:39:15 UTC
Please post the output of 'emerge --info app-crypt/gnupg'.
Comment 2 Arsen Shnurkov 2018-06-08 19:54:11 UTC
(In reply to Zac Medico from comment #1)
> Please post the output of 'emerge --info app-crypt/gnupg'.

# emerge --info app-crypt/gnupg
!!! Repository 'x-portage' is missing masters attribute in '/usr/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
WARNING: One or more repositories have missing repo_name entries:


NOTE: Each repo_name entry should be a plain text file containing a
unique name for the repository on the first line.

Portage 2.3.40 (python 3.5.5-final-0, unavailable, gcc-6.4.0, glibc-2.26-r7, 4.15.0-sabayon x86_64)
                         System Settings
System uname: Linux-4.15.0-sabayon-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q9650_@_3.00GHz-with-gentoo-2.4.1
KiB Mem:     8156340 total,   1335132 free
KiB Swap:    8388604 total,   7479564 free
sh bash 4.4_p12
ld GNU ld (Gentoo 2.30 p2) 2.30.0
dev-lang/python:          2.7.14-r1::gentoo, 3.5.5::gentoo
sys-devel/autoconf:       2.69-r4::gentoo
sys-devel/automake:       1.15.1-r2::gentoo
sys-devel/binutils:       2.30-r2::gentoo
sys-devel/libtool:        2.4.6-r3::gentoo
sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers)

    location: /usr/portage
    sync-type: rsync
    sync-uri: rsync://
    priority: -1000
    sync-rsync-verify-metamanifest: yes
    sync-rsync-verify-max-age: 24
    sync-rsync-verify-jobs: 1

    location: /usr/portage
    masters: gentoo

CFLAGS="-O2 -pipe"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gentoo-release /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
USE="bindist mmx sse sse2"

                        Package Settings

app-crypt/gnupg-2.2.4-r2::gentoo was built with the following:
USE="abi_x86_64 amd64 bzip2 elibc_glibc kernel_linux nls readline smartcard ssl userland_GNU -doc -ldap -selinux -tofu -tools -usb -wks-server"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
Comment 3 Arsen Shnurkov 2018-06-08 20:10:15 UTC
steps to reproduce:

cd /mnt/gentoo
wget -c
tar xvjpf stage3-*.tar.bz2 --xattrs --numeric-owner

mount -t proc /proc /mnt/gentoo/proc
mount --rbind /sys /mnt/gentoo/sys
mount --make-rslave /mnt/gentoo/sys
mount --rbind /dev /mnt/gentoo/dev
mount --make-rslave /mnt/gentoo/dev

chroot /mnt/gentoo /bin/bash
source /etc/profile
export PS1="(chroot) $PS1"

emerge --sync
Comment 4 Zac Medico gentoo-dev 2018-06-08 20:54:03 UTC
(In reply to Arsen Shnurkov from comment #3)

Yes, was able to reproduce the problem with this tarball. Then I emerged strace, and suddenly I was unable to reproduce the problem. I'll have to try again to figure out what suppressed the problem.
Comment 5 Zac Medico gentoo-dev 2018-06-08 21:27:35 UTC
Missing /etc/resolv.conf triggers this issue.
Comment 6 Arsen Shnurkov 2018-06-08 21:29:41 UTC
oh, sorry about this my mistake. Big thanks!
Comment 7 Einstok Fair 2021-06-07 08:59:03 UTC
# readlink /etc/resolv.conf

and that file is created by 
# systemctl start systemd-resolved