Your message dated Tue, 02 Jul 2024 12:35:50 +0000
with message-id <[email protected]>
and subject line Bug#934278: fixed in varnish 7.5.0-1
has caused the Debian Bug report #934278,
regarding varnishlog: loaded failed failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
934278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934278
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: varnish
Version: 6.1.1-1+b1
Severity: normal

Dear Maintainer,

varnishlog fails to start on reboot:

2019-08-09T02:41:13.581+00:00 pawan varnishlog[784]: Starting HTTP 
accelerator log deamon: failed!
2019-08-09T02:41:13.581+00:00 pawan varnishlog[784]: ....
2019-08-09T02:41:13.581+00:00 pawan varnishlog[784]: VSM: Could not get 
hold of varnishd, is it running?
2019-08-09T02:41:13.581+00:00 pawan systemd[1]: varnishlog.service: 
Control process exited, code=exited, status=1/FAILURE
2019-08-09T02:41:13.581+00:00 pawan systemd[1]: varnishlog.service: 
Failed with result 'exit-code'.
2019-08-09T02:41:13.581+00:00 pawan systemd[1]: Failed to start LSB: 
Start HTTP accelerator log daemon.

It appears to be a timing issue restarting it manually works fine:

systemctl restart varnishlog.service

root@pawan:/var/log# systemctl status varnishlog
● varnishlog.service - LSB: Start HTTP accelerator log daemon
   Loaded: loaded (/etc/init.d/varnishlog; generated)
   Active: active (running) since Thu 2019-08-08 22:55:15 EDT; 1min 5s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 6568 ExecStart=/etc/init.d/varnishlog start (code=exited, 
status=0/SUCCESS)
    Tasks: 1 (limit: 4915)
   Memory: 1.2M
   CGroup: /system.slice/varnishlog.service
           └─6576 /usr/bin/varnishlog -a -w /var/log/varnish/varnish.log -D -P 
/run/varnishlog/varnishlog.pid

Aug 08 22:55:15 pawan systemd[1]: Starting LSB: Start HTTP accelerator log 
daemon...
Aug 08 22:55:15 pawan varnishlog[6568]: Starting HTTP accelerator log deamon:.
Aug 08 22:55:15 pawan systemd[1]: Started LSB: Start HTTP accelerator log 
daemon.

That said, I am not really sure this even works.  The only reference I see to
varnishlog is:

root@pawan:/# find /lib/systemd/ /etc -name varnishlog\*
/etc/systemd/system/multi-user.target.wants/varnishlog.service
/etc/default/varnishlog
/etc/init.d/varnishlog

and varnishlog.service is a dangling symlink to:

/lib/systemd/system/varnishlog.service

it seems to some type of left-over from a previous version:

dpkg -S varnishlog
varnish: /usr/bin/varnishlog
varnish: /etc/init.d/varnishlog
varnish: /usr/share/man/man1/varnishlog.1.gz
varnish: /etc/default/varnishlog

So I stopped the service the service and removed the file:

# systemctl disable varnishlog.service
# systemctl stop varnishlog.service
# rm /etc/systemd/system/multi-user.target.wants/varnishlog.service

I wanted to document this, but maybe there is a cleanup process missing
somewhere?


/Allan

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/24 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /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
ii  libpcre3              2:8.39-12
ii  libtinfo6             6.1+20181013-2
ii  libvarnishapi2        6.1.1-1+b1
ii  lsb-base              10.2019051400

varnish recommends no packages.

Versions of packages varnish suggests:
pn  varnish-doc  <none>

-- Configuration Files:
/etc/default/varnish changed:
START=yes
NFILES=131072
MEMLOCK=82000
DAEMON_OPTS="-a :6081 \
             -f /etc/varnish/default.vcl \
             -S /etc/varnish/secret \
             -s file,/var/lib/varnish/$(uname -n)/varnish_storage.bin,32G \
             -T localhost:6082 \
             -t 120"

/etc/default/varnishlog changed:
VARNISHLOG_ENABLED=1

/etc/logrotate.d/varnish changed:
/var/log/varnish/varnish.log {
        compress
        daily
        delaycompress
        missingok
        postrotate
                systemctl -q is-active varnishncsa.service &&
                        /usr/sbin/invoke-rc.d varnishncsa reload > /dev/null
                systemctl -q is-active varnishlog.service &&
                        /usr/sbin/invoke-rc.d varnishlog reload > /dev/null
        endscript
        rotate 30
}

