Mailing List Archive

Varnish child failing due to new VMOD
Hi All,

I have varnish 4 (4.1.8 as of today) installed on a RHEL 7 machine. I have
seen a problem a few days after the past two updates that is causing
varnish to crash and not restart properly. It looks like a child process
is failing but the manager is not trying to restart it. I've included the
varnish system logs from the past 2 months. The error in question is
"Loading VMOD std from /usr/lib64/varnish/vmods/libvmod_std.so: This is no
longer the same file seen by the VCL-compiler." Does anyone have any ideas
what might be causing this or how to prevent it?

Thanks,

Matt


Jul 09 20:46:46 {servername} varnishd[35916]: Child (31586) not responding
to CLI, killed it.
Jul 09 20:46:46 {servername} varnishd[35916]: Unexpected reply from ping:
400 CLI communication error (hdr)
Jul 09 20:46:46 {servername} varnishd[35916]: Child (31586) died signal=11
Jul 09 20:46:46 {servername} varnishd[35916]: Child cleanup complete
Jul 09 20:46:46 {servername} varnishd[35916]: Child (7499) Started
Jul 09 20:46:46 {servername} varnishd[35916]: Child (7499) Pushing vcls
failed:
VCL "boot"
Failed initialization
Message:

Loading VMOD std from /usr/lib64/varnish/vmods/libvmod_std.so:
This is no
longer the same file seen by the VCL-compiler.
Jul 09 20:46:46 {servername} varnishd[35916]: Stopping Child
Jul 09 20:46:47 {servername} varnishd[35916]: Child (7499) ended
Jul 09 20:46:47 {servername} varnishd[35916]: Child (7499) said Child starts
Jul 09 20:46:47 {servername} varnishd[35916]: Child (7499) said Child dies
Jul 09 20:46:47 {servername} varnishd[35916]: Child cleanup complete
Jul 10 10:18:53 {servername} varnishd[35916]: Manager got SIGINT
Jul 10 10:18:53 {servername} systemd[1]: Stopping Varnish Cache, a
high-performance HTTP accelerator...
Jul 10 10:18:53 {servername} systemd[1]: Starting Varnish Cache, a
high-performance HTTP accelerator...
Jul 10 10:18:54 {servername} varnishd[20573]: Platform:
Linux,3.10.0-327.28.3.el7.x86_64,x86_64,-junix,-smalloc,-smal
Jul 10 10:18:54 {servername} systemd[1]: Started Varnish Cache, a
high-performance HTTP accelerator.
Jul 10 10:18:54 {servername} varnishd[20573]: Child (20574) Started
Jul 10 10:18:54 {servername} varnishd[20573]: Child (20574) said Child
starts
Jul 18 17:15:28 {servername} varnishd[20573]: Child (20574) died signal=11
Jul 18 17:15:28 {servername} varnishd[20573]: Child cleanup complete
Jul 18 17:15:28 {servername} varnishd[20573]: Child (14063) Started
Jul 18 17:15:28 {servername} varnishd[20573]: Child (14063) said Child
starts
Aug 09 22:16:04 {servername} varnishd[20573]: Child (14063) died signal=11
Aug 09 22:16:04 {servername} varnishd[20573]: Child cleanup complete
Aug 09 22:16:04 {servername} varnishd[20573]: Child (32837) Started
Aug 09 22:16:04 {servername} varnishd[20573]: Child (32837) Pushing vcls
failed:
VCL "boot"
Failed initialization
Message:

Loading VMOD std from /usr/lib64/varnish/vmods/libvmod_std.so:
This is no
longer the same file seen by the VCL-compiler.
Aug 09 22:16:04 {servername} varnishd[20573]: Stopping Child
Aug 09 22:16:05 {servername} varnishd[20573]: Child (32837) ended
Aug 09 22:16:06 {servername} varnishd[20573]: Child (32837) said Child
starts
Aug 09 22:16:06 {servername} varnishd[20573]: Child (32837) said Child dies
Aug 09 22:16:06 {servername} varnishd[20573]: Child cleanup complete
Aug 09 22:27:46 {servername} systemd[1]: Stopping Varnish Cache, a
high-performance HTTP accelerator...
Aug 09 22:27:46 {servername} varnishd[20573]: Manager got SIGINT
Aug 09 22:27:46 {servername} systemd[1]: Starting Varnish Cache, a
high-performance HTTP accelerator...
Aug 09 22:27:47 {servername} varnishd[34284]: Platform:
Linux,3.10.0-327.28.3.el7.x86_64,x86_64,-junix,-smalloc,-smal
Aug 09 22:27:47 {servername} systemd[1]: Started Varnish Cache, a
high-performance HTTP accelerator.
Aug 09 22:27:47 {servername} varnishd[34284]: Child (34285) Started
Aug 09 22:27:47 {servername} varnishd[34284]: Child (34285) said Child
starts