Running Two varnishncsa Instances using Systemd : looking for best practice

[Dridi Boukelmoune]

On Wed, Jan 29, 2020 at 4:59 PM Yassine Aouadi
<yassine.aouadi90 at gmail.com> wrote:
>
>
> Dridi,
>
> Thank you for the Catch !
>
> I was  going to correct with  "RespStatus > 399 or BerespStatus > 399" but yours is better.

Pick whatever works best for you ;-)

> Splitting the unitsseems to look fine in Dev :
>
> ---
> ● varnishncsa-access.service - Varnish HTTP accelerator log daemon
>    Loaded: loaded (/lib/systemd/system/varnishncsa-access.service; disabled; vendor preset: enabled)
>    Active: active (running) since Wed 2020-01-29 16:52:15 UTC; 5s ago
>      Docs: https://www.varnish-cache.org/docs/4.1/
>            man:varnishncsa
>   Process: 10571 ExecStart=/usr/bin/varnishncsa -c -b -a -w /var/log/varnish/access-varnishncsa.log -D -P /run/varnishncsa/varnishncsa-access.pid -f /etc/varnish/varnishncsa_logmatic.format -q *Status < 400
>  Main PID: 10575 (varnishncsa)
>     Tasks: 1
>    Memory: 188.0K
>       CPU: 44ms
>    CGroup: /system.slice/varnishncsa-access.service
>            └─10575 /usr/bin/varnishncsa -c -b -a -w /var/log/varnish/access-varnishncsa.log -D -P /run/varnishncsa/varnishncsa-access.pid -f /etc/varnish/varnishncsa_logmatic.format -q *Status < 400
>
> Jan 29 16:52:15 LAB-*** systemd[1]: Starting Varnish HTTP accelerator log daemon...
> Jan 29 16:52:15 LAB*** ystemd[1]: Started Varnish HTTP accelerator log daemon.
>
> ● varnishncsa-error.service - Varnish HTTP accelerator log daemon
>    Loaded: loaded (/lib/systemd/system/varnishncsa-error.service; disabled; vendor preset: enabled)
>    Active: active (running) since Wed 2020-01-29 16:52:15 UTC; 5s ago
>      Docs: https://www.varnish-cache.org/docs/4.1/
>            man:varnishncsa
>   Process: 10566 ExecStart=/usr/bin/varnishncsa -c -b -a -w /var/log/varnish/error-varnishncsa.log -D -P /run/varnishncsa/varnishncsa-error.pid -f /etc/varnish/varnishncsa_logmatic.format -q *Status > 399
>  Main PID: 10574 (varnishncsa)
>     Tasks: 1
>    Memory: 312.0K
>       CPU: 46ms
>    CGroup: /system.slice/varnishncsa-error.service
>            └─10574 /usr/bin/varnishncsa -c -b -a -w /var/log/varnish/error-varnishncsa.log -D -P /run/varnishncsa/varnishncsa-error.pid -f /etc/varnish/varnishncsa_logmatic.format -q *Status > 399
>
> Jan 29 16:52:15 LAB-*** systemd[1]: Starting Varnish HTTP accelerator log daemon...
> Jan 29 16:52:15 LAB-*** systemd[1]: Started Varnish HTTP accelerator log daemon.
> ---
>
>
> Would provide feedback once moving to prod.

Please note that you can also put the query in a file with Varnish
6.3, so in theory you could do something like this:

    [Unit]
    Description=Varnish HTTP accelerator log daemon
    Documentation=https://www.varnish-cache.org/docs/4.1/ man:varnishncsa
    After=varnish.service

    [Service]
    Type=forking
    PIDFile=/run/varnishncsa/%i.pid
    RuntimeDirectory=varnishncsa
    User=varnishlog
    Group=varnish
    ExecStart=/usr/bin/varnishncsa -c -b -a -w
/var/log/varnish/%i-varnishncsa.log -D \
            -f /etc/varnish/varnishncsa_logmatic.format -Q /etc/varnish/%i.vslq
    ExecReload=/bin/kill -HUP $MAINPID
    PrivateDevices=true
    PrivateTmp=true
    ProtectHome=true
    ProtectSystem=full

    [Install]
    WantedBy=multi-user.target

Then you can manage both services from the same unit:

    systemctl start varnishncsa at access.service varnishncsa at error.service

In /etc/varnish/access.vslq you would write:

    *Status < 400

I'll leave the dirty systemd details to yourself, but that's how I'd
likely proceed :)

Dridi