Package: varnish Version: 6.1.1-1+deb10u1 Severity: normal Dear Maintainer,
* What led up to the situation? Varnish running on default port, 6081. run "service varnish configtest" to verify custom configuration. configtest reports could not bind to socket, instead of verifying configuration. * What was the outcome of this action? Errors as follows; Error: Could not get socket :6081: Address already in use (-? gives usage) * What outcome did you expect instead? Runs configtest and tries to compile VCL, alerting on any errors. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages varnish depends on: ii adduser 3.118 ii gcc 4:8.3.0-1 ii libc6 2.28-10 ii libc6-dev [libc-dev] 2.28-10 ii libedit2 3.1-20181209-1 ii libjemalloc2 5.1.0-3 ii libncursesw6 6.1+20181013-2+deb10u2 ii libpcre3 2:8.39-12 ii libtinfo6 6.1+20181013-2+deb10u2 ii libvarnishapi2 6.1.1-1+deb10u1 ii lsb-base 10.2019051400 varnish recommends no packages. Versions of packages varnish suggests: pn varnish-doc <none> -- Configuration Files: /etc/varnish/default.vcl changed [not included] -- no debconf information
