maxchk / puppet-varnish

Puppet module to install, configure and manage Varnish
Apache License 2.0
22 stars 95 forks source link

EL7 / plain install: varnish fails on startup #136

Open tobixen opened 7 years ago

tobixen commented 7 years ago

On a relatively clean centos7-box, I tried to do an "include varnish". Varnish doesn't seem to like the tmpfs:

-- Unit varnish.service has begun starting up. Dec 24 16:42:15 myhost varnishd[30052]: Cannot create working directory '/var/lib/varnish/myhost/': Permission denied Dec 24 16:42:15 myhost systemd[1]: varnish.service: control process exited, code=exited status=1 Dec 24 16:42:15 myhost systemd[1]: Failed to start Varnish a high-perfomance HTTP accelerator.

I've tried:

Suggested workaround: make tmpfs false by default?

I'm not going to do more research on this, I'll just disable the tmpfs feature.

system information:

$ varnishd -V varnishd (varnish-3.0.7 revision f544cd8) $ sudo facter -p | grep version (...) kernelmajversion => 3.10 kernelversion => 3.10.0 puppetversion => 3.6.2 systemd_version => 219 varnish_version => 3.0.7

os => {"name"=>"CentOS", "family"=>"RedHat", "release"=>{"major"=>"7", "minor"=>"2", "full"=>"7.2.1511"}, "lsb"=>{"distcodename"=>"Core", "distid"=>"CentOS", "distdescription"=>"CentOS Linux release 7.2.1511 (Core) ", "release"=>":core-4.1-amd64:core-4.1-noarch", "distrelease"=>"7.2.1511", "majdistrelease"=>"7", "minordistrelease"=>"2"}}

Tried on the develop-branch of the varnish module, revision 39ca2f11aa5a398740f19d373cb57e046780262b

tobixen commented 7 years ago

Perhaps version number 3.0 shouldn't be default anymore. I nudged it to 4.1, and then varnish started without problems, on tmpfs.