I've just submitted a similar bug report for varnishlog, with a potential fix. If you're using systemd to control varnishncsa, it's probably the same issue. Try adding a larger -t parameter to the varnishncsa daemon (/etc/systemd/system/varnishncsa.service copied from /lib/systemd/system/varnishncsa.service and then tweaked).
On Thu, 16 Apr 2015 11:28:47 +0200 Oskar Liljeblad <os...@osk.mine.nu> wrote: > Package: varnish > Version: 4.0.2-1 > Severity: normal > > varnishncsa sometimes does not start after reboot. > I suspect varnishncsa fails because it cannot contact varnish, which has not started completely yet. > > Regards, > > Oskar Liljeblad > > > -- System Information: > Debian Release: 8.0 > APT prefers testing > APT policy: (990, 'testing'), (500, 'testing-updates') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > >
