Client loosing access to backend

Hi,
I built my first modx website for a client a few months ago. Everything went smoothly and he was very happy with it. However, ever month or so since the completion of the website I recieve and email from him saying: "The website is broken, I cant update anything." I then have to delete the cache manually before it works again.

Have I dont something wrong with regards to setup of modx?
Please find the error he receives attached.

Many thanks
Alex
- RocketPod LLP

These intermittent caching errors come up from time to time, but don't seem to be consistent enough to be able to figure out what the problem is. I know this is little help, but it at least it lets you know that it isn't anything you've done wrong. Some people have created cron jobs on their server to delete the cache files at various intervals.

Is there any chance this site is hosted on Rackspace Cloud Sites? This seems to be a problematic platform that is currently incompatible with MODX due to the file locking and RCSs unique NFS architecture. If not, there could be permissions issues or some other server issue that could cause file corruption.

Thanks for your reply Susan. What should the permissions be of the cache folder be? I feel this might have something todo with it.

Thanks in advance.
Alex

Depends on your server configuration it should be 755 or 777. If its permissions were wrong, you'd have bigger problems.

What kind of server configuration are you hosted on? Some kind of cloud hosting?

Thanks Jay and Susan. It's set at 777 at the moment. It's on our VPS with Ubuntu. What sort of information do you need?

Kind regards,
Alex

Ah. No, I was just wondering, as sometimes a poorly configured cloud hosting can mess up things like caches (cough ... rackspace ... cough)

Next time it chokes, take a look at all the files and their permissions. Or files may have become corrupted for some reason.

Okay, will do.
Thanks for your help

Alex

Hi again, It's been a week since the last time it happened. I checked the logs and found this:

[Tue May 07 16:08:33 2013] [error] [client 158.125.130.176] Cache unable to open file for writing: /srv/www/v36a.com/public/core/cache/rss//db08533834b22a850d2a76c183fa8c9e, referer: http://www.v36a.com/manager/

I have no idea what that means and if its why my client is losing access to the site.
Any advice would be greatly appreciated.

Thanks

Quote from: ricemast at May 07, 2013, 05:17 AM

Hi again, It's been a week since the last time it happened. I checked the logs and found this:

[Tue May 07 16:08:33 2013] [error] [client 158.125.130.176] Cache unable to open file for writing: /srv/www/v36a.com/public/core/cache/rss//db08533834b22a850d2a76c183fa8c9e, referer: http://www.v36a.com/manager/

I have no idea what that means and if its why my client is losing access to the site.
Any advice would be greatly appreciated.

Thanks

Hi Ricemast,

I'm actually having the same issue. Did you figure out what the solution was? I'm getting the same error to the "cace/rss//db08533834b22a850d2a76c183fa8c9e" file as well!

Sar