We recently moved a site to our boa instance, and it is our first production D7 (baylyblog.com) site. I'm not entirely sure I understand how caching works in Barracuda 2.0.3. I thought those 4 different caches might not even be used anymore, based on something I read, but regardless, it seems that the 4 different (device-based) caches should all be purged at the same time. Testing on an iPhone and iPad and a computer, but the iPhone and iPad are both receiving outdated content.

We don't have any mobile-specific version of our site.

Is there some sort of setup in a module that I need to do to get it working properly?

The Purge settings proxy URL is set to its default:
http://127.0.0.1:8888/purge-normal?purge_method=get http://127.0.0.1:8888/purge-mobile-tablet?purge_method=get http://127.0.0.1:8888/purge-mobile-smart?purge_method=get http://127.0.0.1:8888/purge-mobile-other?purge_method=get

I don't know if this should work, but when I run "curl http://127.0.0.1:8888/purge-normal?purge_method=get" on the server I get a 404 not found.

Here are my log files:
barracuda_log.txt
install.log
barracuda.cnf

Anything else I can provide, I'm happy to do so. Also, any suggestions for even a temporary manual fix would be greatly appreciated. Running "Flush all caches" doesn't do anything. Running cron doesn't help.

Thanks,
-Joseph

Comments

jtbayly’s picture

By the way, we aren't using Boost, since the documentation for 2.0.3 said we didn't need it anymore. Would turning it on possibly fix this problem?

Thanks,
-Joseph

P.S. I'm really tempted to set this to high priority...

omega8cc’s picture

Title: Purge not working completely: iPhone & iPad not receiving latest content » iPhone & iPad not receiving latest content - stalled redis cache?

It's not related to Speed Booster cache, since Speed Booster cache expires after 10 seconds, by default.

I suspect it is related to stale entries in the Redis cache. Please try to run twice:

service redis-server stop
sleep 3
killall -9 redis-server
rm -f /var/lib/redis/*

And see if that helps.

omega8cc’s picture

Title: iPhone & iPad not receiving latest content - stalled redis cache? » Do not use device specific keys for Redis cache entries

We shouldn't use this in Redis cache because Drupal knows nothing about those extra prefixes (so duplicate cache entries per device) and may fail to delete those cache entries.

omega8cc’s picture

Status: Active » Fixed
jtbayly’s picture

With all the help I've been given here, a decent bug report is the least I can do, even if sometimes I'm wrong.

I ran the commands you suggest, and in fact, that seems to have fixed my problem without the 2 commits you linked to.

Thanks again,
-Joseph

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

kevinquillen’s picture

Can I just disable redis caching entirely? It is messing up the mobile device experience on a website I built. I can't find the files above on the server to patch them.

mrP’s picture

I'd been stuck on an issue with themekey for 2 days now and the two fixes in #4 fit the bill.

You're my heroes.

omega8cc’s picture

@kevinquillen - yes, it is explained in the docs linked in your welcome e-mail sent by Octopus - please check the last hint at the bottom of this page: http://omega8.cc/speed-booster-cache-boost-and-advagg-108