hey
getting some unrecognizable output, randomly & occasionally, when viewing nodes (cache_page).
it seems to be Gzip content, with improperly set headers or content type.
this could be a problem in cache backport or on the memcache module
Cache Backport 1.0-alpha3
Memcache API 1.0-beta3
CSS Gzip 1.3
JavaScript Aggregator 1.5
Drupal Cache, Block Cache, Page Compression, CSS & Javascript aggregation and compression/minify.
this kind of issues never happened before, even with other modules like Memcache 6.x and Cache Router 6.x. it also does not happen when using APC 7.x on Cache Backport.
sample output:
HTTP/1.1 200 OK Date: Sat, 19 Mar 2011 23:12:55 GMT Server: Apache/2.2.9 (Debian) DAV/2 SVN/1.5.1 PHP/5.2.6-1+lenny9 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g X-Powered-By: PHP/5.2.6-1+lenny9 Expires: Sun, 19 Nov 1978 05:00:00 GMT Cache-Control: store, no-cache, must-revalidate, post-check=0, pre-check=0 Last-Modified: Sat, 19 Mar 2011 23:12:55 GMT Vary: User-Agent,Accept-Encoding Content-Encoding: gzip Content-Length: 2623 Keep-Alive: timeout=15, max=1 Connection: Keep-Alive Content-Type: text/html; charset=utf-8 ‹½ÛrÛ¸õÝ_ “Ù¤c^$Y²äHÚIìì$m’ugÓLÆ’ ›·‚ e5õõú¶_ÖsR"%Yvíízl‰Ä¹âà\áñ““ŸÏ~=}M"•Ääôó«wo µçKïØqNÎNÈßßœ½G:¶K>))|å8¯?Ð=Bh¤T~ä8óùÜž÷ìLΜ³Î5òé aõhšÊT@§{c-æ:‰Ób²…Ag4:ŠHG1KgÊSJVO+ Ü€gpM¸bÙYü¥¸šÐã,U|ƱH/‰äñ„Q&•_*"€”’HòpBB(^8,Žñ‘ÎbîxL*qyžd²+$±áƒÂ'T$lÆk˰B9…ZÄÜ@ÐùEñÃôO>°±¼8ó/Já‚|³yÌG$ÍRþ‚ÜŒM®·„‚'E,bä_$àIfì@–9‹í‹ÙõÂJ¹šgòiì$Õ{5 Ö*ÐjïȾˆ8W”$<lBaËkF¸K” `‚\ñïÜs}wØëô¹ŽüÞÁap8 <×;=wÄl-~y÷Õ+—"UÓl伿ï‡>tÝÞ(u]ßízKÍÀfO,ë«I¬8yûš¿M›'¹RwêeÁâ»Ç#ð…L•2~v×)|)r¥µŠ²+.{v¤üç/–>~ò•§¿Y–ÖÆà7…_°+fV))¤ÿ¿šäÏûnýnßùÝî(dƒï Ãþa×·/ŠD¤ðI§ãJgté]ÊLç8 8lâøäåÙ˯Ž3ÅŽ‹¿•\.l €Í=;1*B\*°O±þO=VðS¦"zD¨C÷ Å/“°`íÒŸŽ¯ô׬”D2$†·ý ú¬ 1ˆÕ£†œó/?ÁA¥³_2¥QÌY «+X³m»‰Œh€Âƒ¥À7ùí?šYœÚâÇú7ÇÉô¸(Y¢Þ »þ"ãa×}JÍÚ.f‘Z.jSûR›pÝ-ó,“ ˜XƒM–é£O§çºý¡;êöÉ ¹yþb¯ ƒoß *VñãTSñá| ̦™²B`¨¬\–àkœÍf<°DªßX‘Hh¥Y€·0 Aö…übÅ<Ü4°¤ÞN¸""€Rb¹ÔkÕj%+)—çA&¤úZRcz±tˆ-QÚ\fRMë?KN°±lkÌêÔµ¥Lè›,áU=ˆðq“ñX$³VöÛ™tQ®§3JX¬jöΆ"k/P¼¹t×þ´¥R–p}ˆeéVYRG6ñVŠûXéî΀m±¤uÖWwh¼a“€êe‹CÕŽsHíÓÑòqE»´k>jÍ%Ëóû{ñR¯Õᬅ¶\÷ ¢ñ’Ð4k%«³$Ô‹dª;Dï,׫lRXÞý DmªuÛ(Eé]p?@õš1Ìôp|ÝmÛ¢«ÍºCn†qר OK8‘XÔ°‘„BŠ`)ØÒ¡Òø—x¹Œó¬Pº×؉&º2žn¸Åú ×_[ììÞeçîcgì8„±x´C(„ùxd`?ÌÜŽéè„ò}‚>Ì æö§ÝŸ)\Ÿçʪúùì'œ``Š20Zœj³iƒi-BE§MípÝ‚ô’ h«••å<PdPT„x4l3ÇènæÓwÙŒ@a*1Ý’ŸþöäŽVS"‘æe³WÝÙuÌÓ™Š&´ÛïS‚ÉnB ëóëJBË+þ D%W,.á‘¶vi$anol¬k0¶F+7®&\#ĆDéÐé—ˆÁÉŠœ¥-ŽÇ[ ½UéÏ"ж¨Z ¶éôÏÐ\õô¾f¸µÕµm—¶íï°-Y)çÜÛ&9@vÚèô>¡VÿW›ä•ÚZt[Uˆ¾5›5,sO‹4EB:I„Zù{C\ ªìmbjMH㬱Dà•‹a‹¨ç^)b%#AS»Þ(ðº»þaÈÃa‡Ì=ðCÞ÷üÐ;Xʾ'ö}Ô¨Ð[lä'%—p®çàÞU J®J™žÃP²ž(*… JHãwdž#V„¹ÆgŠß–™¶Ã£¯[±ÐÊ^£€VÙK_vè:Ú,¡O»ýnokmÔÑ/cEä´^‹+FÇ,õ!¦‹ºfµ ²qÍû©¾½ì£Î*€ªHüþ–")Ÿ“H®#Ü‚Æ-¶±KØÄت\>cÝh™ÜÑBlíAÛ|³•lwÃõ©F÷"F&_– ô:ß\_µäSìÅWµÂ|ÖL7¹oöf¨„˜YKc걯š½L¿ ûõµÕtÌ+ôI6H.EÂä‚¶Ü ;‘+ÑØD£'¡khÓ_Ÿ·Ý²Aˆ¡áBˆ]ñ˜NOðkíp÷nmýÛ–Úþ³n6k›ùhz@>\îa54WöÆ“ym5”Ëßõ9c%wœO#q!ÆNÞžZöÈæô©ic_õcüL0þ¹¾|¾¥¹6Ð?vŽY9ʆ÷fÝoÜ”ãºÅ“\-–Y]ÒÜQ–ç˜>‘ÀÖ–¦þ³[ùi–¶×§&õ’ôqÍþÚ®êèÙ¦î†< Å=|°³L=b¤6äЛͰ±Þu´æŠÅ¢ÀÒ³Ý ð÷tÄÇœaÝ@˜ÎZ0îêò)…ïäÙœCÿ¾Urkè^wú˦S$Þ‚˜{ï}.‰)À|^‡ž3…<”à£1ÁÒ×ÅcŽ—ž:cGú®Óô±ŽßÃýn¹6Ô·q–/±?+v8Çû,ÀÑ.Øar'—&ŒêNN_éo½crH´¼}M›˜¥ÆX}I’¥…M^1ÿ2Ϥ2 ua—,‚Á:Ù~#ô;žÍÉ_YDÎp å´õÁ÷àÿ ˆ
Comments
Comment #1
lpalgarvio commentedseems to occur only on Anonymous sessions.
using Google Chrome for anonymous; Firefox for logged in sessions.
testing a bit more...
Comment #2
lpalgarvio commentedsame output with firefox and chrome.
only occurs in some anonymous sessions/hits, randomly.
firefox additionaly exibits odd behavior, taking longer to load the page.
response headers:
a correct page returns these headers:
note the Transfer-Encoding: chunked tag.
with Page Compression turned off in performance, this issue won't happen.
by looking at the code, this likely isn't a problem with Cache Backport.
Memcache does change headers though - line 108 in memcache.inc:
Comment #3
lpalgarvio commentedmoving discussion here
http://drupal.org/node/1098934
Comment #4
lpalgarvio commentedafter all, it's a problem in Cache Backport, and not in Memcache, because the problem occurs in all cache backends.
remdinder, happens in all browsers, when navigating with a anonymous account, if Page Compression is on.
Comment #5
pounardSeems an odd bug. Can you tell me exactly what modules and Drupal versions you used to get this error? I'm going to try to reproduce it on my side.
Comment #6
pounardOh you did, sorry, I'm trying.
Comment #7
pounardCan you give me the configuration you used for cache backport ?
Comment #8
pounardI found a real bug, but I'm not sure this is the one that got you this error.
EDIT: I just pushed an 6.x-1.0-alpha4 release that should be available for download within the next minutes. Please upgrade and test again (even if I'm not sure this is related). I'm continuing my tests.
Comment #9
pounardI tested using the alpha4 fixed version (fixes a single bug with database backend).
I used the exact same modules as you (and not other contrib modules), same versions. I also added APC backend for
cache_menuandcachetables. I set memcache backend forcache_pageand activated the aggressive caching.I enabled CSS compression and JS compression using JSMin+, I cleared all caches, and set this as cache configuration:
I didn't experience your bug. I'm installing Chrome for testing.
EDIT: I didn't configure Memcache servers because I'm using Memcached on localhost. I tested it and aggresive cache page is fetched from it, so all good.
Comment #10
pounardI was unable to reproduce the bug, using FF 3.6.15, Chromium 10.x (freshly compiled) and Epiphany 2.30.6.
Comment #11
lpalgarvio commentedwill test with alpha4 and other performance modules turned off.
my client uses:
Firefox 3.6.15 and Chrome 10.0.648.151 under Windows 7 64-bit
i'm using a single server configuration, no cluster.
modules:
Comment #12
pounardI tried installing *a lot* of modules.
The full I18n suite, Global redirect, some others, didn't experience the bug at all.
I also have OG and some modules of mine for testing purposes.
I read more attentively your posts, and saw that some of your HTTP headers are not given by D6 per default, have you some kind of specific HTTPd configuration or a reverse proxy cache that would modify those?
EDIT: May be Varnish patches?
Comment #13
lpalgarvio commentednope.
standard LAMP stack, debian linux, drupal 6.20 without modifications like pressflow.
default .htaccess with the addition of a rewrite rule.
Comment #14
pounardOk, thanks, still trying to find out what's happening, but honestly I can't reproduce the bug, that's weird. Trying to check my own HTTP headers but I don't even have the same headers.
Comment #15
lpalgarvio commenteddisabled these modules:
autoload, dbtng, css gzip, devel, drupal queue, Javascript Aggregator, js alter, url alter
turned on cache backport, with File Cache and APC.
played around with these settings:
Caching mode: normal & off
Block cache: on & off
Page Compression: on & off
Optimize CSS files: on & off
Optimize JavaScript files: on & off
no issues yet.
Comment #16
pounardOk. As you said upper, Memcache stores headers, but normal cache mode also will, this is because page cache stores headers that modules could have modified and restores them when serving a cached page.
It seems quite a normal behavior, other backends will also do it.
It's possible that a time, a page has been stored with wrong headers. It could happen considering the modules you are using, some of them could mess up with. It could be the result of something being gzip twice, maybe.
Have you kept a Drupal instance where the bug still happens? If yes, flushing the memcache cache (restarting the memcached deamon is an efficient way to do it) may make the bug dissapear, if this happens it could be a memcache module problem (wrong storing, or maybe an outdated cache kept with wrong headers, don't know..).
Please tell me if you find anything.
Comment #17
lpalgarvio commentedthe problem returns with Devel module enabled (from that list i disabled), while having Page Compression on, and this option enabled in devel:
* Display page timer
issue goes away as soon as i disable Page Compression in Drupal or Display page timer on Devel.
does not occur with these options enabled in Devel:
* Collect query info
* Display memory usage
also no problems with all options in Devel disabled.
no issues with CSS Gzip, JavaScript Aggregator (both compress), URL Alter, JS Alter or Drupal Queue either.
this never happened to me before. not even with Cache Router, Memcache (D6), with other cache backends, standard caching or no caching at all, in various drupal installations, with Drupal 6.19/6.20 and Drupal 7.
i always empty cache tables, flush APC/Memcache and file caches between tests, manually, and also in the browsers. restarting daemons helps.
testing further.
Comment #18
pounardOk, thanks, I'll try with Devel module, but this is sunday night and I'm going to get some rest. Really thanks for the effort, I'll give you some feedback soon.
Comment #19
pounardIn
devel_shutdown_real()it seems that devel messes up with HTTP content, still looking.Comment #20
lpalgarvio commentedokay.
managed to isolate further the issue.
requirements:
* Drupal 6.20
* Cache Backport 6.x-1.0-alpha3/4
* a cache engine (APC 7.x-1.0-beta2, Memcache API 7.x-1.0-beta3, File Cache 7.x-1.0-alpha2, or supplied DB)
* Devel 6.x-1.23
* Page Compression enabled in Drupal
* Display page timer enabled in Devel
* Access devel information permission enabled for anonymous user
* Navigate site randomly with a anonymous session
//edit:
just noticed that with this config, Devel won't show anything on the footer for the anonymous session.
and the information won't update ever for the anonymous session. you need to clear the caches all the time.
Devel for Drupal 7 probably has this changed and fixed to accommodate the new cache.inc.
i use Access devel information permission enabled for anonymous user when testing performance.
it should only be used in development.
Comment #21
pounardI cannot see it bug. When I activate the page timer, Devel displays it at the very bottom of the page. I gave the see devel information to anymous users, timer don't show up anymore after logout. So, I restarted Memcached (to clear cache) then refresh the home as anonymous. Devel showed the timer again. I tried then a refresh to ensure to get back a cached page, when Drupal serves a cached page, Devel information is not shown. Devel information probably is sent after the page is being cached.
This where I got, but I still couldn't reproduce the bug.
Comment #22
lpalgarvio commentedmight be a problem in my end, will try testing on other sites.
it does not occur always though. probably happens at around 1/10 to 1/2 of the times.
Comment #23
pounardThanks, I'll try again a on fresh empty instance.
Currently I'm unable to reproduce it with Devel 1.23 and latest Cache Backport alpha4. My configuration pretty much is the same as you. I'm using Memcache for cache_page bin, APC for cache and cache_menu bins, and all the others goes to database backend (per default).
Can you give me your backend settings in your settings.php file?
Comment #24
lpalgarvio commentedhere it is
same results with $conf['cache_****'] = set for memcache, apc and file cache.
Comment #25
pounardDid you activated the Memcache module? If so, try disabling it. Try commenting out the
$conf['memcache_bins']which is redundant with cache backend configuration.Comment #26
lpalgarvio commentedsame behavior with just one backend enabled, like memcache, or apc.
coppied issue to Devel issue queue
http://drupal.org/node/1099434
Comment #27
pounardThanks, let's wait for their answer. I'll still do some testing later. Have a good sunday night!
Comment #28
lpalgarvio commented+1
Comment #29
pounardNever got an answer, and this seems to be non-related to cache backport itself. Feel free to reopen if you reproduce it.