[Varnish] #1054: Child not responding to CLI, killing it
Varnish
varnish-bugs at varnish-cache.org
Mon Dec 17 12:35:43 CET 2012
#1054: Child not responding to CLI, killing it
---------------------------+-----------------------
Reporter: scorillo | Owner: lkarsten
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: documentation | Version: 3.0.2
Severity: normal | Resolution:
Keywords: |
---------------------------+-----------------------
Comment (by martin):
Hi,
We believe that what you are experiencing is due to resource exhaustion on
your virtual machine, and the monitoring thread in Varnish is being
starved.
The memory available to your Varnish instance seems on the low side, with
only 2GB configured on the VM. This should be increased. If that is not
possible, you could prevent Varnish scaling up to using too much memory by
setting a much lower max number of threads. Maybe as low as 100-150.
You could also try to disable the core dumps on the box to see if there
are any hidden panic message that gets eaten due to cores taking too long
time. Though I don't expect this to be the case.
Regards,
Martin Blix Grydeland
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1054#comment:15>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list