[Varnish] #1825: Cannot Start Varnish After Just Restarting The Service
Varnish
varnish-bugs at varnish-cache.org
Wed Dec 2 10:34:45 CET 2015
#1825: Cannot Start Varnish After Just Restarting The Service
------------------------+--------------------
Reporter: ghostshell | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: varnishd | Version: 4.1.0
Severity: major | Resolution:
Keywords: |
------------------------+--------------------
Changes (by fgsch):
* version: 4.1.0-TP1 => 4.1.0
* milestone: Varnish 4.1-TP1 =>
Old description:
> I upgraded via the CentOS package manager using the official repo from v4
> to v4.1, had a small issue which I got fixed and everything was working
> fine. I needed to restart the varnish service yesterday and now it shows
> started but when I check the status of varnish or go to a web site hosted
> on the server the service shows not started and I cannot access any of my
> sites. I was able to get the access log going again, but I cannot figure
> out how to get the log going showing varnish startup/service errors or
> the success messages when it goes to start so all I have is the log info
> from messages which is:
>
> Nov 30 23:30:42 www varnishd[16665]: Child (16667) not responding to CLI,
> killing it.
> Nov 30 23:30:42 www varnishd[16665]: Child (16667) died signal=11 (core
> dumped)
> Nov 30 23:30:42 www varnishd[16665]: Child (16667) Panic message:#012
> Assert error in child_sigsegv_handler(), mgt/mgt_child.c line 297:#012
> Condition(Segmentation fault by instruction at 0x205970) not
> true.#012thread = (cache-worker)#012version = varnish-4.1.0 revision
> 3041728#012ident =
> Linux,2.6.32-573.8.1.el6.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit,epoll#012Backtrace:#012
> 0x432483: varnishd() [0x432483]#012 0x450de9: varnishd() [0x450de9]#012
> 0x34a480f790: libpthread.so.0() [0x34a480f790]#012 0x43c2b9:
> varnishd(VCL_DefaultDirector+0x19) [0x43c2b9]#012 0x436b9e:
> varnishd(CNT_Request+0x74e) [0x436b9e]#012 0x44cc3b:
> varnishd(HTTP1_Session+0x11b) [0x44cc3b]#012 0x439921:
> varnishd(SES_Proto_Req+0x61) [0x439921]#012 0x447aed: varnishd()
> [0x447aed]#012 0x447eeb: varnishd() [0x447eeb]#012 0x34a4807a51:
> libpthread.so.0() [0x34a4807a51]#012req = 0x7fe026896020 {#012 vxid = 2,
> step = R_STP_RECV,#012 req_body = R_BODY_NONE,#012 restarts = 0,
> esi_level = 0,#012 sp = 0x7fe02640f420 {#012 fd = 13, vxid = 1,#012
> client = 180.76.15.6 56796,#012 step = S_STP_H1PROC,#012 },#012
> worker = 0x7fe02d7eebc0 {#012 stack = {0x7fe02d7ef000 ->
> 0x7fe02d7e3000},#012 ws = 0x7fe02d7eedb8 {#012 id = "wrk",#012
> {s,f,r,e} = {0x7fe02d7ee380,0x7fe02d7ee380,(nil),+2040},#012 },#012
> VCL::method = none,#012 ws = 0x7fe026896200 {#012 id = "req",#012
> {s,f,r,e} = {0x7fe026898000,+216,(nil),+57336},#012 },#012
> http_conn = 0x7fe026896128 {#012 fd = 13,#012 doclose =
> NULL,#012 ws = 0x7fe026896200,#012 {rxbuf_b, rxbuf_e} =
> {0x7fe026898000, 0x7fe0268980b8},#012 {pipeline_b, pipeline_e} =
> {(nil), (nil)},#012 content_length = -1,#012 body_status =
> none,#012 first_byte_timeout = 0.000000,#012
> between_bytes_timeout = 0.000000,#012 },#012 http[req] =
> 0x7fe026896298 {#012 ws[req] = 0x7fe026896200,#012 hdrs {#012
> "GET",#012 "/",#012 "HTTP/1.1",#012 "Host:
> wsww",#012 "Accept-Lang
> Nov 30 23:30:42 www varnishd[16665]: child (17228) Started
> Nov 30 23:30:43 www varnishd[16665]: Pushing vcls failed:#012Could not
> load compiled VCL.#012#011dlopen(vcl_boot/vgc.so) = vcl_boot/vgc.so:
> cannot open shared object file: No such file or directory
> Nov 30 23:30:44 www varnishd[16665]: Child (17228) ended
> Nov 30 23:30:44 www varnishd[16665]: Child (17228) said Child starts
> Nov 30 23:30:44 www varnishd[16665]: Child (17228) said Child dies
> Nov 30 23:31:53 www named[2444]: error (network unreachable) resolving
> 'www.amazon.it/A/IN': 2001:502:4612::1#53
> Nov 30 23:32:20 www varnishd[16665]: Manager got SIGINT
> Nov 30 23:32:24 www varnishd[18670]: Platform:
> Linux,2.6.32-573.8.1.el6.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit
> Nov 30 23:32:24 www varnishd[18670]: child (18672) Started
> Nov 30 23:32:24 www varnishd[18670]: Child (18672) said Child starts
> Nov 30 23:32:51 www varnishd[18670]: Manager got SIGINT
> Nov 30 23:32:52 www varnishd[18670]: Child (18672) ended
> Nov 30 23:32:52 www varnishd[18670]: Child (18672) said Child die
>
> All my sites are currently down, the only solution I have for the moment
> is to downgrade to 4.0 from 4.1.0-1. I tested the downgrade and the
> service and my sites came right online once the downgrade was complete. I
> would like to keep updated.
New description:
I upgraded via the CentOS package manager using the official repo from v4
to v4.1, had a small issue which I got fixed and everything was working
fine. I needed to restart the varnish service yesterday and now it shows
started but when I check the status of varnish or go to a web site hosted
on the server the service shows not started and I cannot access any of
my sites. I was able to get the access log going again, but I cannot
figure out how to get the log going showing varnish startup/service
errors or the success messages when it goes to start so all I have is
the log info from messages which is:
{{{
Nov 30 23:30:42 www varnishd[16665]: Child (16667) not responding to CLI,
killin
g it.
Nov 30 23:30:42 www varnishd[16665]: Child (16667) died signal=11 (core
dumped)
Nov 30 23:30:42 www varnishd[16665]: Child (16667) Panic message:
Assert error in child_sigsegv_handler(), mgt/mgt_child.c line 297:
Condition(Segmentation fault by instruction at 0x205970) not true.
thread = (cache-worker)
version = varnish-4.1.0 revision 3041728
ident =
Linux,2.6.32-573.8.1.el6.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbi
t,epoll
Backtrace:
0x432483: varnishd() [0x432483]
0x450de9: varnishd() [0x450de9]
0x34a480f790: libpthread.so.0() [0x34a480f790]
0x43c2b9: varnishd(VCL_DefaultDirector+0x19) [0x43c2b9]
0x436b9e: varnishd(CNT_Request+0x74e) [0x436b9e]
0x44cc3b: varnishd(HTTP1_Session+0x11b) [0x44cc3b]
0x439921: varnishd(SES_Proto_Req+0x61) [0x439921]
0x447aed: varnishd() [0x447aed]
0x447eeb: varnishd() [0x447eeb]
0x34a4807a51: libpthread.so.0() [0x34a4807a51]
req = 0x7fe026896020 {
vxid = 2, step = R_STP_RECV,
req_body = R_BODY_NONE,
restarts = 0, esi_level = 0,
sp = 0x7fe02640f420 {
fd = 13, vxid = 1,
client = 180.76.15.6 56796,
step = S_STP_H1PROC,
},
worker = 0x7fe02d7eebc0 {
stack = {0x7fe02d7ef000 -> 0x7fe02d7e3000},
ws = 0x7fe02d7eedb8 {
id = "wrk",
{s,f,r,e} = {0x7fe02d7ee380,0x7fe02d7ee380,(nil),+2040},
},
VCL::method = none,
ws = 0x7fe026896200 {
id = "req",
{s,f,r,e} = {0x7fe026898000,+216,(nil),+57336},
},
http_conn = 0x7fe026896128 {
fd = 13,
doclose = NULL,
ws = 0x7fe026896200,
{rxbuf_b, rxbuf_e} = {0x7fe026898000, 0x7fe0268980b8},
{pipeline_b, pipeline_e} = {(nil), (nil)},
content_length = -1,
body_status = none,
first_byte_timeout = 0.000000,
between_bytes_timeout = 0.000000,
},
http[req] = 0x7fe026896298 {
ws[req] = 0x7fe026896200,
hdrs {
"GET",
"/",
"HTTP/1.1",
"Host: wsww",
"Accept-Lang
Nov 30 23:30:42 www varnishd[16665]: child (17228) Started
Nov 30 23:30:43 www varnishd[16665]: Pushing vcls failed:
Could not load compiled VCL.
#011dlopen(vcl_boot/vgc.so) = vcl_boot/vgc.so: cannot open shared object
file: N
o such file or directory
Nov 30 23:30:44 www varnishd[16665]: Child (17228) ended
Nov 30 23:30:44 www varnishd[16665]: Child (17228) said Child starts
Nov 30 23:30:44 www varnishd[16665]: Child (17228) said Child dies
Nov 30 23:31:53 www named[2444]: error (network unreachable) resolving
'www.amaz
on.it/A/IN': 2001:502:4612::1#53
Nov 30 23:32:20 www varnishd[16665]: Manager got SIGINT
Nov 30 23:32:24 www varnishd[18670]: Platform:
Linux,2.6.32-573.8.1.el6.x86_64,x
86_64,-junix,-smalloc,-smalloc,-hcritbit
Nov 30 23:32:24 www varnishd[18670]: child (18672) Started
Nov 30 23:32:24 www varnishd[18670]: Child (18672) said Child starts
Nov 30 23:32:51 www varnishd[18670]: Manager got SIGINT
Nov 30 23:32:52 www varnishd[18670]: Child (18672) ended
Nov 30 23:32:52 www varnishd[18670]: Child (18672) said Child die
}}}
All my sites are currently down, the only solution I have for the
moment is to downgrade to 4.0 from 4.1.0-1. I tested the downgrade
and the service and my sites came right online once the downgrade was
complete. I would like to keep updated.
--
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1825#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list