Varnish stops working after few days

canefield

Dear all,

I encounter the same problems…after a couple of days Varnish is stopped and won't come online until a reboot of pfSense. Then again a couple days later the system doesn't respond to my external requests. How come?

Thanks,
Canefield

marcelloc

Is there any log or alert or message during manual service restart to help on identifying this problem?

I`m using it on amd64 for a long time without crashes.

att,
Marcello Coutinho

canefield

Yes, after a couple of tests the following error emerge:

"php: : The command '/usr/local/etc/rc.d/varnish.sh' returned exit code '2', the output was 'kern.ipc.nmbclusters: 65536 sysctl: kern.ipc.nmbclusters: Invalid argument kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 NB: Storage size limited to 2GB on 32 bit architecture, NB: otherwise we could run out of address space. Message from VCC-compiler: Reference to unknown backend 'CANLB' at ('input' Line 55 Pos 28) .backend = CANLB; –-------------------------###########- In director specification starting at: ('input' Line 53 Pos 1) director CA client { ########------------ Running VCC-compiler failed, exit 1 VCL compilation failed'"

Thanks a lot,
Canefield

marcelloc

canefield,

something is messing up config:

Message from VCC-compiler: Reference to unknown backend 'CANLB' at ('input' Line 55 Pos 28) .backend = CANLB; –-------------------------###########-
In director specification starting at: ('input' Line 53 Pos 1) director CA client { ########------------ Running VCC-compiler failed, exit 1 VCL compilation failed'"

xudus

marcelloc, is there any particular command that I could run that would help with finding the root cause?

TIA,
Dave

marcelloc

xudus,

try to run the startup command on console/ssh

/usr/local/etc/rc.d/varnish.sh restart

xudus

This is what I'm getting:


kern.ipc.nmbclusters: 65536
sysctl: kern.ipc.nmbclusters: Invalid argument
kern.ipc.somaxconn: 16384 -> 16384
kern.maxfiles: 131072 -> 131072
kern.maxfilesperproc: 104856 -> 104856
kern.threads.max_threads_per_proc: 4096 -> 4096
storage_malloc: max size 128 MB.
Using old SHMFILE

marcelloc

@xudus:

This is what I'm getting:

There is no varnish fatal errors on this log, so it should be runinng.

xudus

Sorry, it is running as I just restarted pfs. I'll post the output when it'll malfunction next time.

xudus

marcelloc, it did it again.

The output from /usr/local/etc/rc.d/varnish.sh restart is same as before (no errors). Is there any other place that I could poke to see what is braking varnish?

marcelloc

xudus,

check with netstat -an if varnish port are still up
check with ps ax | grep -i varnish if varnish is still running.

You can also create a cron job to restart varnish after two days for example to prevent this random error.

att,
Marcello Coutinho

xudus

Marcello,

Varnish is running and port 80 listening (*.80). Restarting varnish does not help. Restarting pfs does.

xudus

I disabled squidGuard (1.4_2 pkg v.1.9.1) and everything is working so far for the last 14 days. I'll give it another week or two before re-enabling squidGuard again.

xudus

After 20 days varnish goes belly up. Will be removing squid and squidGuard to see what difference it makes. There is no love between those three.

BTW does anybody have pfBlocker, pfflowd, squid, squidGuard and Varnish installed and stable on pfs 2.0.1?