Grey Cloud wrote:[How come posts look ok in preview but when posted are full of carriage returns?]
redeye wrote:I've come acroos a problem where, if you haven't logged in and you try to post a comment, it will prompt you to go through the login process - then, once you have finished the post and hit submit or preview, it will ask you to login again and then return you to a blank screen, meaning you have lost what you had typed.
It's not a problem if you ensure you are logged in before attempting to post.
arc-us wrote:Is it just occurring locally at my end or is anyone else experience between 30-35 seconds server response time when submitting (or previewing) posts? Extremely annoying so I'd like to know if it's just here or elsewhere as well. Thanks.
Osmosis wrote:I see the "this account has exceeded cpu blah blah blah" popped up again a few minutes ago.
This Account Has Exceeded Its CPU Quota
Please contact this site's webmaster.
Wait a few minutes and use your browser's "Back" button or click here to try again.
If you are the webmaster, your account may have gotten this error for one or more of the following reasons:
* Your account has used more than its share of the cpu in the past 60 second sliding window.
* Your account has too many concurrent processes running simultanously.
* Your account has consumed too much memory.
* Your site was recently very busy trying to run inefficient scripts.
The solution would be to optimize your applications to use less CPU.
Adding appropriate indeces to your SQL tables can often help reduce CPU.
Using static .html documents instead of painful .php scripts will practically eliminate CPU usage.
http://host22.hostmonster.com/highload. ... CKRCCNYDO9
Me, privately wrote:... But I think the 'problem' simply 'looks' worse than it is, BECAUSE they actually tell you what's going on. Long before even the first host move, from time to time when trying to access the Thunderbolts site or the forum, I would get the "Internet explorer cannot display this web page" message, and similar if I tried it with Firefox. I would try just a few seconds or a minute or two later, and the site would be 'up' again. I took this to be a glitch 'somewhere between here and there'.
This seems to be the 'problem' with this host, though they redirect to a specific error message instead of the generic "cannot display this webpage" one which most hosts leave you with.
Now I'm not saying this is the complete problem, and that the hosts are not being stingy, but from what I've been told (and I've spoken directly with their tech people) their system is no different to anyone else's essentially, except they tell you WHY you can't get on, and that it will only be a short time before you can.
The other factor affecting all of this is that the forum runs on "PHP", and php whilst in can be very 'dynamic' and helpful if you're doing something where lots of information needs to be stored/available at the drop of a hat (like a busy forum), it IS by it's nature CPU intense. As the forum grows in size, it uses more CPU to 'do' anything. ALL hosts put a limit on CPU usage on shared servers, but most don't actually tell you when you've exceeded the quota. You simply get a generic message and the next time you try it's working again, so you don't realize it's a CPU issue in the first place.
I really don't think we're under any specific kind of attack, though it is possible.
The thing the host recommends with ALL php scripts is 'optimizing' them, but from what I've been able to ascertain so far this is a complicated process which requires a reasonable programming knowledge. I'm hunting through the php-support pages at the moment in my 'spare' time to see if I can pick up any hints, but so far I haven't found much which will help us specifically. We need to find someone who's a wizz with php programming to really overcome this problem, and then we have to trust them enough to let them have a go at fixing it - a pretty tall order it seems.
So, to recap, we're seeing a message which other hosts fail to show us under the exact same circumstances. PHP programs are CPU intensive by their nature, and should be 'optimized' if we knew how to do it. As the forum grows, this will become more of an issue.
I will have another talk with the host's support people about the problem and see if I can be directed to someone helpful somewhere. All in all this host has been far superior than others, in that you can actually talk to real people about problems and get pretty good advice. Now at least we know what the problem is, instead of flying blind as with previous hosts.
I hope this helps you understand the nature of the problem and that it 'appears' worse than it is, only because the host actually tells you what's going on. But I will look into it further and see if there's anything we can do to help it happen less frequently. ...
Users browsing this forum: No registered users and 1 guest