It looks like you have a plugin (or snippet) that's creating its own cached RSS feed file. The file can't be opened because there's a double slash before the /db part of it, which likely means that the plugin is adding an unnecessary slash between two parts of the file path or using an invalid path for one part or the other. Another possibility is that there's supposed to be something between the two slashes that's missing at certain times.
If this is what's causing the client to lose access (it may not be), there may be a configuration option for the plugin to fix this or the plugin may be using a Media Source with a bad path. As a last resort you could disable the plugin if that's the problem.
Of course, as Susan and Jay have suggested, it could just be a plain old corrupted cache. Some users have had to resort to a cron job that periodically deletes all files in the core/cache directory (or just the cache files causing the trouble if you can figure out which ones they are).
Quote from: BobRay at Oct 03, 2013, 11:01 PMOf course, as Susan and Jay have suggested, it could just be a plain old corrupted cache. Some users have had to resort to a cron job that periodically deletes all files in the core/cache directory (or just the cache files causing the trouble if you can figure out which ones they are).
Hi BobRay.
I only just saw your reply. I don't have my automatic-email-subscription-to-replies on (but I do now).
Here's the solution to my post if anyone is interested:
https://forums.modx.com/thread/87001/changes-to-the-manager-don-039-t-reflect-on-the-front-end---hack#dis-post-479426.
I do believe it was a corrupt file in the cache..but also maybe had something to do with sessions.
Sar
☆ Flag it! - Don't forget to "star" a reply if it's answered your question