Package: nghttp2-proxy Version: 1.20.0-1 Severity: normal Dear Maintainer, when nghttpx starts at boot, the dns resolver may not be available and then the start fails. More surprisingly, this also happens for explicit ip addresses and port addresses such as 127.0.0.1:80.
The upstream bug is https://github.com/nghttp2/nghttp2/issues/857 Cheers. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nghttp2-proxy depends on: ii init-system-helpers 1.47 ii libc-ares2 1.12.0-1 ii libc6 2.24-9 ii libev4 1:4.22-1 ii libgcc1 1:6.3.0-10 ii libjansson4 2.9-1 ii libjemalloc1 3.6.0-9.1 ii libnghttp2-14 1.20.0-1 ii libspdylay7 1.3.2-2.1 ii libssl1.1 1.1.0e-1 ii libstdc++6 6.3.0-10 ii libsystemd0 232-19 ii libxml2 2.9.4+dfsg1-2.2 ii lsb-base 9.20161125 ii openssl 1.1.0e-1 ii python 2.7.13-2 ii zlib1g 1:1.2.8.dfsg-5 nghttp2-proxy recommends no packages. nghttp2-proxy suggests no packages. -- Configuration Files: /etc/nghttpx/nghttpx.conf changed [not included] -- no debconf information
