Closed (fixed)
Project:
Cache Router
Version:
5.x-1.0-beta9
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2009 at 17:42 UTC
Updated:
3 Sep 2009 at 12:36 UTC
Using the 5.x-1.0-beta9 version of the module, I applied the 5.10 serialization patch as required by the module. (I was going to begin by using the file caching method). Before the patch was applied, I could see cache files being ccreated. However, once the patch was applied, I received a WSOD and the following errors:
Notice: Undefined index: cache in sites/all/modules/cacherouter/engines/file.php on line 15
Notice: Array to string conversion in includes/bootstrap.inc on line 434
Warning: require_once(1) [function.require-once]: failed to open stream: No such file or directory in includes/bootstrap.inc on line 970
Fatal error: require_once() [function.require]: Failed opening required '1' (include_path='.:') in includes/bootstrap.inc on line 970
Any ideas? Is there another patch that should be rolled against the latest Drupal core update? Any help would be greatly appreciated.
Comments
Comment #1
torgospizzaFYI I am using this with the latest build of Drupal, 5.15.
Comment #2
joshk commentedIt looks like you've got something mis-configured in teh $conf array in settings.php actually. Line 970 in bootstrap is where it loads the caching engine, and that's where the fatal error is coming from. Doublecheck your settings.php $conf overrides.
Also, clear your cache. Once you apply the patch, if there data in there that was set pre-patch, Drupal won't be able to figure it out. That shouldn't be the issue here, but it's something to be aware of when applying that serialization patch.
Comment #3
slantview commentedClear your cache_ files in your cache directory and see if that helps. This is a pretty common error in the memcache module, not as common with cache router. Typically you want to apply the serialization patch and THEN turn on cache router.
Can you include a copy of your configuration too.
Let me know if that works.
Thanks,
Steve
Comment #4
asb commentedHi,
similar problem here; the serialization patch applied cleanly on five D5 sites with separate codebase; three are running fine with "Cache Router", two are completely dead. Error message:
In bootstrap.inc, I can't find any references to /usr/share/pear, but I'm using the PEAR Wiki filter on all five sites. I have no idea why this is working three times and failing twice; the sites are configured pretty similar. In my cache directory there are no cache_ files.
Reverting the patch brought reliably back both broken sites.
Then disabled and uninstalled "Cache Router" module, Re-applied serialization patch again, reloaded the site; several of the usual warnings (those warnings appeared on all sites for a short period), but site's still working:
Disabled all caching at /admin/settings/performance, enabled "Cache router" module - site's still working. Re-enabled Drupal core's caching features. This procedure could be reproduced on the broken site.
Lessons learned from this:
* "Typically you want to apply the serialization patch and THEN turn on cache router." - this sems to be of the essence! (please consider adding it to the installation instructions)
* Cache Router and the serialization patch feels a bit fragile.
* I'm desperately missing an administrative page, or at least some reminder that the serialization patch has been applied and the "Cache Router" module is active; maybe /admin/logs/status wouldbe an appropriate place for this? Btw: the vanished statistics page looked pretty cool ;-)
* The Drupal community is great ;-) I wouldn't have solved this in a couple of minutes without this issue and slantview's essential hints.
Thanks a lot & greetings, -asb
PS: Also, I'm missing advice on how to use the different caches in a sensible manner, or how they should/shouldn't be combined. Currently, I'm running my sites with Drupal core's caching features under Lighttpd, that one is running PHP as FastCGI with APC (yes, that does work. Currently I'm evaluating a combined caching strategy with Memcached, but I haven't found out if this even affects Drupal's performance. Also, what about a third layer of caching ("Boost" module). I'd love to hear from user experiences about these scenarios!
Comment #5
slantview commented