These are chat archives for collectiveaccess/support

26th
Apr 2016
kaiall
@kaiall
Apr 26 2016 18:15
So, I finally got the cache completely cleared out. In all, it was nearly 100 GB! It may be a wise move to add something to installation directions that includes adding the cron job to clear those out regularly. (And no, Providence's cache doesn't grow nearly as quickly, but it clearly needed some weeding too.) Thanks for your help in getting this resolved!
Stefan
@stefankeidel
Apr 26 2016 19:30
Hmm, the Providence cache should actually be okay. There's a garbage collection process that runs every __CA_CACHE_TTL__ seconds (the next time a page is accessed) that loops through all the cache items and kills the expired ones
By default that runs once per hour
Stefan
@stefankeidel
Apr 26 2016 19:37
Actually, just found a setup where the Providence cache got fairly large and is not being cleared either. Let's see what's going on ...
Stefan
@stefankeidel
Apr 26 2016 20:04
Ah, I think I found the problem. Expired sessions could hang around in some cases. Argh. We'll have a fix in v1.6.2
kaiall
@kaiall
Apr 26 2016 20:47
Awesome. Glad this problem of mine will help eliminate some headaches for others!