From varnish-bugs at varnish-cache.org Thu Mar 1 13:35:57 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 01 Mar 2012 13:35:57 -0000 Subject: [Varnish] #1077: "Assert error in smp_open_segs" panic with persistent storage In-Reply-To: <043.c165512d738b197b7405085ff64f8c95@varnish-cache.org> References: <043.c165512d738b197b7405085ff64f8c95@varnish-cache.org> Message-ID: <052.92093ba671859db8acd28bce1f613c04@varnish-cache.org> #1077: "Assert error in smp_open_segs" panic with persistent storage ----------------------+----------------------------------------------------- Reporter: acdha | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: critical | Keywords: ----------------------+----------------------------------------------------- Comment(by timbunce): Same problem here. varnishd (varnish-3.0.2 revision 55e70a4) on CentOS 6. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Mar 3 21:10:55 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 03 Mar 2012 21:10:55 -0000 Subject: [Varnish] #1100: Assert error in stv_alloc(), stevedore.c line 144 In-Reply-To: <042.63d2077ebde3a5ab8b3d16b5f7a5e9eb@varnish-cache.org> References: <042.63d2077ebde3a5ab8b3d16b5f7a5e9eb@varnish-cache.org> Message-ID: <051.e31abdd2ef4673d6a1774e57a02fb978@varnish-cache.org> #1100: Assert error in stv_alloc(), stevedore.c line 144 -------------------+-------------------------------------------------------- Reporter: Roze | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Keywords: | -------------------+-------------------------------------------------------- Comment(by Roze): I updated to 2012-02-28 trunk snapshot and now I get different assert (also now 'panic.show' worked). Could it be that just the CLI timeout is too low for the 'free space' operations? {{{ Mar 3 21:46:10 is50 varnishd[18147]: Child (18148) not responding to CLI, killing it. Mar 3 21:46:10 is50 varnishd[18147]: Child (18148) not responding to CLI, killing it. Mar 3 21:46:10 is50 varnishd[18147]: Child (18148) died signal=6 Mar 3 21:46:10 is50 varnishd[18147]: Child (18148) Panic message: Assert error in vfp_nop_bytes(), cache/cache_fetch.c line 115:#012 Condition((bo->fetch_failed) == 0) not true.#012errno = 104 (Connection reset by peer)#012thread = (cache-worker)#012ident = Linux,3.2.0-rc2-2-default,x86_64,-sfile,-sfile,-smalloc,-Mar 3 21:46:11 is50 varnishd[18147]: Child cleanup complete Mar 3 21:46:11 is50 varnishd[18147]: child (27817) Started Mar 3 21:46:11 is50 varnishd[18147]: Child (27817) said Child starts Mar 3 21:46:11 is50 varnishd[18147]: Child (27817) said SMF.s0 mmap'ed 107374182400 bytes of 107374182400 Mar 3 21:46:11 is50 varnishd[18147]: Child (27817) said SMF.s1 mmap'ed 107374182400 bytes of 107374182400 }}} {{{ 200 ----------------------------- Varnish Cache CLI 1.0 ----------------------------- Linux,3.2.0-rc2-2-default,x86_64,-sfile,-sfile,-smalloc,-hcritbit Type 'help' for command list. Type 'quit' to close CLI session. panic.show 200 Last panic at: Sat, 03 Mar 2012 19:46:10 GMT Assert error in vfp_nop_bytes(), cache/cache_fetch.c line 115: Condition((bo->fetch_failed) == 0) not true. errno = 104 (Connection reset by peer) thread = (cache-worker) ident = Linux,3.2.0-rc2-2-default,x86_64,-sfile,-sfile,-smalloc,-hcritbit,epoll Backtrace: 0x430ea8: pan_ic+d8 0x424755: vfp_nop_bytes+c5 0x425716: FetchBody+8e6 0x4169f4: cnt_fetchbody+104 0x418eb5: CNT_Session+415 0x434879: ses_pool_task+f9 0x43324f: Pool_Work_Thread+10f 0x43f589: wrk_thread_real+b9 0x7f4800ca6a4f: _end+7f4800622297 0x7f4800a1091d: _end+7f480038c165 sp = 0x7f15078d9a20 { fd = 373, id = 373, xid = 235842465, client = 10.0.10.1 3657, step = STP_FETCHBODY, handling = deliver, err_code = 200, err_reason = (null), restarts = 0, esi_level = 0 busyobj = 0x7f1503fb0040 { ws = 0x7f1503fb0080 { id = "bo", {s,f,r,e} = {0x7f1503fb1a90,+10160,(nil),+58768}, }, is_gunzip bodystatus = 4, }, http[bereq] = { ws = 0x7f1503fb0080[bo] "GET", "/profile_gal/897/440/v2/l_897440.jpg", "HTTP/1.1", "Host: i0.imgdomain.com", "User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11", "Accept: */*", "Accept-Language: lv-LV,lv;q=0.8,en-US;q=0.6,en;q=0.4", "Accept-Charset: windows-1257,utf-8;q=0.7,*;q=0.3", "X-Varnish: 235842465", "Accept-Encoding: gzip", }, http[beresp] = { ws = 0x7f1503fb0080[bo] "HTTP/1.1", "200", "OK", "Date: Sat, 03 Mar 2012 19:46:06 GMT", "Content-Type: image/jpeg", "Content-Length: 127992", "Last-Modified: Sat, 08 Oct 2011 22:30:33 GMT", "Connection: keep-alive", "Expires: Thu, 31 Dec 2037 23:55:55 GMT", "Cache-Control: max-age=315360000", "Accept-Ranges: bytes", }, ws = 0x7f1506002150 { id = "req", {s,f,r,e} = {0x7f1506003728,+520,(nil),+59640}, }, http[req] = { ws = 0x7f1506002150[req] "GET", "/profile_gal/897/440/v2/l_897440.jpg", "HTTP/1.1", "Host: i0.imgdomain.com", "Connection: keep-alive", "User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11", "Accept: */*", "Accept-Language: lv-LV,lv;q=0.8,en-US;q=0.6,en;q=0.4", "Accept-Charset: windows-1257,utf-8;q=0.7,*;q=0.3", }, worker = 0x7f15e4be6c90 { ws = 0x7f15e4be6e50 { id = "wrk", {s,f,r,e} = {0x7f15e4be6480,0x7f15e4be6480,(nil),+2048}, }, }, vcl = { srcname = { "input", "Default", }, }, obj = 0x7f2d37652000 { xid = 235842465, ws = 0x7f2d37652018 { id = "obj", {s,f,r,e} = {0x7f2d376521e8,+224,(nil),+280}, }, http[obj] = { ws = 0x7f2d37652018[obj] "HTTP/1.1", "OK", "Date: Sat, 03 Mar 2012 19:46:06 GMT", "Content-Type: image/jpeg", "Last-Modified: Sat, 08 Oct 2011 22:30:33 GMT", "Expires: Thu, 31 Dec 2037 23:55:55 GMT", "Cache-Control: max-age=315360000", }, len = 0, store = { }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 5 11:12:16 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Mar 2012 11:12:16 -0000 Subject: [Varnish] #1102: content delivered looks encrypted In-Reply-To: <045.99dc27835f0e5b7a71acb5d6209a1e56@varnish-cache.org> References: <045.99dc27835f0e5b7a71acb5d6209a1e56@varnish-cache.org> Message-ID: <054.e8930add62ceff7fa4acd35a8b2b348f@varnish-cache.org> #1102: content delivered looks encrypted ---------------------------------+------------------------------------------ Reporter: gnollet | Type: defect Status: new | Priority: normal Milestone: Varnish 2.1 release | Component: varnishd Version: 2.1.5 | Severity: normal Keywords: | ---------------------------------+------------------------------------------ Comment(by tfheen): Could you please provide output of varnishlog showing the problem? A copy of your VCL would also be useful. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 5 11:28:01 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Mar 2012 11:28:01 -0000 Subject: [Varnish] #1100: Assert error in stv_alloc(), stevedore.c line 144 In-Reply-To: <042.63d2077ebde3a5ab8b3d16b5f7a5e9eb@varnish-cache.org> References: <042.63d2077ebde3a5ab8b3d16b5f7a5e9eb@varnish-cache.org> Message-ID: <051.a5c5735abf081b416f9658654496c3b4@varnish-cache.org> #1100: Assert error in stv_alloc(), stevedore.c line 144 ---------------------+------------------------------------------------------ Reporter: Roze | Type: defect Status: closed | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Resolution: fixed | Keywords: ---------------------+------------------------------------------------------ Changes (by Poul-Henning Kamp ): * status: new => closed * resolution: => fixed Comment: (In [f9e413c77249b0b6c407c087836a1cd80d72d1ab]) Don't assert if we fail to get storage in VFP_Begin() Fixes #1100 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 5 11:34:00 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Mar 2012 11:34:00 -0000 Subject: [Varnish] #1102: content delivered looks encrypted In-Reply-To: <045.99dc27835f0e5b7a71acb5d6209a1e56@varnish-cache.org> References: <045.99dc27835f0e5b7a71acb5d6209a1e56@varnish-cache.org> Message-ID: <054.a98e2e2ecec10d63cd3b1997cfa8cefe@varnish-cache.org> #1102: content delivered looks encrypted ---------------------------------+------------------------------------------ Reporter: gnollet | Type: defect Status: new | Priority: normal Milestone: Varnish 2.1 release | Component: varnishd Version: 2.1.5 | Severity: normal Keywords: | ---------------------------------+------------------------------------------ Comment(by gnollet): Hello, It's not easy to capture output of varnishlog because the problem appears only few time a day. But last week, i got the problem, then I did wget of the faulty page and I could analyze it. Finally, the oage is gzipped ans stored on the cache in this state but the content-type of this page is not transmit to web browser. If I mannually unzip this page, the result is readble. Then, I search about similar problem and apparently varnish 3 is full native with gzip, then we treid to upgrade to this new version and the result is OK, since the upgrade, there is no more issue. Regards Gilles -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 6 15:21:32 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Mar 2012 15:21:32 -0000 Subject: [Varnish] #1103: example for authentication in wiki Message-ID: <065.d06e06dadd8e2a51076548590047a8bb@varnish-cache.org> #1103: example for authentication in wiki -----------------------------------------+---------------------------------- Reporter: thibault.ketterer@? | Type: documentation Status: new | Priority: low Milestone: | Component: documentation Version: 2.1.5 | Severity: normal Keywords: | -----------------------------------------+---------------------------------- You may add this example in the wiki challenge = "ixslvvxrgkjptxmcgnnsdxsvdmvfympg" secret = "foo\n" import hashlib print hashlib.sha256(challenge + "\n" + secret + challenge + "\n").hexdigest() https://www.varnish-cache.org/trac/wiki/CLI#Authentication:Thegorydetails I spent 1 hour searching why my authentication was not working, I had not seen the "\n" at the end of the secret file. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 6 15:23:47 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Mar 2012 15:23:47 -0000 Subject: [Varnish] #1103: example for authentication in wiki In-Reply-To: <065.d06e06dadd8e2a51076548590047a8bb@varnish-cache.org> References: <065.d06e06dadd8e2a51076548590047a8bb@varnish-cache.org> Message-ID: <074.8754913d13f332f66e2f70821b4227b2@varnish-cache.org> #1103: example for authentication in wiki -----------------------------------------+---------------------------------- Reporter: thibault.ketterer@? | Type: documentation Status: new | Priority: low Milestone: | Component: documentation Version: 2.1.5 | Severity: normal Keywords: | -----------------------------------------+---------------------------------- Comment(by thibault.ketterer@?): re-written the code {{{ import hashlib challenge = "ixslvvxrgkjptxmcgnnsdxsvdmvfympg" secret = "foo\n" print hashlib.sha256(challenge + "\n" + secret + challenge + "\n").hexdigest() }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 8 18:00:09 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 08 Mar 2012 18:00:09 -0000 Subject: [Varnish] #1104: Duplicate Date headers Message-ID: <042.8a0ed17d7e67a9f44306f0deae7980c1@varnish-cache.org> #1104: Duplicate Date headers -------------------+-------------------------------------------------------- Reporter: Roze | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: | -------------------+-------------------------------------------------------- Varnish sends additional Date header with the date when the object was first fetched (on first request the dates are identical). {{{ wget -S http://10.0.0.1/251324940.jpg HTTP/1.1 200 OK Date: Thu, 08 Mar 2012 17:47:45 GMT Content-Type: image/jpeg Last-Modified: Thu, 08 Mar 2012 17:23:43 GMT Expires: Thu, 31 Dec 2037 23:55:55 GMT Cache-Control: max-age=315360000 Content-Length: 126142 Date: Thu, 08 Mar 2012 17:47:45 GMT Age: 0 Connection: keep-alive }}} and a second request (after ~10 sec) {{{ HTTP/1.1 200 OK Date: Thu, 08 Mar 2012 17:47:45 GMT Content-Type: image/jpeg Last-Modified: Thu, 08 Mar 2012 17:23:43 GMT Expires: Thu, 31 Dec 2037 23:55:55 GMT Cache-Control: max-age=315360000 Content-Length: 126142 Date: Thu, 08 Mar 2012 17:47:54 GMT Age: 9 Connection: keep-alive X-Cache: HIT }}} On both requests there are 2 Date headers. Can be seen also from varnishlog: {{{ 2738 TxResponse c OK 2738 TxHeader c Date: Thu, 08 Mar 2012 17:47:45 GMT 2738 TxHeader c Content-Type: image/jpeg 2738 TxHeader c Last-Modified: Thu, 08 Mar 2012 14:11:23 GMT 2738 TxHeader c Expires: Thu, 31 Dec 2037 23:55:55 GMT 2738 TxHeader c Cache-Control: max-age=315360000 2738 TxHeader c Content-Length: 126142 2738 TxHeader c Date: Thu, 08 Mar 2012 17:47:45 GMT 2738 TxHeader c Age: 0 2738 TxHeader c Connection: keep-alive }}} Doesn't happen with 2.1.5. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Mar 11 07:48:27 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 11 Mar 2012 07:48:27 -0000 Subject: [Varnish] #1104: Duplicate Date headers In-Reply-To: <042.8a0ed17d7e67a9f44306f0deae7980c1@varnish-cache.org> References: <042.8a0ed17d7e67a9f44306f0deae7980c1@varnish-cache.org> Message-ID: <051.726bbe66fbb21dafedc3722b4c00f964@varnish-cache.org> #1104: Duplicate Date headers ---------------------+------------------------------------------------------ Reporter: Roze | Type: defect Status: closed | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Resolution: fixed | Keywords: ---------------------+------------------------------------------------------ Changes (by Poul-Henning Kamp ): * status: new => closed * resolution: => fixed Comment: (In [e725920a03e5329949635ced22d02f52ab91a5b9]) Remove old Date: header before adding our new one. Submitted by: scoof Fixes #1104 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Mar 11 20:06:00 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 11 Mar 2012 20:06:00 -0000 Subject: [Varnish] #1105: varnish cache server Message-ID: <058.489efa3db9cc390e12284401be951deb@varnish-cache.org> #1105: varnish cache server ----------------------------------+----------------------------------------- Reporter: varnish cache server | Type: task Status: new | Priority: lowest Milestone: Later | Component: build Version: trunk | Severity: trivial Keywords: | ----------------------------------+----------------------------------------- Varnish is an HTTP accelerator designed for content-heavy dynamic web sites. '''[http://www.adminspoint.com/web-servers/1551-what-varnish-cache- server.html varnish cache server]''' In contrast to other HTTP accelerators, such as Squid, which began life as a client-side cache, or Apache and nginx, which are primarily origin servers, Varnish was designed from the ground up as an HTTP accelerator. Varnish is focused exclusively on HTTP, unlike other proxy servers that often support FTP, SMTP and other network protocols. While Varnish is designed to reduce contention between threads to a minimum, its authors claim that its performance will only be as good as that of the system's pthreads implementation. Additionally, a poor malloc implementation may add unnecessary contention and thereby limit performance. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 12 09:33:19 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Mar 2012 09:33:19 -0000 Subject: [Varnish] #1106: Document vcl regex Message-ID: <042.b934242b60e7a17b40b71c3885fc8440@varnish-cache.org> #1106: Document vcl regex -------------------+-------------------------------------------------------- Reporter: neaj | Type: documentation Status: new | Priority: normal Milestone: | Component: build Version: 3.0.0 | Severity: normal Keywords: | -------------------+-------------------------------------------------------- vcl.7 should mention that varnish uses POSIX regex, together with any differences if applicable. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 12 11:06:57 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Mar 2012 11:06:57 -0000 Subject: [Varnish] #1103: example for authentication in wiki In-Reply-To: <065.d06e06dadd8e2a51076548590047a8bb@varnish-cache.org> References: <065.d06e06dadd8e2a51076548590047a8bb@varnish-cache.org> Message-ID: <074.41c5b6d2019945db8a9df78eed5d9400@varnish-cache.org> #1103: example for authentication in wiki -----------------------------------------+---------------------------------- Reporter: thibault.ketterer@? | Owner: scoof Type: documentation | Status: new Priority: low | Milestone: Component: documentation | Version: 2.1.5 Severity: normal | Keywords: -----------------------------------------+---------------------------------- Changes (by scoof): * owner: => scoof -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 12 11:07:22 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Mar 2012 11:07:22 -0000 Subject: [Varnish] #1102: content delivered looks encrypted In-Reply-To: <045.99dc27835f0e5b7a71acb5d6209a1e56@varnish-cache.org> References: <045.99dc27835f0e5b7a71acb5d6209a1e56@varnish-cache.org> Message-ID: <054.a6f11c3c9487fd69d3243975c3949561@varnish-cache.org> #1102: content delivered looks encrypted ----------------------------------+----------------------------------------- Reporter: gnollet | Type: defect Status: closed | Priority: normal Milestone: Varnish 2.1 release | Component: varnishd Version: 2.1.5 | Severity: normal Resolution: invalid | Keywords: ----------------------------------+----------------------------------------- Changes (by tfheen): * status: new => closed * resolution: => invalid Comment: Closing this as unreproducible as it was fixed by an upgrade. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 12 11:11:55 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Mar 2012 11:11:55 -0000 Subject: [Varnish] #1103: example for authentication in wiki In-Reply-To: <065.d06e06dadd8e2a51076548590047a8bb@varnish-cache.org> References: <065.d06e06dadd8e2a51076548590047a8bb@varnish-cache.org> Message-ID: <074.67142a390501414f0bf8256004e5fa40@varnish-cache.org> #1103: example for authentication in wiki -----------------------------------------+---------------------------------- Reporter: thibault.ketterer@? | Owner: scoof Type: documentation | Status: closed Priority: low | Milestone: Component: documentation | Version: 2.1.5 Severity: normal | Resolution: fixed Keywords: | -----------------------------------------+---------------------------------- Changes (by scoof): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 12 11:43:19 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Mar 2012 11:43:19 -0000 Subject: [Varnish] #1106: Document vcl regex In-Reply-To: <042.b934242b60e7a17b40b71c3885fc8440@varnish-cache.org> References: <042.b934242b60e7a17b40b71c3885fc8440@varnish-cache.org> Message-ID: <051.6164e193f758c604225a6b37a6e6dccd@varnish-cache.org> #1106: Document vcl regex -------------------------+-------------------------------------------------- Reporter: neaj | Type: documentation Status: closed | Priority: normal Milestone: | Component: build Version: 3.0.0 | Severity: normal Resolution: worksforme | Keywords: -------------------------+-------------------------------------------------- Changes (by tfheen): * status: new => closed * resolution: => worksforme Comment: In vcl.7: In Varnish 2.1.0 Varnish switched to using PCRE - Perl-compatible regular expressions. For a complete description of PCRE please see the PCRE(3) man page. so this is already in place, under the heading "Regular expressions". -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 12 12:00:02 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Mar 2012 12:00:02 -0000 Subject: [Varnish] #1106: Document vcl regex In-Reply-To: <042.b934242b60e7a17b40b71c3885fc8440@varnish-cache.org> References: <042.b934242b60e7a17b40b71c3885fc8440@varnish-cache.org> Message-ID: <051.df38b968cb56557164018b1aa394d8d0@varnish-cache.org> #1106: Document vcl regex -------------------------+-------------------------------------------------- Reporter: neaj | Type: documentation Status: closed | Priority: normal Milestone: | Component: build Version: 3.0.0 | Severity: normal Resolution: worksforme | Keywords: -------------------------+-------------------------------------------------- Comment(by neaj): Strange: when I search in 2.1.5 I don't see the text you quote: {{{ jean at klippie:~/tmp/varnish-2.1.5$ grep Regular man/* jean at klippie:~/tmp/varnish-2.1.5$ grep -r "Regular expressions" * }}} Was it taken out? In the FAQ I do get hits: {{{ jean at klippie:~/tmp/varnish-2.1.5$ grep -r "we use PCRE" * ... doc/sphinx/faq/general.rst:From version 2.1.0 and forward, we use PCRE regular expressions, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 13 16:55:28 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 13 Mar 2012 16:55:28 -0000 Subject: [Varnish] #1107: Add ignore_saintmode to req Message-ID: <044.55eb1578247b1b264abd611b623e69b7@varnish-cache.org> #1107: Add ignore_saintmode to req -------------------------------+-------------------------------------------- Reporter: ismell | Type: enhancement Status: new | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Keywords: saintmode restart | -------------------------------+-------------------------------------------- With bug #1091 getting fixed there is no way to skip the saintmode check. Before you could just return (restart) and if there was no grace object it would call the same backend with the same request. Having the ability to skip the saintmode check allows us to return a non- ideal response instead of returning a 500 error. The attached patch adds a req.ignore_saintmode flag and includes a test case. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 15 14:46:51 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Mar 2012 14:46:51 -0000 Subject: [Varnish] #1051: child process died In-Reply-To: <045.f22d848aeef4ec1e301fd6d2603e1e88@varnish-cache.org> References: <045.f22d848aeef4ec1e301fd6d2603e1e88@varnish-cache.org> Message-ID: <054.b11a7c5ce5fb5f5d83c8a20067728c93@varnish-cache.org> #1051: child process died -----------------------+---------------------------------------------------- Reporter: sreniaw | Type: defect Status: reopened | Priority: normal Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Resolution: | Keywords: -----------------------+---------------------------------------------------- Changes (by sreniaw2): * status: closed => reopened * resolution: fixed => Comment: /var/lib/pgsql/${postgres_version}/data/postgresql.conf Replying to [comment:2 phk]: > Your -spersistent silo has been corrupted, and you should remove the file entirely. > > Please tell me if it happens again. We have experienced again same crash. Child process died and it wasn't able to recover. The problem was solved by deleting silo. {{{ Mar 13 21:17:14 CLI communication error (hdr) Mar 13 21:17:14 Condition(sg1->p.offset != sg->p.offset) not true. Mar 13 21:17:14 thread = (cache-main) Mar 13 21:17:14 ident = Linux,2.6.18-274.18.1.el5,x86_64,-smalloc,-spersistent,-smalloc,-hclassic,no_waiter Mar 13 21:17:14 Backtrace: Mar 13 21:17:14 0x42c7a6: /usr/sbin/varnishd [0x42c7a6] Mar 13 21:17:14 0x4472f5: /usr/sbin/varnishd [0x4472f5] Mar 13 21:17:14 0x4474bb: /usr/sbin/varnishd [0x4474bb] Mar 13 21:17:14 0x444d57: /usr/sbin/varnishd(STV_open+0x27) [0x444d57] Mar 13 21:17:14 0x42b525: /usr/sbin/varnishd(child_main+0xc5) [0x42b525] Mar 13 21:17:14 0x43d5ec: /usr/sbin/varnishd [0x43d5ec] Mar 13 21:17:14 0x43d852: /usr/sbin/varnishd(MGT_Run+0x1c2) [0x43d852] Mar 13 21:17:14 0x44cacb: /usr/sbin/varnishd(main+0xd1b) [0x44cacb] Mar 13 21:17:14 0x3411c1d994: /lib64/libc.so.6(__libc_start_main+0xf4) [0x3411c1d994] Mar 13 21:17:14 0x40ba79: /usr/sbin/varnishd(VCLS_func_help+0x81) [0x40ba79] }}} {{{ # ps axu | grep varnishd root 21704 0.0 0.0 63026924 1216 ? Ss 21:17 0:00 /usr/sbin/varnishd -P /var/run/varnish.pid -a :80 -T localhost:6082 -f /etc/varnish/default.vcl -u varnish -g varnish -S /etc/varnish/secret -p lru_interval 20 -p cli_timeout 60 -h classic,500009 -s malloc,30G -s persistent,/var/lib/varnish/store/silo,64424509440 -p thread_pool_min 500 -p thread_pool_max 4000 -p thread_pools 4 -p thread_pool_add_delay 2 -p session_linger 100 -p send_timeout 120 -p sess_timeout 10 -p listen_depth 4096 -p nuke_limit 50 root 21786 0.0 0.0 61140 704 pts/5 S+ 21:17 0:00 grep varnishd }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Mar 17 18:39:59 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 17 Mar 2012 18:39:59 -0000 Subject: [Varnish] #1108: SIGBUS during Deflate Message-ID: <045.8fb532fe38e889cac3469129c3fe8b9d@varnish-cache.org> #1108: SIGBUS during Deflate ---------------------+------------------------------------------------------ Reporter: phobe77 | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Varnish seems to (randomly?) crash during gzipping content: {{{ Last panic at: Sat, 17 Mar 2012 06:16:05 GMT Assert error in vmod_ch_sighandler(), vmod_crashhandler.c line 18: Condition(Caught signal 7) not true. thread = (cache-worker) ident = Linux,2.6.32-5-xen-amd64,x86_64,-sfile,-smalloc,-hcritbit,epoll Backtrace: 0x4307a5: /usr/sbin/varnishd() [0x4307a5] 0x7f80ef4e8a77: /usr/lib/varnish/vmods/libvmod_crashhandler.so(vmod_ch_sighandler+0x47) [0x7f80ef4e8a77] 0x7f8878a5c230: /lib/libc.so.6(+0x32230) [0x7f8878a5c230] 0x7f8878aa9a4b: /lib/libc.so.6(memcpy+0x15b) [0x7f8878aa9a4b] 0x7f8879884163: /usr/lib/varnish/libvgz.so(+0x2163) [0x7f8879884163] 0x7f8879884922: /usr/lib/varnish/libvgz.so(+0x2922) [0x7f8879884922] 0x7f8879885521: /usr/lib/varnish/libvgz.so(deflate+0x121) [0x7f8879885521] 0x426909: /usr/sbin/varnishd(VGZ_Gzip+0xa9) [0x426909] 0x41ed2a: /usr/sbin/varnishd() [0x41ed2a] 0x421186: /usr/sbin/varnishd(VEP_Finish+0xa6) [0x421186] sp = 0x7f80be543008 { fd = 12, id = 12, xid = 1221668465, client = 10.255.128.2 32830, step = STP_FETCHBODY, handling = deliver, err_code = 200, err_reason = (null), restarts = 0, esi_level = 0 flags = do_esi is_gzip bodystatus = 3 ws = 0x7f80be543080 { id = "sess", {s,f,r,e} = {0x7f80be543c90,+504,(nil),+262144}, }, http[req] = { ws = 0x7f80be543080[sess] "HEAD", "/bw-egas-eethen/7731064140411661", "HTTP/1.1", "Host: www.klusbedrijf-wijzer.nl", "Pragma: no-cache", "Accept: */*", "Proxy-Connection: Keep-Alive", "X-Prime: true", "X-Real-IP: 10.255.128.2", "X-UA-Browser: unk", "X-UA-Render: unk", "X-UA-Device: unk", "X-Forwarded-For: 10.255.128.2", }, worker = 0x7f80adcf7ab0 { ws = 0x7f80adcf7cf0 { id = "wrk", {s,f,r,e} = {0x7f80adce5a40,+2624,(nil),+65536}, }, http[bereq] = { ws = 0x7f80adcf7cf0[wrk] "GET", "/bw-egas-eethen/7731064140411661", "HTTP/1.1", "Host: www.klusbedrijf-wijzer.nl", "Pragma: no-cache", "Accept: */*", "Proxy-Connection: Keep-Alive", "X-Prime: true", "X-Real-IP: 10.255.128.2", "X-UA-Browser: unk", "X-UA-Render: unk", "X-UA-Device: unk", "X-Forwarded-For: 10.255.128.2", "X-Varnish: 1221668465", "Accept-Encoding: gzip", }, http[beresp] = { ws = 0x7f80adcf7cf0[wrk] "HTTP/1.1", "200", "OK", "P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"", "X-Depends: vcard-NL9fb5ef5e-c145-102d-aa25-00163e221d37, vcard- NL184fb9e6-c131-102d-aa25-00163e221d37, vcard-NLa1707800-c145-102d- aa25-00163e221d37, vcard-NL802227ec-c155-102d-aa25-00163e221d37, vcard- NLfdfea3ae-c13f-102d-aa25-00163e221d37, vcard-NL26526dde-c147-102d- aa25-00163e221d37, vcard-NL7c337bce-c158-102d-aa25-00163e221d37, vcard- NL8b33fdba-c13a-102d-aa25-00163e221d37, vcard-NLe77fbe96-c0af-102d- aa25-00163e221d37, vcard-NL6c5ab8e6-c141-102d-aa25-00163e221d37, vcard- NL87b9e540-c145-102d-aa25-00163e221d37, template", "Content-Type: text/html; charset=utf-8", "Last-Modified: Sat, 17 Mar 2012 04:19:21 GMT", "Content-Encoding: gzip", "Transfer-Encoding: chunked", "Date: Sat, 17 Mar 2012 04:19:21 GMT", "X-Request-Path: /bw-egas-eethen/7731064140411661", "X-Request-Url: www.klusbedrijf-wijzer.nl/bw-egas- eethen/7731064140411661", "Vary: Accept-Encoding,Cookie", "X-Reset-Age: true", "Cache-Control: public,max-age=86400", "X-I: yp-85,http6", }, }, vcl = { srcname = { "input", "Default", "useragent.vcl", "purge.vcl", }, }, obj = 0x7f86d7e0a000 { xid = 1221668465, ws = 0x7f86d7e0a018 { id = "obj", {s,f,r,e} = {0x7f86d7e0a258,+1056,(nil),+1104}, }, http[obj] = { ws = 0x7f86d7e0a018[obj] "HTTP/1.1", "OK", "P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"", "X-Depends: vcard-NL9fb5ef5e-c145-102d-aa25-00163e221d37, vcard- NL184fb9e6-c131-102d-aa25-00163e221d37, vcard-NLa1707800-c145-102d- aa25-00163e221d37, vcard-NL802227ec-c155-102d-aa25-00163e221d37, vcard- NLfdfea3ae-c13f-102d-aa25-00163e221d37, vcard-NL26526dde-c147-102d- aa25-00163e221d37, vcard-NL7c337bce-c158-102d-aa25-00163e221d37, vcard- NL8b33fdba-c13a-102d-aa25-00163e221d37, vcard-NLe77fbe96-c0af-102d- aa25-00163e221d37, vcard-NL6c5ab8e6-c141-102d-aa25-00163e221d37, vcard- NL87b9e540-c145-102d-aa25-00163e221d37, template", "Content-Type: text/html; charset=utf-8", "Last-Modified: Sat, 17 Mar 2012 04:19:21 GMT", "Content-Encoding: gzip", "Date: Sat, 17 Mar 2012 04:19:21 GMT", "X-Request-Path: /bw-egas-eethen/7731064140411661", "X-Request-Url: www.klusbedrijf-wijzer.nl/bw-egas- eethen/7731064140411661", "Vary: Accept-Encoding,Cookie", "X-Reset-Age: true", "Cache-Control: public,max-age=86400", "X-I: yp-85,http6", }, len = 3813, store = { 3813 { 1f 8b 08 00 00 00 00 00 00 03 02 00 00 00 ff ff |................| 6c 90 4d 4f c2 40 10 86 ef 24 fe 87 71 4f 9a d8 |l.MO. at ...$..qO..| ae 84 8b 08 e5 c0 47 a2 06 85 68 8d 7a 5c da 81 |......G...h.z\..| 2e 6e 67 71 3b b4 f8 ef dd 52 34 68 bc ec ee 3b |.ngq;....R4h...;| [3749 more] }, }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 19 11:25:53 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Mar 2012 11:25:53 -0000 Subject: [Varnish] #1108: SIGBUS during Deflate In-Reply-To: <045.8fb532fe38e889cac3469129c3fe8b9d@varnish-cache.org> References: <045.8fb532fe38e889cac3469129c3fe8b9d@varnish-cache.org> Message-ID: <054.9a11d22b648f15e0f2205e46c261d703@varnish-cache.org> #1108: SIGBUS during Deflate ---------------------+------------------------------------------------------ Reporter: phobe77 | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Comment(by martin): Hi, Do you know anything more specifically how to reproduce this error? How often does it occur, specific circumstances leading up to it etc. Please also attach the VCL configuration if possible, and varnishstat output. Could you also please confirm if this could be a out-of-storage situation? Is the file used for -sfile backing sparse? Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 19 22:04:25 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Mar 2012 22:04:25 -0000 Subject: [Varnish] #1108: SIGBUS during Deflate In-Reply-To: <045.8fb532fe38e889cac3469129c3fe8b9d@varnish-cache.org> References: <045.8fb532fe38e889cac3469129c3fe8b9d@varnish-cache.org> Message-ID: <054.833e2b39a72a5e102e5f31f7f9e79abb@varnish-cache.org> #1108: SIGBUS during Deflate ---------------------+------------------------------------------------------ Reporter: phobe77 | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Comment(by phobe77): Hi, after doing some more digging into the system it looks likely that it is a disk space issue. I think i have set the partition size to close to the cache size although the cache has never been filled to more than 30%. Have doubled the available disk space and restarted varnish. Lets see for a couple of days if this fixes the issue. For now you can close the case. Thanks for your support. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 20 08:44:25 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 20 Mar 2012 08:44:25 -0000 Subject: [Varnish] #1108: SIGBUS during Deflate In-Reply-To: <045.8fb532fe38e889cac3469129c3fe8b9d@varnish-cache.org> References: <045.8fb532fe38e889cac3469129c3fe8b9d@varnish-cache.org> Message-ID: <054.691cc6449c298ba3ebddd98fdf670ce4@varnish-cache.org> #1108: SIGBUS during Deflate ----------------------+----------------------------------------------------- Reporter: phobe77 | Type: defect Status: closed | Priority: normal Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Resolution: invalid | Keywords: ----------------------+----------------------------------------------------- Changes (by martin): * status: new => closed * resolution: => invalid Comment: Thanks for the update. I will close this bug. Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 20 16:47:37 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 20 Mar 2012 16:47:37 -0000 Subject: [Varnish] #1109: Gzip+ESI are broken for large included objects Message-ID: <044.d9ed1bba65805b3b22e3040f63c29ee9@varnish-cache.org> #1109: Gzip+ESI are broken for large included objects -----------------------------+---------------------------------------------- Reporter: nimnul | Type: defect Status: new | Priority: normal Milestone: Varnish 3.0 dev | Component: varnishd Version: 3.0.2 | Severity: normal Keywords: | -----------------------------+---------------------------------------------- I have the following ESI include file (/esi.js): {{{ }}} varnish config is: {{{ backend node { .host = "..."; .port = "..."; } sub vcl_recv { set req.backend = node; } sub vcl_fetch { set beresp.do_gzip = true; if (bereq.url == "/esi.js") { set beresp.do_esi = true; } } }}} Varnish is set to gzip foo.js and esi.js. It works as expected while foo.js is small, but starting from approx. 200kB Varnish sends broken gzip stream (Chrome and zcat either display damaged content or complain about end of file or invalid stream format errors). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 21 14:08:13 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 21 Mar 2012 14:08:13 -0000 Subject: [Varnish] #1110: HTTP/1.0 Simple-Response problem Message-ID: <041.e142752956cecd20575e30047e4b3c37@varnish-cache.org> #1110: HTTP/1.0 Simple-Response problem -------------------+-------------------------------------------------------- Reporter: lgx | Type: enhancement Status: new | Priority: low Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Keywords: | -------------------+-------------------------------------------------------- "The version of an HTTP message is indicated by an HTTP-Version field in the first line of the message. If the protocol version is not specified, the recipient must assume that the message is in the simple HTTP/0.9 format". -- http/1.1 "After receiving and interpreting a request message, a server responds in the form of an HTTP response message. Response = Simple-Response | Full-Response Simple-Response = [ Entity-Body ] " -- http/1.0 It seems that varnishd can't handle Simple-Response from backend properly. Instead italways response with a 503 error code to user. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 22 12:45:41 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 22 Mar 2012 12:45:41 -0000 Subject: [Varnish] #1111: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled Message-ID: <045.9e60476f5b500e4a6f02ea6ad7bb36a7@varnish-cache.org> #1111: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled ---------------------+------------------------------------------------------ Reporter: derjohn | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Hello, in our setup we have a varnish in front of several Tomcat7. When Tomcat7 delivers static content, it uses chunked tranfers. We'hit by a bug in that combination. The user gets the static content (e.g. jquery.js) and receives a 200 status, but the content sometimes (!) is not transferred completely. E.G. there jquery.js get truncated after some kilobytes. My observation was, that this happens mostly (only?) if the backend is reused. In the logs I see such error msgs, which correlate to the error: 19 Debug c Hit send timeout, wrote = 11680/21115; retrying 19 Debug c Write error, retval = -1, len = 9435, errno = Resource temporarily unavailable To test I use a simple script like that and look if the outputs is always the same or not: for i in $(seq 1 1000); do curl -s -x "" -k 'http://$HOST/...011_jquery-1.7.1.js' | md5sum ; done I tried varnish 3.0.2 and some newer trunks, the effect is still the same. The same setup runs with the same config with varnish2.1.5 fine. (I had to adapt the config parts of ESI enabling, as the syntax changed from 2.x to 3.x). rgds, derjohn -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 22 12:47:55 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 22 Mar 2012 12:47:55 -0000 Subject: [Varnish] #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled Message-ID: <045.a494717a9dcd83966ef7bb1fb1473262@varnish-cache.org> #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled ---------------------+------------------------------------------------------ Reporter: derjohn | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Hello, in our setup we have a varnish in front of several Tomcat7. When Tomcat7 delivers static content, it uses chunked tranfers. We'hit by a bug in that combination. The user gets the static content (e.g. jquery.js) and receives a 200 status, but the content sometimes (!) is not transferred completely. E.G. there jquery.js get truncated after some kilobytes. My observation was, that this happens mostly (only?) if the backend is reused. In the logs I see such error msgs, which correlate to the error: 19 Debug c Hit send timeout, wrote = 11680/21115; retrying 19 Debug c Write error, retval = -1, len = 9435, errno = Resource temporarily unavailable To test I use a simple script like that and look if the outputs is always the same or not: for i in $(seq 1 1000); do curl -s -x "" -k 'http://$HOST/...011_jquery-1.7.1.js' | md5sum ; done I tried varnish 3.0.2 and some newer trunks, the effect is still the same. The same setup runs with the same config with varnish2.1.5 fine. (I had to adapt the config parts of ESI enabling, as the syntax changed from 2.x to 3.x). rgds, derjohn -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 22 12:49:46 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 22 Mar 2012 12:49:46 -0000 Subject: [Varnish] #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled In-Reply-To: <045.a494717a9dcd83966ef7bb1fb1473262@varnish-cache.org> References: <045.a494717a9dcd83966ef7bb1fb1473262@varnish-cache.org> Message-ID: <054.a9afdf567b6d4036c2c6e5f6795a674b@varnish-cache.org> #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled ---------------------+------------------------------------------------------ Reporter: derjohn | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Comment(by derjohn): My Logfile is too large to attach it ... trac throws an 413 generated by ngnix :) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 23 09:12:20 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Mar 2012 09:12:20 -0000 Subject: [Varnish] #1111: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled In-Reply-To: <045.9e60476f5b500e4a6f02ea6ad7bb36a7@varnish-cache.org> References: <045.9e60476f5b500e4a6f02ea6ad7bb36a7@varnish-cache.org> Message-ID: <054.770cfe8177a9f534fb638664ed164e17@varnish-cache.org> #1111: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled ------------------------+--------------------------------------------------- Reporter: derjohn | Type: defect Status: closed | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Changes (by scoof): * status: new => closed * resolution: => duplicate -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 23 09:12:39 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Mar 2012 09:12:39 -0000 Subject: [Varnish] #1111: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled In-Reply-To: <045.9e60476f5b500e4a6f02ea6ad7bb36a7@varnish-cache.org> References: <045.9e60476f5b500e4a6f02ea6ad7bb36a7@varnish-cache.org> Message-ID: <054.83db6dcf7849d1c0c3c1d25723f11aee@varnish-cache.org> #1111: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled ------------------------+--------------------------------------------------- Reporter: derjohn | Type: defect Status: closed | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Comment(by scoof): See #1112 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 23 09:47:09 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Mar 2012 09:47:09 -0000 Subject: [Varnish] #1098: Return HTTP 416 for unsatisfiable byte-range requests In-Reply-To: <046.d36edf075ecb09f13af5a5bf04c34628@varnish-cache.org> References: <046.d36edf075ecb09f13af5a5bf04c34628@varnish-cache.org> Message-ID: <055.cefd9aec6630e37fd70103fcca7f4927@varnish-cache.org> #1098: Return HTTP 416 for unsatisfiable byte-range requests -----------------------+---------------------------------------------------- Reporter: jmeacham | Type: enhancement Status: closed | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by scoof): * status: new => closed * resolution: => fixed Comment: Added to https://www.varnish-cache.org/trac/wiki/Future_Feature. Please use the wiki for feature requests, trac is for bugs -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 23 14:45:43 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Mar 2012 14:45:43 -0000 Subject: [Varnish] #877: ESI Documentation In-Reply-To: <044.66e1f1a5ee7e8dbfa3877e0b2a30d519@varnish-cache.org> References: <044.66e1f1a5ee7e8dbfa3877e0b2a30d519@varnish-cache.org> Message-ID: <053.3cfa057a94a927741840ef15a87566aa@varnish-cache.org> #877: ESI Documentation ---------------------------+------------------------------------------------ Reporter: peroni | Owner: perbu Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: 2.0 Severity: normal | Resolution: invalid Keywords: | ---------------------------+------------------------------------------------ Changes (by kristian): * status: new => closed * resolution: => invalid Comment: This is sort of a non-issue in Varnish 3: It understands GZIP. (This ticket took a while to close.... it's been fixed for quite some time, though.) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 23 18:15:03 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Mar 2012 18:15:03 -0000 Subject: [Varnish] #1113: Backend HTTP status is used when hitting max_restarts after fetch Message-ID: <043.af89d41c041964c89ea3c31ccbdf8526@varnish-cache.org> #1113: Backend HTTP status is used when hitting max_restarts after fetch ----------------------+----------------------------------------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- When restarting in or after fetch and hitting max_restarts, it looks like we deliver the backend HTTP status to the client instead of 503 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Mar 25 16:36:10 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 25 Mar 2012 16:36:10 -0000 Subject: [Varnish] #1114: localtime () in inline c not behaving as expected Message-ID: <049.ee6933a5374165f0696cda162df76543@varnish-cache.org> #1114: localtime () in inline c not behaving as expected -------------------------+-------------------------------------------------- Reporter: cyberroadie | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Keywords: | -------------------------+-------------------------------------------------- Hi, I created a a small method to return some json with time information. I found that the localtime() method does not behave as expected, instead of returning the time set according to the timezone of the OS it sets it to UTC. Does varnish set itself to UTC overriding the the OS settings? See attached file for example -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Mar 25 19:52:37 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 25 Mar 2012 19:52:37 -0000 Subject: [Varnish] #1114: localtime () in inline c not behaving as expected In-Reply-To: <049.ee6933a5374165f0696cda162df76543@varnish-cache.org> References: <049.ee6933a5374165f0696cda162df76543@varnish-cache.org> Message-ID: <058.77ef0f0932b6c559ab10f534439c2636@varnish-cache.org> #1114: localtime () in inline c not behaving as expected --------------------------+------------------------------------------------- Reporter: cyberroadie | Type: defect Status: closed | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Resolution: invalid | Keywords: --------------------------+------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => invalid Comment: Yes, varnish runs in UTC timezone, in order to generate Date: headers etc. Its a particularly poignant example of the short-sightedness of POSIX that it assumes that a process will never need to know about more than one timezone. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Mar 25 23:09:22 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 25 Mar 2012 23:09:22 -0000 Subject: [Varnish] #1114: localtime () in inline c not behaving as expected In-Reply-To: <049.ee6933a5374165f0696cda162df76543@varnish-cache.org> References: <049.ee6933a5374165f0696cda162df76543@varnish-cache.org> Message-ID: <058.a6076abcc1c1cd871a09b8fd504850bb@varnish-cache.org> #1114: localtime () in inline c not behaving as expected --------------------------+------------------------------------------------- Reporter: cyberroadie | Type: defect Status: closed | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Resolution: invalid | Keywords: --------------------------+------------------------------------------------- Comment(by cyberroadie): Is it not possible to use with gmtime()/timegm() since the output UTC? Now there is the danger some inline C forces the timezone back to something else -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 05:56:07 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 05:56:07 -0000 Subject: [Varnish] #1115: varnishncsa spuriously logs incorrect request URLs Message-ID: <043.661333fba437e692c4e4ca33fc0a4b8a@varnish-cache.org> #1115: varnishncsa spuriously logs incorrect request URLs -------------------+-------------------------------------------------------- Reporter: lampe | Type: defect Status: new | Priority: normal Milestone: | Component: varnishncsa Version: 3.0.2 | Severity: minor Keywords: | -------------------+-------------------------------------------------------- The URL appears to contain remnants of previously logged URLs, e.g. a request for .js could be logged as .jspg (jpg), .jsss (css), .jsif (gif) Example: {{{ 0 RxURL c /css/img/icon_link.gif df_U :/css/img/icon_link.gifi: 0 RxURL c /js/efPageload.js df_U :/js/efPageload.jsvi: }}} {{{ varnishncsa.c: ... collect_client() ... case SLT_RxURL: ... qs = index(ptr, '?'); (void)VSL_H_Print(stderr, tag, 0, len, spec, ptr, 0); if (qs) { lp->df_U = trimline(ptr, qs); lp->df_q = trimline(qs, end); } else { lp->df_U = trimline(ptr, end); } fprintf(stderr, "df_U :%s:\n", lp->df_U); break; }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 10:05:15 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 10:05:15 -0000 Subject: [Varnish] #1113: Backend HTTP status is used when hitting max_restarts after fetch In-Reply-To: <043.af89d41c041964c89ea3c31ccbdf8526@varnish-cache.org> References: <043.af89d41c041964c89ea3c31ccbdf8526@varnish-cache.org> Message-ID: <052.e2c5fea70bd51029cb8a3e0cf7718832@varnish-cache.org> #1113: Backend HTTP status is used when hitting max_restarts after fetch ----------------------+----------------------------------------------------- Reporter: scoof | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 10:11:11 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 10:11:11 -0000 Subject: [Varnish] #1110: HTTP/1.0 Simple-Response problem In-Reply-To: <041.e142752956cecd20575e30047e4b3c37@varnish-cache.org> References: <041.e142752956cecd20575e30047e4b3c37@varnish-cache.org> Message-ID: <050.c7f8579338bd607ccebf8a6cf3b8c06f@varnish-cache.org> #1110: HTTP/1.0 Simple-Response problem -------------------------+-------------------------------------------------- Reporter: lgx | Type: enhancement Status: closed | Priority: low Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Resolution: worksforme | Keywords: -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: Correct, Varnish does not support really antique HTTP versions. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 10:13:09 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 10:13:09 -0000 Subject: [Varnish] #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled In-Reply-To: <045.a494717a9dcd83966ef7bb1fb1473262@varnish-cache.org> References: <045.a494717a9dcd83966ef7bb1fb1473262@varnish-cache.org> Message-ID: <054.fa1e7f24153ccd124225d44d2fb3b3f8@varnish-cache.org> #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled ---------------------+------------------------------------------------------ Reporter: derjohn | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Comment(by martin): Hi, Could you provide the complete client log when the error happens please? We don't need the full log (that would be too large yes), but the complete client transaction around where the single line you refer to, as well as the backend traffic log if this was a fetch would be most useful. Also please provide some details of your stack as such, e.g. which version of OSs and such. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 10:16:15 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 10:16:15 -0000 Subject: [Varnish] #1109: Gzip+ESI are broken for large included objects In-Reply-To: <044.d9ed1bba65805b3b22e3040f63c29ee9@varnish-cache.org> References: <044.d9ed1bba65805b3b22e3040f63c29ee9@varnish-cache.org> Message-ID: <053.ecd05a490ff89f0811446a8bef634b4e@varnish-cache.org> #1109: Gzip+ESI are broken for large included objects ----------------------+----------------------------------------------------- Reporter: nimnul | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.2 Severity: normal | Keywords: ----------------------+----------------------------------------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 10:16:29 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 10:16:29 -0000 Subject: [Varnish] #1115: varnishncsa spuriously logs incorrect request URLs In-Reply-To: <043.661333fba437e692c4e4ca33fc0a4b8a@varnish-cache.org> References: <043.661333fba437e692c4e4ca33fc0a4b8a@varnish-cache.org> Message-ID: <052.4db87dd36836016d4b521ac5f693602a@varnish-cache.org> #1115: varnishncsa spuriously logs incorrect request URLs -------------------------+-------------------------------------------------- Reporter: lampe | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: 3.0.2 Severity: minor | Keywords: -------------------------+-------------------------------------------------- Changes (by tfheen): * owner: => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 12:35:15 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 12:35:15 -0000 Subject: [Varnish] #1116: initscript varnishncsa for Debian i386 broken Message-ID: <044.9d7fa14e59a76e6c60ad3e08e4dc19e7@varnish-cache.org> #1116: initscript varnishncsa for Debian i386 broken --------------------+------------------------------------------------------- Reporter: klausb | Type: defect Status: new | Priority: normal Milestone: | Component: varnishncsa Version: 3.0.2 | Severity: normal Keywords: | --------------------+------------------------------------------------------- The init-script for varnishncsa out of the http://repo.varnish- cache.org/debian/dists/squeeze/varnish-3.0/binary-i386/varnish_3.0.2-1~1squeeze1_i386.deb is broken. The line {{{ DAEMON_OPTS="-a -w ${LOGFILE} -D -P $PIDFILE}" }}} needs to be changed into something like this: {{{ DAEMON_OPTS="-a -w ${LOGFILE} -D -P ${PIDFILE}" }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 13:01:29 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 13:01:29 -0000 Subject: [Varnish] #1116: initscript varnishncsa for Debian i386 broken In-Reply-To: <044.9d7fa14e59a76e6c60ad3e08e4dc19e7@varnish-cache.org> References: <044.9d7fa14e59a76e6c60ad3e08e4dc19e7@varnish-cache.org> Message-ID: <053.19768200b5413147cd9e5874f75c81a5@varnish-cache.org> #1116: initscript varnishncsa for Debian i386 broken ------------------------+--------------------------------------------------- Reporter: klausb | Type: defect Status: closed | Priority: normal Milestone: | Component: varnishncsa Version: 3.0.2 | Severity: normal Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Changes (by scoof): * status: new => closed * resolution: => duplicate Comment: See #1049 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 13:04:44 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 13:04:44 -0000 Subject: [Varnish] #1116: initscript varnishncsa for Debian i386 broken In-Reply-To: <044.9d7fa14e59a76e6c60ad3e08e4dc19e7@varnish-cache.org> References: <044.9d7fa14e59a76e6c60ad3e08e4dc19e7@varnish-cache.org> Message-ID: <053.2fec08afc32402e9f244d3e0e2ff5293@varnish-cache.org> #1116: initscript varnishncsa for Debian i386 broken ------------------------+--------------------------------------------------- Reporter: klausb | Type: defect Status: closed | Priority: normal Milestone: | Component: varnishncsa Version: 3.0.2 | Severity: normal Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Comment(by klausb): sry, didn't saw it in the search - my fault. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 26 14:17:15 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 26 Mar 2012 14:17:15 -0000 Subject: [Varnish] #1117: error - varnishncsa[473]: segfault at 0 ip 00007fd645a00022 Message-ID: <047.78536ce4e57383a6a091e8d8777b70f6@varnish-cache.org> #1117: error - varnishncsa[473]: segfault at 0 ip 00007fd645a00022 -----------------------+---------------------------------------------------- Reporter: webmaster | Type: defect Status: new | Priority: highest Milestone: | Component: varnishncsa Version: 3.0.0 | Severity: critical Keywords: | -----------------------+---------------------------------------------------- Hi All, the below pasted are the messages (/var/log/messages) i am getting in my server and everytime this message comes, the varnishncsa services gets stopped. I would appreciate if anybody could help us and let us know a solution for this. 12.so[7f40e8b5c000+175000] Mar 24 20:39:28 slonj360c kernel: varnishncsa[2298]: segfault at 0 ip 00007f4e8f762022 sp 00007fff49b88d58 error 4 in libc-2.12.so[7f4e8f6e2000+175000] Mar 25 03:46:47 slonj360c kernel: varnishncsa[29073]: segfault at 0 ip 00007f329746b022 sp 00007fff67ce9b18 error 4 in libc-2.12.so[7f32973eb000+175000] Mar 25 06:37:19 slonj360c kernel: varnishncsa[10802]: segfault at 0 ip 00007f63be1d1022 sp 00007fff5b286678 error 4 in libc-2.12.so[7f63be151000+175000] Mar 25 13:17:45 slonj360c kernel: varnishncsa[3473]: segfault at 0 ip 00007fe666026022 sp 00007fff09f51978 error 4 in libc-2.12.so[7fe665fa6000+175000] Mar 25 19:40:16 slonj360c kernel: varnishncsa[473]: segfault at 0 ip 00007fd645a00022 sp 00007fff578004a8 error 4 in libc-2.12.so[7fd645980000+175000] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 27 13:28:51 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 27 Mar 2012 13:28:51 -0000 Subject: [Varnish] #1118: Varnish docs should elaborate on ESI SRC a bite more Message-ID: <045.1c6a71deda4de08b9c60868f7e45de22@varnish-cache.org> #1118: Varnish docs should elaborate on ESI SRC a bite more ---------------------+------------------------------------------------------ Reporter: derjohn | Type: documentation Status: new | Priority: normal Milestone: | Component: documentation Version: 3.0.0 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Hello, I've been asked if there is a maximum size for the SRC URL of a esi:include. Our developers want to send parameters to the backend via "http get", thus appending ?foo=bar&......... to the ESI SRC. So I want to know if that gets truncated by varnish at some length. I know that the http server on the backend may truncate the request, too. rgds, derjohn -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 30 17:59:53 2012 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 30 Mar 2012 17:59:53 -0000 Subject: [Varnish] #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled In-Reply-To: <045.a494717a9dcd83966ef7bb1fb1473262@varnish-cache.org> References: <045.a494717a9dcd83966ef7bb1fb1473262@varnish-cache.org> Message-ID: <054.49037ffbbed7966fde5a30a47690d56f@varnish-cache.org> #1112: Varnish delivers truncated files when serving from Tomcat7 Backend and ESI enabled ---------------------+------------------------------------------------------ Reporter: derjohn | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 3.0.2 | Severity: normal Keywords: | ---------------------+------------------------------------------------------ Comment(by teominator): Hi, is there any new word on this? I have a similar problem and i'm wondering if you found some changed behavior in Tomcat 7 to cause this... Thanks, Teo -- Ticket URL: Varnish The Varnish HTTP Accelerator From michal.paal at digmia.com Wed Mar 14 09:04:56 2012 From: michal.paal at digmia.com (Michal Paal) Date: Wed, 14 Mar 2012 09:04:56 -0000 Subject: req.backend.healthy in VCL deliver is not always available and causes crash Message-ID: <64EE172A-8FF6-43A7-9617-763CACDB56ED@digmia.com> Hi, We have found a problem with req.backend.healthy information. in https://www.varnish-cache.org/docs/3.0/reference/vcl.html?highlight=req.backend.healthy#variables we can read "Although subroutines take no arguments, the necessary information is made available to the handler subroutines through global variables." We have used set resp.http.X-H = req.backend.healthy; in vcl_deliver, and it was working fine, but after the backend went sick, and varnish recieved next request, child will die leaving this message in /var/log/messages Mar 13 00:29:55 hostname-censored varnishd[9549]: Child (14754) Panic message: Assert error in VRT_r_req_backend_healthy(), cache_vrt_var.c line 539:#012 Condition((sp->director) != NULL) not true.#012thread = (cache-worker)#012ident = Linux,2.6.32-220.el6.x86_64,x86_64,-smalloc,-smalloc,-hcritbit,epoll#012Backtrace:#012 0x42c7a6: /usr/sbin/varnishd() [0x42c7a6]#012 0x4372d3: /usr/sbin/varnishd(VRT_r_req_backend_healthy+0xd3) [0x4372d3]#012 0x7fec62bf522d: ./vcl.RWdxVutw.so(+0x222d) [0x7fec62bf522d]#012 0x4331d6: /usr/sbin/varnishd(VCL_deliver_method+0x46) [0x4331d6]#012 0x4169f3: /usr/sbin/varnishd() [0x4169f3]#012 0x417a6e: /usr/sbin/varnishd(CNT_Session+0x9ae) [0x417a6e]#012 0x42efb8: /usr/sbin/varnishd() [0x42efb8]#012 0x42e19b: /usr/sbin/varnishd() [0x42e19b]#012 0x7fec6c9677f1: /lib64/libpthread.so.0(+0x77f1) [0x7fec6c9677f1]#012 0x7fec6c6a492d: /lib64/libc.so.6(clone+0x6d) [0x7fec6c6a492d]#012sp = 0x7fe9e5dbd008 {#012 fd = 52, id = 52, xid = 341045106,#012 client = 209.85.238.178 47081,#012 step = STP_PREPRESP,#012 handling = deliver,#012 restarts = 0, esi_level = 0#012 flags = #012 bodystatus = 4#012 ws = 0x7fe9e5dbd080 { #012 id = "sess",#012 {s,f,r,e} = {0x7fe9e5dbdc90,+448,(nil),+65536},#012 },#012 http[req] = {#012 ws = 0x7fe9e5dbd080[sess]#012 "GET",#012 "/xml/somexml.xml",#012 "HTTP/1.1",#012 "Connection: Keep-alive",#012 "Accept: */*",#012 "User-Agent: Feedfetcher-Google; (+http://www.google.com/feedfetcher.html; 114 subscribers; feed-id=5174819811214747333)",#012 "If-Modified-Since: Mon, 12 Mar 2012 22:30:53 GMT",#012 "X-Forwarded-For: 209.85.238.178",#012 "host: www.somepage.tld",#012 "Accept-Encoding: gzip",#012 },#012 worker = 0x7febbe0fea80 {#012 ws = 0x7febbe0fecc0 { #012 id = "wrk",#012 {s,f,r,e} = {0x7febbe0eca30,+168,(nil),+65536},#012 },#012 http[resp] = {#012 ws = 0x7febbe0fecc0[wrk]#012 "HTTP/1.1",#012 "Service Unavailable",#012 "Server: Varnish",#012 "Content-Type: tex I assume this wil be bug, what do you think? Thanks, Michal Paal http://www.digmia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5023 bytes Desc: not available URL: