MODX having a hard time on Rackspace Cloud Sites

Tried this and it messed up the site and the admin manager too.

Error messages were same as before...

PHP Warning: file_put_contents() [<a href='function.file-put-contents'>function.file-put-contents</a>]: Exclusive locks are not supported for this stream in /manager/core/xpdo/cache/xpdocachemanager.class.php on line 275

I cleared the cache before trying, just in case you wondered.

Thanks.

Networked file systems don't like that. What FS does RSC use, anyway?

Quote from: sottwell at Dec 06, 2012, 12:34 AM

Networked file systems don't like that. What FS does RSC use, anyway?

Howdy all, this is Chris from the Rackspace Cloud Sites support team.

We do use NFS. Our operations team is actively looking into why Modx doesn't seem to play nicely with Cloud Sites (or vice versa, not trying to point fingers in any way). [ed. note: zerreissen last edited this post 13 years, 9 months ago.]

Quote from: zerreissen at Dec 06, 2012, 07:10 AM

Our operations team is actively looking into why Modx doesn't seem to play nicely with Cloud Sites (or vice versa, not trying to point fingers in any way).

This is excellent news. I'm about to go out of my mind watching over all of our sites. Having sites that just randomly don't render its navigation or main banner makes clients real upset and my life somewhat miserable. I'm on the verge of having to move one of our sites off of RSC altogether. I really don't know what else to do.

Here's hoping a solution is found... soon.

Me too - I've been complaining to Rackspace for 3 days. I'm installing ok - however cannot at packages - the file system has trouble recognizing folders. It's definitely the way php is running. I'm at a loss.

Quote from: SpaceCity at Dec 06, 2012, 08:23 AM

Quote from: zerreissen at Dec 06, 2012, 07:10 AM

Our operations team is actively looking into why Modx doesn't seem to play nicely with Cloud Sites (or vice versa, not trying to point fingers in any way).

This is excellent news. I'm about to go out of my mind watching over all of our sites. Having sites that just randomly don't render its navigation or main banner makes clients real upset and my life somewhat miserable. I'm on the verge of having to move one of our sites off of RSC altogether. I really don't know what else to do.

Here's hoping a solution is found... soon.

Me too - I've been complaining to Rackspace for 3 days. I'm installing ok - however cannot at packages - the file system has trouble recognizing folders. It's definitely the way php is running. I'm at a loss.

Quote from: SpaceCity at Dec 06, 2012, 08:23 AM

Quote from: zerreissen at Dec 06, 2012, 07:10 AM

Our operations team is actively looking into why Modx doesn't seem to play nicely with Cloud Sites (or vice versa, not trying to point fingers in any way).

This is excellent news. I'm about to go out of my mind watching over all of our sites. Having sites that just randomly don't render its navigation or main banner makes clients real upset and my life somewhat miserable. I'm on the verge of having to move one of our sites off of RSC altogether. I really don't know what else to do.

Here's hoping a solution is found... soon.

I've got all of these issues!

Quote from: himmdesign at Nov 13, 2012, 04:41 PM

We have been longtime MODx and Rackspace users. Been on MODx longer than RSC

So about the time we upgraded to 2.2.5 we started seeing some MAJOR issues, some in no particular order.

• Can't clear cache, or doesn't report that it cleared. http://grab.by/hve2
• Wayfinder is having fits, sometimes won't display a menu, then after clearing the cache manually it will work... for a while.
• Downloading packages / updates. They will just error out and then leave a 0 byte zip file in the packages dir.
• Manager error 500, until a manual cache clearing

Those are a few off the top of my head... anyone else on RSC having these issues? I spent most of today clearing caches and saying WTF? Rackspace of course points it at the application.

So I spoke with RS Support - they did confirm the issue has been escalated to their senior guys - of which Chris (who commented) on this thread is one of them.

I do believe the issue is specifically with directories made by php. Something is going on with ownership preventing php from being able to write to directories that it has created. I'm having some luck if I delete and recreate folders using my admin ftp user. very strange.

So, it would appear that even though the newer versions of Modx is giving the ability to disable flock, it appears that the application is still using flock. I still see errors "Exclusive locks are not supported for this stream" on a site that has had flock disabled using the new variables in the latest version (./core/xpdo/xpdo.class.php: const OPT_USE_FLOCK = 'false';
)

On a host such as GoDaddy, you probably won't see the file corruption because of their single node environment (we use a multi node environment).

Speaking of multi node, Modx looks to be using the process PID, which won't work reliably on our environment as the same PIDs can be re-used at the same time in our environment on the different nodes. A more reliable process might be to use the hostname/servername in conjuction with the PID.