Custom Query (260 matches)
Results (7 - 9 of 260)
|#177||worksforme||about the xcache admin error||moo||vyouzhi|
see here, when i login admin and clean var or php, the xcache give me the error
While trying to process the request: POST /xcache_admin/ HTTP/1.1 Host: www.xxxx.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; zh-CN; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: zh-cn,zh;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: gb2312,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://www.xxxx.com/xcache_admin/ Cookie: __utmz=49687349.1206196763.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __utma=49687349.1644187740.1207388624.1210079277.1210342459.10; AJSTAT_ok_times=9; PHPSESSID=04e083e7af5a4aa6047ae00974aca548 Content-Type: application/x-www-form-urlencoded Content-Length: 46 The following error was encountered: * Invalid Response The HTTP Response message received from the contacted server could not be understood or was otherwise malformed. Please contact the site operator. Your cache administrator may be able to provide you with more details about the exact nature of the problem if needed. Your cache administrator is xxxx.com.
|#94||fixed||Garbage collector disabled when xcache.cacher set to off||moo||void|
On 1.2 and i think also head revision,
the garbage collector doesn't work when xcache.cacher is set to off (got some segfault, and i was trying to isolate the cause).
But with xcache.cacher set to off, i got problems with the garbage collector countdown staying @ maximum level. and therefore var_cache is useless if we use expiration for semi dynamical datas.
|#81||--||vbulletin 3.6.4 / 3.6.5 rare fatal errors viewing threads w xcache 1.0.3||moo||vissa|
Vbulletin 3.6.4 (security patched) RHEL4 php 4.4.5 xcache 1.0.3 (compiled from source -- you are missing this version in your ticket dropdowns)
Overall xcache is running excellent. However, I have had sporadic reports of users getting the following error when clicking a thread after using "new posts." I have also seen reports of this at vbulletin.com.
Fatal error: Direct instantiation of vB_Postbit class prohibited. Use the vB_Postbit_Factory class. in /includes/class_postbit.php on line 239
Here is a link of other reports of this error at vbulletin.com http://www.vbulletin.com/forum/showthread.php?t=215068
I also noticed when upgrading from vb 3.5.3 to 3.6.5 on another forum that there were some problems during the upgrade that never happened before xcache. May be unrelated. I had to disable xcache for moodle on one site (I'll make another ticket for that).