Your message dated Mon, 23 May 2016 16:45:59 +0200 with message-id <[email protected]> and subject line Fixed in 4.1.0 has caused the Debian Bug report #815713, regarding varnish: Assert error in SES_ScheduleReq(), cache/cache_session.c line 229 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 815713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815713 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: varnish Version: 4.0.2-1 Severity: important Dear Maintainer, Varnish child dies. There is output from panic.show: varnish> panic.show 200 Last panic at: Tue, 23 Feb 2016 17:47:26 GMT Assert error in SES_ScheduleReq(), cache/cache_session.c line 229: Condition((sp)->magic == 0x2c2f9c5a) not true. thread = (cache-worker) ident = Linux,3.16.0-4-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x4330a8: /usr/sbin/varnishd() [0x4330a8] 0x43baed: /usr/sbin/varnishd(SES_ScheduleReq+0x18d) [0x43baed] 0x425208: /usr/sbin/varnishd() [0x425208] 0x4276d0: /usr/sbin/varnishd(HSH_DerefObjCore+0x1a0) [0x4276d0] 0x4176b7: /usr/sbin/varnishd(VBO_DerefBusyObj+0x1b7) [0x4176b7] 0x436e31: /usr/sbin/varnishd(CNT_Request+0x391) [0x436e31] 0x42d18b: /usr/sbin/varnishd(HTTP1_Session+0x3eb) [0x42d18b] 0x43b537: /usr/sbin/varnishd() [0x43b537] 0x43c508: /usr/sbin/varnishd(SES_pool_accept_task+0x2a8) [0x43c508] 0x435cdc: /usr/sbin/varnishd(Pool_Work_Thread+0x39c) [0x435cdc] req = 0x7f4fcce1d020 { sp = 0x7f4fb2d56960, vxid = 1075576888, step = R_STP_DELIVER, req_body = R_BODY_NONE, err_code = 200, err_reason = (null), restarts = 0, esi_level = 0 sp = 0x7f4fb2d56960 { fd = 687, vxid = 1835061, client = 178.16.38.139 64141, step = S_STP_WORKING, }, worker = 0x7f4fc3422c90 { ws = 0x7f4fc3422ea8 { id = "wrk", {s,f,r,e} = {0x7f4fc3422490,0x7f4fc3422490,(nil),+2048}, }, VCL::method = 0x0, VCL::return = deliver, }, ws = 0x7f4fcce1d1b8 { id = "req", {s,f,r,e} = {0x7f4fcce1f010,+712,(nil),+57360}, }, Output truncated Bug explained here: https://www.varnish-cache.org/trac/ticket/1607 Fixed here: https://www.varnish-cache.org/trac/changeset/9a2a221c713b7329231d7a1b9e996a4a41eedcf2 -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages varnish depends on: ii adduser 3.113+nmu3 ii gcc 4:4.9.2-2 ii init-system-helpers 1.22 ii libc6 2.19-18+deb8u3 ii libc6-dev [libc-dev] 2.19-18+deb8u3 ii libedit2 3.1-20140620-2 ii libjemalloc1 3.6.0-3 ii libncurses5 5.9+20140913-1+b1 ii libpcre3 2:8.35-3.3+deb8u2 ii libtinfo5 5.9+20140913-1+b1 ii libvarnishapi1 4.0.2-1 varnish recommends no packages. Versions of packages varnish suggests: pn varnish-doc <none> -- Configuration Files: /etc/default/varnish changed [not included] /etc/varnish/default.vcl [Errno 2] No such file or directory: u'/etc/varnish/default.vcl' -- no debconf information
--- End Message ---
--- Begin Message ---Version: 4.1.0-1 This bug was fixed in commit 9a2a221c713b7329231d7a1b9e996a4a41eedcf2 in the upstream repository. This commit was first included in Varnish 4.1.0 -- Stig Sandbeck Mathisen <[email protected]>
--- End Message ---