/etc/varnish/default.vcl changed:
vcl 4.0;
import std;
backend default {
        .host = "127.0.0.1";
        .port = "8080";
}
sub vcl_backend_response {
        if (bereq.url ~ "^[^?]*\.(mp[34]|pdf|wav)(\?.*)?$") {
                unset beresp.http.set-cookie;
                set beresp.do_stream = true;
        } else if (bereq.uncacheable) {
        } else if (beresp.ttl <= 0s || beresp.http.Set-Cookie || 
beresp.http.Surrogate-control ~ "no-store" || (!beresp.http.Surrogate-Control 
&& beresp.http.Cache-Control ~ "no-cache|no-store|private") || beresp.http.Vary 
== "*") {
                # Mark as "Hit-For-Pass" for the next 2 minutes
                set beresp.ttl = 120s;
                set beresp.uncacheable = true;
        }
        return (deliver);
}
sub vcl_recv {
        if (req.url ~ 
"^[^?]*\.(css|gif|jpeg|jpg|js|pdf|mp3|mp4|png|txt|wav)(\?.*)?$") {
                unset req.http.Cookie;
                return (hash);
        }
}


-- no debconf information

--- End Message ---
--- Begin Message ---
Source: varnish
Source-Version: 7.5.0-1
Done: Marco d'Itri <[email protected]>

We believe that the bug you reported is fixed in the latest version of
varnish, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marco d'Itri <[email protected]> (supplier of updated varnish package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 02 Jul 2024 13:59:11 +0200
Source: varnish
Architecture: source
Version: 7.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Varnish Package Maintainers <[email protected]>
Changed-By: Marco d'Itri <[email protected]>
Closes: 657449 659005 737528 881056 934278 961750 1056156 1068455
Changes:
 varnish (7.5.0-1) unstable; urgency=medium
 .
   * New upstream release. Fixes:
     + HTTP/2 Rapid Reset Attack (CVE-2023-44487, VSV00013).
       (Closes: #1056156)
     + HTTP/2 Broke Window Attack (CVE-2024-30156, VSV00014).
       (Closes: #1068455)
   * Remove the unmaintained init scripts.
     (Closes: #657449, #659005, #737528, #881056, #934278, #961750)
   * Make all daemons Restart=on-failure.
   * Switch to systemd-tmpfiles and systemd-sysusers.
   * Stop creating /var/lib/varnish/$HOSTNAME/, which is not used anymore
     by modern Varnish.
   * Create /var/lib/varnish/CACHEDIR.TAG to signal that the directory
     content should not be backed up.
   * Replace more embedded Javascript with libjs-sphinxdoc.
Checksums-Sha1:
 68e409050b6ccbb34e18fb2f134694870d21ea2e 1858 varnish_7.5.0-1.dsc
 3bdf4388ec9bfeb7558fe1ae9289dbd7e03b49fc 2068104 varnish_7.5.0.orig.tar.gz
 3940763eeda1cee79a67cc3f6fcd6d952deb1d85 20768 varnish_7.5.0-1.debian.tar.xz
 ba562e5d908fd7d31134612e223e7237a37d255a 10385 varnish_7.5.0-1_amd64.buildinfo
Checksums-Sha256:
 9a0e301fd70fe47e5dff1a52789fbe17b19eba0275ad24edceda6a9c65dce813 1858 
varnish_7.5.0-1.dsc
 b1771abe56662fb1664e46166c572477660541c6fd142d8585fe013dec5c1a31 2068104 
varnish_7.5.0.orig.tar.gz
 d9e2acd9b36c04ac26fd3cf0ddfd3287d5b59e2dc0aa757829750d6b728814c4 20768 
varnish_7.5.0-1.debian.tar.xz
 dad783eaa5d1730688688db9b7615415a4f396f5126bd88a2b9c9aa8d6406893 10385 
varnish_7.5.0-1_amd64.buildinfo
Files:
 25f868f8b2c757d5e21af912cf340bbc 1858 web optional varnish_7.5.0-1.dsc
 da5f7f0703faf76dfbe181dbcf010773 2068104 web optional varnish_7.5.0.orig.tar.gz
 87f5ce5237f1b771c0fc8e8366dc60e2 20768 web optional 
varnish_7.5.0-1.debian.tar.xz
 69cf7c49d1b8cc91889b8d5fc1789e3f 10385 web optional 
varnish_7.5.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCZoPw4gAKCRDLPsM64d7X
geClAQC8t8FAYY/RUIwixx4HQ9p2xH6JepJL1sJI5faeqZjQVwD/aPa/uxJuOpek
wxuahjBJr8DEJgOTjKYkfrrL2VcK6w8=
=YXca
-----END PGP SIGNATURE-----

Attachment: pgpx9DHWOKYZG.pgp
Description: PGP signature


--- End Message ---

Reply via email to