Magento Confused about varnish 6 varnish.params

niamniamniam · Aug 2, 2019

Hey, I've really happy with my magento install, installed a couple of months and it still the fastest and cheapest magento stack
I tryed to update the varnish cache of it and It seems that varnish 6 and above, doesn't use the varnish.params file, so what should I do with the custom params echoed by the 5.2.1 install?
I'm afraid to update it and break a honestly pretty great mage install. Anyone using varnish 6.2?

eva2000 · Aug 2, 2019

probably need to google and read documentation https://varnish-cache.org/docs/trunk/whats-new/upgrading-6.0.html

The biggest change that resulted in unifying our systemd setup across all official packages is that the varnish.params file available on Red Hat derivatives is gone. We noticed that using an environment file to hide the fact that varnishd is configured via command line arguments misled some people into thinking that what was proposed in the file was your only set of configuration options. For example, you can specify multiple listen addresses using multiple -a options but you only get variables for one address and a catch-all variable DAEMON_OPTS for anything not fitting in the template. In addition using an environment file pollutes the process's environment.

Another big difference between Red Hat and Debian derivatives was the way we handled VCL reloads via the service manager. We introduced a new varnishreload script that operates on top of varnishadm to perform hot reloads of one VCL configuration or label at a time. All you need is enough privileges to contact varnishd's command line interface, which should not be a problem for package managers.

Once the varnish package is installed, you can learn more:

varnishreload -h

Again, many thanks to downstream maintainers and some early adopters for their help in testing the new script.

To stay on the topic of the command line interface, packages no longer create a secret file for the CLI, and services omit -S and -T options on the varnishd command. This means that out of the box, you can only connect to the CLI locally with enough privileges to read a secret generated randomly. This means less noise in our packages, and you need to change the service configuration to enable remote access to the CLI. With previous packages, you also needed to change your configuration because the CLI would only listen to the loopback interface anyway.

To change how varnishd is started, please refer to the systemd documentation.
Click to expand...

niamniamniam · Aug 3, 2019

Hey @eva2000 thanks for the help, I've already had foun this, but still not clear to me. So i'm guessing I should use the DAEMON_OPTS variable on /etc/sysconfig/varnish?

eva2000 · Aug 3, 2019

Best to ask on Varnish user support channels/community https://varnish-cache.org/support/

Log in / Register

Forums

Welcome to Centmin Mod Community

Magento Confused about varnish 6 varnish.params

niamniamniam New Member

eva2000 Administrator Staff Member

niamniamniam New Member

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Welcome to Centmin Mod Community

Magento Confused about varnish 6 varnish.params

niamniamniam New Member

eva2000 Administrator Staff Member

niamniamniam New Member

eva2000 Administrator Staff Member

.