MODX having a hard time on Rackspace Cloud Sites

Thanks Opengeek.

I tried the install/upgrade - http://modx.s3.amazonaws.com/releases/2.2.7/modx-2.2.7-dev-20121228.zip

Unfortunately I get a 500 server error on the setup procedure.

And after clearing cache and trying again several times I checked the PHP error log.

And I repeatedly get this error...

PHP Parse error: syntax error, unexpected '{' in /mnt/stor0-wc2-dfw1/xxxxxx/www.xxxxx.com/web/content/manager/core/config/config.inc.php on line 13

My config file is now different from before and reads...

11. $table_prefix = '{table_prefix}';
12. $database_dsn = '{database_dsn}';
13. $config_options = {config_options};
14. $driver_options = {driver_options};

For what its worth, I've had this happen before but only on either the config_options or driver_options variable. I just removed what is in the brackets/restored to previous version and re-ran setup.

Quote from: adskiremote at Dec 28, 2012, 11:57 AM

11. $table_prefix = '{table_prefix}';
12. $database_dsn = '{database_dsn}';
13. $config_options = {config_options};
14. $driver_options = {driver_options};

Thanks pyrographics it worked the second time around. I think it might be because I was already on 2.2.7-dev version.

@Opengeek - I'm receiving errors in the modx manager error log, here's some of the output...

[2012-12-28 13:35:34] (ERROR @ /manager/index.php) Could not cache system settings.
[2012-12-28 13:35:34] (ERROR @ /manager/connectors/lang.js.php) Could not cache system settings.
[2012-12-28 13:35:34] (ERROR @ /manager/connectors/layout/modx.config.js.php) Could not cache system settings.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/system/registry/register.php) Could not cache system settings.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/element/category.php) Could not cache system settings.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/element/category.php) Could not cache context settings for mgr.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/source/index.php) Error caching lexicon topic lexicon/en/core/default
[2012-12-28 13:35:39] (ERROR @ /manager/connectors/system/registry/register.php) Could not cache system settings.

And I am repeatedly receiving this error in my PHP error log...

PHP Warning: link() [<a href='function.link'>function.link</a>]: File exists in /mnt/stor0-wc2-dfw1/xxxxxx/www.xxxxxx.com/web/content/manager/core/xpdo/cache/xpdocachemanager.class.php on line 279

As the install failed the first time around I want to be 100% sure everything went through ok. Is there a file I could check which indicate this latest fix?

Many thanks.

Quote from: adskiremote at Dec 28, 2012, 01:49 PM

@Opengeek - I'm receiving errors in the modx manager error log, here's some of the output...

[2012-12-28 13:35:34] (ERROR @ /manager/index.php) Could not cache system settings.
[2012-12-28 13:35:34] (ERROR @ /manager/connectors/lang.js.php) Could not cache system settings.
[2012-12-28 13:35:34] (ERROR @ /manager/connectors/layout/modx.config.js.php) Could not cache system settings.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/system/registry/register.php) Could not cache system settings.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/element/category.php) Could not cache system settings.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/element/category.php) Could not cache context settings for mgr.
[2012-12-28 13:35:37] (ERROR @ /manager/connectors/source/index.php) Error caching lexicon topic lexicon/en/core/default
[2012-12-28 13:35:39] (ERROR @ /manager/connectors/system/registry/register.php) Could not cache system settings.

And I am repeatedly receiving this error in my PHP error log...

PHP Warning: link() [<a href="function.link">function.link</a>]: File exists in /mnt/stor0-wc2-dfw1/xxxxxx/www.xxxxxx.com/web/content/manager/core/xpdo/cache/xpdocachemanager.class.php on line 279

As the install failed the first time around I want to be 100% sure everything went through ok. Is there a file I could check which indicate this latest fix?

Many thanks.

Those errors in the MODX error.log just mean that a particular thread was unable to get a lock to write the file, and are not necessarily bad if multiple processes were competing to write the files. I'll check into the PHP Warning you are seeing in the link() call.

The errors indicate you have the latest version...

FWIW, I'm waiting on access to a test account Rackspace is providing me with so I can test this directly.

OK thanks opengeek.

If you are still waiting and haven't received a test account. Let me know. I've already got a fresh install with this fix on a test sub domain. And would be happy for you to test there.

Jason, I'm having this problem too. I'll be happy to give you access to my account if you want it. I posted details here:

https://forums.modx.com/thread/81448/weird-caching-problem-in-multi-domain-revo-install-in-rackspace-cloud-sites-environment

I have been provided access to a test account and I will update everyone when I know more.

Awesome, you rock! Thanks for being all over this.

OK, I just tried installing 2.2.7 on a test subdomain on top of a clean install of 2.2.6. Here are my notes:

• I can't get package management to work in the clean install of 2.2.6 - I get the same results described above, it just creates an empty package file. With flock turned off, it also creates an empty lock file, but still no package. So I haven't tested whether I'm getting the same problems that I have in production, as I didn't want to take the time to install Wayfinder by hand. I'm going to assume this means my test install is experiencing the issue.
• I also got a 500 error on running setup, right after action=welcome. I had previously put "xPDO::OPT_USE_FLOCK => false," in my $config_options array in config.inc.php when trying to get 2.2.6 package mgt to work. So I removed that line, and then was able to run setup (actually setup timed out, which sometimes happens, but the process seems to have completed).
• I put "xPDO::OPT_USE_FLOCK => false," back in my $config_options and I was able to install Wayfinder via package management! Yaaay, progress! I also installed bootstrap and made a couple of test pages with no problems - except that I can't edit a resource by clicking on it, I have to use the context menu, but that's probably a session cookie problem and I doubt it's related to this.
• At first I was getting caching errors in the MODX error log. They are mostly coming from connectors, which isn't what I was seeing in production under 2.2.6, where the errors mostly come from index.php. However, after clearing the cache and clicking around the site a few times I stopped getting errors almost completely, even after creating a new resource, clearing the cache, and clicking around again. I did get one error after editing a chunk, but then that went away as well.
• Most importantly, the site appears to work fine!
• Over the weekend, I plan to (after making a full backup of course) try deploying 2.2.7 in production and see if it fixes the problems I'm having on my multi-domain install. Fingers crossed...

Hmmm... well, I re-ran setup on my test subdomain to try to clear up the problem with editing resources. It worked - and now package management is working fine even with flock on. That actually kind of worries me - I'm no longer confident that I've actually reproduced the problem. Maybe the problem I was having with package management was a fluke - or maybe the problem is still there but it happens to be working at the moment. This problem has always been intermittent.