Your message dated Tue, 2 Jul 2024 15:43:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#934189: varnish: problem in upgrading to buster
has caused the Debian Bug report #934189,
regarding varnish: problem in upgrading to buster
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.)
--
934189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934189
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: varnish
Version: 6.1.1-1+b1
Severity: normal
Dear Maintainer,
In upgrading to buster from stretch I got:
Setting up varnish (6.1.1-1+b1) ...
insserv: script varnish1: service varnish already provided!
insserv: script varnish1: service varnish already provided!
Job for varnishncsa.service failed because the control process exited with
error code.
See "systemctl status varnishncsa.service" and "journalctl -xe" for details.
invoke-rc.d: initscript varnishncsa, action "restart" failed.
* varnishncsa.service - Varnish HTTP accelerator log daemon
Loaded: loaded (/lib/systemd/system/varnishncsa.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-08-07 23:00:14 CEST;
5ms ago
Docs: https://www.varnish-cache.org/docs/6.1/
man:varnishncsa
Process: 10352 ExecStart=/usr/bin/varnishncsa -a -w
/var/log/varnish/varnishncsa.log -D -P /run/varnishncsa/varnishncsa.pid
(code=exited, status=1/FAILURE)
Aug 07 23:00:13 catho2 systemd[1]: Starting Varnish HTTP accelerator log
daemon...
Aug 07 23:00:14 catho2 varnishncsa[10352]: Can't open output file (Permission
denied)
Aug 07 23:00:14 catho2 systemd[1]: varnishncsa.service: Control process exited,
code=exited, status=1/FAILURE
Aug 07 23:00:14 catho2 systemd[1]: varnishncsa.service: Failed with result
'exit-code'.
Aug 07 23:00:14 catho2 systemd[1]: Failed to start Varnish HTTP accelerator log
daemon.
dpkg: error processing package varnish (--configure):
installed varnish package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
varnish
E: Sub-process /usr/bin/dpkg returned an error code (1)
and apt -f install keeps trying to configure varnish without success.
It looks like it's https://bugzilla.redhat.com/show_bug.cgi?id=1371181 : the
new varnish version expects owner varnish:varnish, while the old one used
root:root.
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT.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 [not included]
/etc/varnish/default.vcl changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.5.0-1
On Aug 07, Paolo Benvenuto <[email protected]> wrote:
Ciao Paolo!
> Aug 07 23:00:14 catho2 varnishncsa[10352]: Can't open output file (Permission
> denied)
Now the ownership of /var/log/varnish/ is controlled by the
LogsDirectory directive in varnishncsa.service itself, so it will always
been correct.
--
ciao,
Marco
signature.asc
Description: PGP signature
--- End Message ---
