varnish-4.1.3 and varnish-modules-0.9.1 for fedora and epel

The Varnish Cache project recently released varnish-4.1.3 and varnish-modules-0.9.1. Of course, we want updated rpms for Fedora and EPEL.

While there are official packages for el6 and el7, I tend to like to use my Fedora downstream package, also for EPEL. So I have pushed updates for Fedora, and updated copr builds for epel5, epel6, and epel7.

An update of the official supported bundle of varnish modules, varnish-modules-0.9.1, was also released a few weeks ago. I did recently wrap it for Fedora, and am waiting for its review in BZ #1324863. Packages for epel5, epel6, and epel7 are in copr as well.

Fedora updates for varnish-4.1.3 may be found at https://bodhi.fedoraproject.org/updates/?packages=varnish

The Copr repos for epel are here: https://copr.fedorainfracloud.org/coprs/ingvar/varnish41/

Test and reports are very welcome.

–

Varnish Cache is a powerful and feature rich front side web cache. It is also very fast, and that is, fast as in powered by The Dark Side of the Force. On steroids. And it is Free Software.

Redpill Linpro is the market leader for professional Open Source and Free Software solutions in the Nordics, though we have customers from all over. For professional managed services, all the way from small web apps, to massive IPv4/IPv6 multi data center media hosting, and everything through container solutions, in-house, cloud, and data center, contact us at www.redpill-linpro.com.

Tags: , , , ,

This entry was posted on Wednesday, August 10th, 2016 at 14:45 and is filed under comp, sysadmin, varnish. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

2 Responses to “varnish-4.1.3 and varnish-modules-0.9.1 for fedora and epel”

  1. Chad says:
    August 18, 2016 at 14:54

    It would be nice if the varnishlog and varnishncsa services worked by default. They need tmpfiles.d entries or a removal/update of the PIDFile/User/Group. To make it work:

    [Service]
    RuntimeDirectory=varnishlog
    Type=forking
    PIDFile=/run/varnishlog.pid
    #PIDFile=/run/varnishlog/varnishlog.pid
    #User=varnish
    #Group=varnish
    ExecStart=/usr/bin/varnishlog -a -w /var/log/varnish/varnish.log -D -P /run/varnishlog.pid
    #ExecStart=/usr/bin/varnishlog -a -w /var/log/varnish/varnish.log -D -P /run/varnishlog/varnishlog.pid
    ExecReload=/bin/kill -HUP $MAINPID

  2. ingvar says:
    September 2, 2016 at 13:01

    No, they shouldn’t need tmpfiles.d, as they have RuntimeDirectory set, and systemd will create the necessary tempfiles when started. Your problem is probably that varnish.log is owned by root, from an earlier version. See rhbz #1371181. This should be fixed in varnish-4.1.3-5, in fedora updates-testing now.

    Ingvar

Leave a Reply

You must be logged in to post a comment.