Bug 1707831

Summary:	Permissions wrong on /var/opt/rh/rh-varnish6/log/varnish
Product:	Red Hat Software Collections	Reporter:	Jeff Voskamp <javoskam>
Component:	rh-varnish6	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rh-varnish6	CC:	bnater, jorton
Target Milestone:	---
Target Release:	3.4
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-26 09:40:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Voskamp 2019-05-08 13:51:53 UTC

Description of problem:
Permissions on log directory won't let varnishncsa start.


Version-Release number of selected component (if applicable):
Package rh-varnish6-varnish-6.0.0-2


How reproducible:
Problem is present "out of the box"


Steps to Reproduce:
1. install rh-varnish6-varnish
2. systemctl start rh-varnish6-varnishncsa.service 

Actual results:
From logs:
systemd: Starting Varnish Cache HTTP accelerator NCSA logging daemon...
varnishncsa: Can't open output file (Permission denied)
systemd: rh-varnish6-varnishncsa.service: control process exited, code=exited status=1
systemd: Failed to start Varnish Cache HTTP accelerator NCSA logging daemon.
systemd: Unit rh-varnish6-varnishncsa.service entered failed state.
systemd: rh-varnish6-varnishncsa.service failed.

Expected results:
from "ps axf":
/opt/rh/rh-varnish6/root/usr/bin/varnishncsa -a -w /var/opt/rh/rh-varnish6/log/varnish/varnishncsa.log -D -P /var/opt/rh/rh-varnish6/run/rh-varnish6-varnish/varnishncsa.pid



Additional info:
Permissions on log and pid directories are wrong" drwx------ root.root" when varnishncsa runs as varnish.varnish
Probably needs a file in /usr/lib/tmpfiles.d/

Comment 11 errata-xmlrpc 2020-05-26 09:40:34 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:2262