5.4 on Rackspace Cloud
Permalink 3 users found helpful
I have a Concrete5 site running on a Rackspace Cloud Sites account. It was running okay on V5.3.3.1. Last night I upgraded to V5.4 and it was working last night, but this morning, with I guess the cloud working under load, the site keeps failing stating that there are no suitable nodes in the cloud to service the request.
So if you're hosting with Rackspace Cloud Sites then BEWARE!!
So if you're hosting with Rackspace Cloud Sites then BEWARE!!
Rackspace got back to me and the issue was caused by some LONG running query. And the error we were gettings meant that a script was timing out.
Hey, I'm hosting my site with RackSpace and it is coming up with
"This website is temporarily unavailable. Please check back later.
Unfortunately there were no suitable nodes available to serve this request."
How did you fix this??
Many Thanks
Mike Down
"This website is temporarily unavailable. Please check back later.
Unfortunately there were no suitable nodes available to serve this request."
How did you fix this??
Many Thanks
Mike Down
I haven't actually fixed it yet. I just rolled back to 5.3.3.1.
I do find that Concrete5 runs slower on the Rackspace Cloud Sites service, than it did on my cheap old shared host. Probably because MySQL isn't on the same box as the site.
I do find that Concrete5 runs slower on the Rackspace Cloud Sites service, than it did on my cheap old shared host. Probably because MySQL isn't on the same box as the site.
Oh, ok. Do you know where i can get hold of the 5.3.3.1 core files?? Yer i noticed that it seemed to take a while to load even the error page!
How does it run on 5.3.3.1?
How does it run on 5.3.3.1?
Actually...I just found it on the download page! Thanks for your help.
You can download those here:http://www.concrete5.org/developers/downloads/...
These two sites are running on Cloud Sites:
http://sales-clarity.com/
http://agreementexpress.com/
They run okay, though depending on the time of day the performance can suffer. With the improvements in 5.4 I was hoping to see some speed increases, but not so.
The error takes a while to pop up because PHP has a 30 second max execution time setup at Rackspace. So it takes 30 seconds before it times out and then throws the error.
If you find any fixes to these performance issues PLEASE let me know. My clients aren't complaining about their site performance right now, cause I only charge them a few bucks a month for hostings, though obviously I would like to see them loading much faster.
These two sites are running on Cloud Sites:
http://sales-clarity.com/
http://agreementexpress.com/
They run okay, though depending on the time of day the performance can suffer. With the improvements in 5.4 I was hoping to see some speed increases, but not so.
The error takes a while to pop up because PHP has a 30 second max execution time setup at Rackspace. So it takes 30 seconds before it times out and then throws the error.
If you find any fixes to these performance issues PLEASE let me know. My clients aren't complaining about their site performance right now, cause I only charge them a few bucks a month for hostings, though obviously I would like to see them loading much faster.
Could this be your problem? This was definitely the case with some of my clients' servers, though not on my shared server:
http://andrewembler.com/web/improving-the-performance-of-zend-cache...
Made a HUGE difference, and now their sites work great.
http://andrewembler.com/web/improving-the-performance-of-zend-cache...
Made a HUGE difference, and now their sites work great.
How can I tell if the Zend_Cache is enabled on my server?
phpinfo();
http://agreementexpress.com/martin-test-info.php
It doesn't look like it's enabled. Unless I'm reading this wrong.
It doesn't look like it's enabled. Unless I'm reading this wrong.
it /is/ required for 5.4
So I guess it's time to either bug Rackspace to install it, which probably isn't going to happen, or find a new host for my clients' sites.
You can try disabling the cache in the Dashboard and see if it makes a difference in your performance. If your server doesn't actually have it installed, this might improve performance.
However, it might fall under some other sort of add-on for PHP, like "Zend Optimizer", in which case you may consider trying Andrew's code in your config/site.php file anyway to see if it makes a difference.
However, it might fall under some other sort of add-on for PHP, like "Zend Optimizer", in which case you may consider trying Andrew's code in your config/site.php file anyway to see if it makes a difference.
Thanks elyon, I'll try that out. Rackspace said they don't support Zend_Cache, then again the support guys might not even know what I'm talking about.
I uploaded a fresh copy of Concrete5 V5.4 and it seems to be working. It definitely isn't super fast, but it is working. Here's a test URL to see what it's like:http://test.coastalextreme.com/...
Ok, after having a very bad weekend with a client's site, I stumbled upon this post. I am curious if, going forward, I am going to need to either a) not upgrade c5 to any version that makes use of the Zend Caching or b) move my clients to a different hosting environment that supports it. Is is possible to simply turn of caching with Zend to fix this issue? We really like Rackspace's cloud offerings and they have been rock solid so far, but we also really like Concrete 5. Please don't make us choose...
Don't upgrade C5. My one client running C5 on Cloud Sites is running 5.3 and I have two other sites that I'm leaving on my old shared hosting account until I find a better solution. In 5.4 you can't disable caching since it's totally built in so that's not an option. I've pondered the idea of starting up a Cloud Server, but I don't want the hassle of having to manage it. I like the managed aspects of Cloud Sites. Then again maybe I just need to nut up and give Cloud Servers a shot.
As Elyon posted earlier in the thread have you tried adding this to your config/site.php
Don't know if it will help but you can read more here...
http://andrewembler.com/web/improving-the-performance-of-zend-cache...
Don't know if it will help but you can read more here...
http://andrewembler.com/web/improving-the-performance-of-zend-cache...
Yes, I tried that and that did not solve the issue.
My test site has that setting enabled and it's still super slow even with an clean install:http://test.coastalextreme.com/...
Just a side note that google reveals problems with Drupal & Joomla on this hosting provider also..
Well that doesn't help.
It's a shame to have such a large reliance on a plugin to make Concrete5 fast. Wordpress is great on Cloud Sites and it's SUPER fast if you use the WPSuperCache plugin.
It's a shame to have such a large reliance on a plugin to make Concrete5 fast. Wordpress is great on Cloud Sites and it's SUPER fast if you use the WPSuperCache plugin.
Okay just want to clear up some details here as this is becoming a frequent issue and this thread shows up on google high....
1) The new use of Zend stuff in concrete5.4 is built into concrete5.4. There is nothing your server has to "support." If it supports PHP 5.2, it supports this stuff too, as it's just a bunch of libraries we actually include with concrete5.4. I'm not sure that's clear from some of the comments (including my own) to this thread, but just to be 100% clear there's nothing that any web host would have to turn on, install, or support beyond what should be in any basic php install.
2) We will continue to rely on Zend. Zend is written by the core group behind PHP, it's not going anywhere, it's updated frequently, you can go read from Andrew why we love Zend here:
http://andrewembler.com/concrete5/concrete5-and-the-zend-framework/...
3) concrete5.3.x didn't use as much of the Zend framework as concrete5.4.x does. Specifically Zend Translate and Zend Cache are both heavily relied on in concrete5.4 and not used at all in 5.3.x.
Because of point #3 it is my belief that sites hosted in Rackspace Cloud were just barely working with the resources the Cloud provides in 5.3 and when you upgrade to 5.4 the additional drain causes their system to start throwing up the dreaded "No suitable nodes are available to serve your request" errors. I don't know if it's because of all the Zend Translate disk I/O or the additional CPU requirements of Zend Cache, or what - but its pretty hard for us to debug it as the errors tend to be sporadic and since its "the cloud" you can't really follow the normal processes we would on a server where we can see where the holdup is happening.
It is /possible/ you might get better performance out of the next version of concrete5 if you have full page caching turned on, but I can't say thats a promise of any sort.
If you're sensing a certain amount of disdain for "the cloud," you're very perceptive. To be 100% clear I think the cloud is very very interesting when it comes to massive bulk storage, or the need to perform a repetitive CPU work (like SETI or converting a ka-jillion video files).. Okay that makes sense to me. Farm this work out to thousands of computers, great. Even if you're doing something like Basecamp, a simple web application that behaves the same for everyone that you need to scale quickly, perhaps.. yeah maybe with the right relationships and access I'd consider the cloud for that...
But for basic web hosting? What possible value do I get out of NOT having access to the hardware running my website? I mean it's not like Unix has a long history of being unable to serve websites perfectly fine. So cloud computing isn't fixing a broken problem when they get into the web hosting business, they're competing with me having access to a machine where I can see what MySQL is doing and run TOP when things go sour. Never have I ever ever ever heard of ANYONE saying "OMG I got concrete5 running on a cloud setup and its sooo much faster than my old VPS setup." At best, it is "hey I've made it work on mediatemple's cloud, mostly." Well woop-dee-doo - the bar was set pretty high there, no? The promise of infinite scalability seems pretty laughable when basic performance is a factor of 10 or even 100 lower. That's why I say, sure for something where performance at a unit level isn't important (converting a video file) I get the allure of being able to go from 10 a day to 10,000,000,000 a day without changing infrastructure. I just don't think that most of us actually have that problem and I think the money behind the marketing of cloud computing has convinced folks of the opposite.
What I find truly amazing is people pick an open source CMS, I'm assuming for some degree because of the transparency and access to "how it works," and then stick it in the cloud and get frustrated with the result. There are half a dozen "clouds" across large hosts, they're all built with proprietary solutions the parent companies are eager to protect and none of them give you the basic ability to tweak performance you can get out of WHM/cPanel. When you get these "No Nodes" messages you're told by Rackspace that it is the fault of your code. So basically it's a black box that would make even Orwell quiver and when it breaks, you're asked to stop breaking it.
I mean really. "Cloud" For real? The /weather/ is what pops into your mind as a strong metaphor when I say "what's a reliable technology platform?" ;) Forecast says scattered chance of data delivery today...
Host with us, or go get an account on some nicely provisioned LAMP server where the owners won't over sell your machines and are actually capable of telling you what's going on when something goes wrong. If you can make concrete5 work on the cloud more power to you, please share your tips and tricks here. With our small team and the limited amount of time in a day, we're going to continue forging ahead on the assumption you're sticking concrete5 in the most popular and healthiest web server environment known to man: a LAMP stack.
There's the philosophy that's prevalent around the office, if we're wrong I'm always happy to hear why - it happens. ;)
1) The new use of Zend stuff in concrete5.4 is built into concrete5.4. There is nothing your server has to "support." If it supports PHP 5.2, it supports this stuff too, as it's just a bunch of libraries we actually include with concrete5.4. I'm not sure that's clear from some of the comments (including my own) to this thread, but just to be 100% clear there's nothing that any web host would have to turn on, install, or support beyond what should be in any basic php install.
2) We will continue to rely on Zend. Zend is written by the core group behind PHP, it's not going anywhere, it's updated frequently, you can go read from Andrew why we love Zend here:
http://andrewembler.com/concrete5/concrete5-and-the-zend-framework/...
3) concrete5.3.x didn't use as much of the Zend framework as concrete5.4.x does. Specifically Zend Translate and Zend Cache are both heavily relied on in concrete5.4 and not used at all in 5.3.x.
Because of point #3 it is my belief that sites hosted in Rackspace Cloud were just barely working with the resources the Cloud provides in 5.3 and when you upgrade to 5.4 the additional drain causes their system to start throwing up the dreaded "No suitable nodes are available to serve your request" errors. I don't know if it's because of all the Zend Translate disk I/O or the additional CPU requirements of Zend Cache, or what - but its pretty hard for us to debug it as the errors tend to be sporadic and since its "the cloud" you can't really follow the normal processes we would on a server where we can see where the holdup is happening.
It is /possible/ you might get better performance out of the next version of concrete5 if you have full page caching turned on, but I can't say thats a promise of any sort.
If you're sensing a certain amount of disdain for "the cloud," you're very perceptive. To be 100% clear I think the cloud is very very interesting when it comes to massive bulk storage, or the need to perform a repetitive CPU work (like SETI or converting a ka-jillion video files).. Okay that makes sense to me. Farm this work out to thousands of computers, great. Even if you're doing something like Basecamp, a simple web application that behaves the same for everyone that you need to scale quickly, perhaps.. yeah maybe with the right relationships and access I'd consider the cloud for that...
But for basic web hosting? What possible value do I get out of NOT having access to the hardware running my website? I mean it's not like Unix has a long history of being unable to serve websites perfectly fine. So cloud computing isn't fixing a broken problem when they get into the web hosting business, they're competing with me having access to a machine where I can see what MySQL is doing and run TOP when things go sour. Never have I ever ever ever heard of ANYONE saying "OMG I got concrete5 running on a cloud setup and its sooo much faster than my old VPS setup." At best, it is "hey I've made it work on mediatemple's cloud, mostly." Well woop-dee-doo - the bar was set pretty high there, no? The promise of infinite scalability seems pretty laughable when basic performance is a factor of 10 or even 100 lower. That's why I say, sure for something where performance at a unit level isn't important (converting a video file) I get the allure of being able to go from 10 a day to 10,000,000,000 a day without changing infrastructure. I just don't think that most of us actually have that problem and I think the money behind the marketing of cloud computing has convinced folks of the opposite.
What I find truly amazing is people pick an open source CMS, I'm assuming for some degree because of the transparency and access to "how it works," and then stick it in the cloud and get frustrated with the result. There are half a dozen "clouds" across large hosts, they're all built with proprietary solutions the parent companies are eager to protect and none of them give you the basic ability to tweak performance you can get out of WHM/cPanel. When you get these "No Nodes" messages you're told by Rackspace that it is the fault of your code. So basically it's a black box that would make even Orwell quiver and when it breaks, you're asked to stop breaking it.
I mean really. "Cloud" For real? The /weather/ is what pops into your mind as a strong metaphor when I say "what's a reliable technology platform?" ;) Forecast says scattered chance of data delivery today...
Host with us, or go get an account on some nicely provisioned LAMP server where the owners won't over sell your machines and are actually capable of telling you what's going on when something goes wrong. If you can make concrete5 work on the cloud more power to you, please share your tips and tricks here. With our small team and the limited amount of time in a day, we're going to continue forging ahead on the assumption you're sticking concrete5 in the most popular and healthiest web server environment known to man: a LAMP stack.
There's the philosophy that's prevalent around the office, if we're wrong I'm always happy to hear why - it happens. ;)
