Core Cache file locks and will not update

we tried making the changes posted on https://github.com/modxcms/revolution/commit/702b29e3e213410b3d41bfd856a87c4e7d1298aa
However we still experience the random blank pages.

Is anyone else still experiencing this? We're on rackspace cloud.
We've just upgraded entirely to 2.2.5 in hopes that it would now work, so far it's been a day and the error hasn't occurred.

You are spinning your wheels with Rackspace Cloud Sites. It is incompatible with MODX Revolution. We've had to move all our heavier use sites elsewhere. The use_flock change led to corrupted cache within a week without even updating any resources. From what I can tell, MODX uses more individual requests than Rackspace can handle. Here is what Rackspace told me:

When browsing your site I was seeing some slowness. When taking a further look at an strace I did see that it was accessing a lot of cache files as well as elements within .../core/model/modx/processors/element/tv/renders/web/output

When doing a count on the calls the site is making prior to rendering it does seem to stat, access and open a lot of resources:

791 lstat
822 read
837 mmap
883 close
909 open
1063 fstat
2516 access
3078 stat

Unfortunately we are not developers so trouble shooting code would not be something within our scope of support.

There are a number of major sites using Rackspace. For example, the showcase site for delldesignlibrary.com is on Rackspace Cloud. http://modx.com/why-modx/applications/versioning-enterprise-search/

See the comments on Mark Hamstra's site for a source https://www.markhamstra.com/modx-blog/2012/01/bringing-dropbox-to-media-sources/

Thanks for the feedback pyrographics guys, but your answers balanced out
pyrographics Have you tried upgrading to 2.2.5 on rackspace cloud?
And sottwell are you sure the dell design library is hosting on rackspace cloud? I find that hard to believe

To be clear, I am referring to Rackspace Cloud Sites not Rackspace Cloud Servers. We utilize both nearly exclusively, Cloud Servers operate very well and we have no problems with them. I imagine the sites to which Susan is referring run on Cloud Servers not Cloud Sites.

Most, if not all, of our Revolution sites on Rackspace Cloud Sites are upgraded to 2.2.5. We have about a half dozen of them there still. We have been troubleshooting the white screen of death problem/cache corruption since last spring and have not been able to find any sort of cause for it. We had hoped it was flock related but we set modx to not use flock on three of the sites after it was released and all three were corrupted within the week. They operate fine with flock enabled for the most part but they operate better elsewhere.

The more heavily trafficked sites would display 500 errors or white screens every so often. One site we launched last month tested out perfectly in development but as soon as we moved it to the live domain it went blank twice within a week. We moved that to a Rackspace Cloud Server and it has been working without issue since. The sites feel slower on Cloud Sites, long response times, slow manager operation. We moved a large local news site from Rackspace Cloud Sites to MODXCloud a week or two ago and it is 1000X better, the manager responds faster, no more blank pages. The client is very happy with the move so far.

Just my 2¢ worth, I spent countless hours pulling my hair out with it and wanted to share the experience.

We're having similar issues overall with rackspace cloud sites. Had a BIG client go down hard today with 500's everywhere. Our trick was to rename the cache directory, because we couldn't delete it fast enough before a visitor would hit the site and start re-filling it.

Pyro who do you use now?

Yea a rename of cache folder usually does the trick, but the question is how long can you keep doing that? and it happens randomly, we have pingdom setup to monitor and tell us when it goes down but so much work for something so simple...it should just work.

I've given up with rackspace cloud sites, i've been battling with it all year now, and don't know what else to say to clients.
I've decided today to move into a VPS environment and see how things go else I'll loose all my clients running on MODX.

I'm about there too. But I like the email and client setup for RSC ... uh.

I know I've been with them for a while now but at the end of the day, uptime is what matters, and at rackspace prices you can hire someone to setup email and clients for you lol

We primarily use a Rackspace Cloud Server with cPanel. It works well with MODX, server image is auto-backed up nightly and affords us access to their Cloud Files CDN, which is yet to be integrated with MODX media sources. Their new openstack cloud servers can be downloaded and spun up on other cloud providers.

We moved one of our large sites to MODX Cloud. It works great but has no mail support. Their plans are currently too rich for small business clients but are well worth it for large sites. I hope they release smaller spec/smaller price plans in the near future allowing us to move more clients there. Note we couldn't get MODX Cloud's Vapor packaging script to work on our site, it created a huge amount of data and ran out of memory before completing.

If I were starting fresh, I'd look at SoftLayer for my cloud. They are big MODX supporters. I would never go back to a stand-alone VPS because it is not as flexible.

Regarding mail on Cloud Sites, we're leaving it there while moving the sites. It is not an ideal solution but is least intrusive for our clients. Another big issue we have with Cloud Sites is there is no SSH access. Not a problem until you need to delete a massive directory or run a command line script.