Web4 *must* be sick!

BluJag

BluJag

Perch
I have a number of pretty standard Joomla sites on Web4. Until recently, they all used to run fine, but now it's almost impossible to connect to them without getting a Error 500: Internal Server Error. When they do connect, the sites are very very slow.

I've raised tickets numerous times and was eventually told that one of my sites (the first one I listed) was causing the problem with an errant script and was an "abuse". Thus, end of problem as far as the Helpdesk was concerned.

I don't accept this explanation because *all* my Joomla sites are affected, and I've taken the so-called "abusing" site off-line, yet still the errors keep on happening. Furthermore, they are just standard Joomla sites, nothing fancy, and are from versions 1.5.23 through to 1.7

So, I believe Web4 must be pretty sick and in need of urgent treatment.

I don't want to be palmed off anymore with the first simple excuse the Helpdesk people can think of.

If Stephen reads this, please help!!!

Thanks,
Rob
PS All use MySQL8 too

PPS - just to show I'm not being too fussy, below is an email received this morning.

Hi there

I like the website & have uploaded some photos – but – getting the home page up often = unsuccessful, or times out. Even when I have logged in (and trying to look at the photo gallery, for instance) pages often take ages to load – and sometimes time out.

Hmm – your site is the only one that I am having trouble with – I have fairly new ‘kit’ & (regrettably/sadly, etc!) spend quite a lot of time on line = I think the problem (if there is one) is with your server.

Anyone your end any good with a spanner?

Not really a complaint – more of an observation

Keep up the good work

DV
 
It's been said what is the issue all along, they will move you to web16 with apache recompiled to resolve.
 
Ah Stephen, thank you. So it's *not* me "abusing" the server then - perhaps the Helpdesk staff should admit to the problem being a duff server rather than blaming me!!

What are the implications for me re moving to Web16? (downtime etc)

Thanks for replying so promptly - very much appreciated.
 
BluJag said:
Ah Stephen, thank you. So it's *not* me "abusing" the server then - perhaps the Helpdesk staff should admit to the problem being a duff server rather than blaming me!!

What are the implications for me re moving to Web16? (downtime etc)

Thanks for replying so promptly - very much appreciated.
Click to expand...

There is nothing duff about the server, it is just something that comes up when PHP is used heavily due to the way the php is working, and certain apps, make the errors come sooner than others, joomla is one that makes it come more, due to a large amount of includes and other factors, it isn't 'your site' as much as it is the config but it is not a server issue so much as a compilation issue. I am trying to get an update on linux team for when this will proceed to more servers, the problem is sporadically bad based on different usage levels of apps.

Basically there is a hard limit compiled into apache for how many items can process and it has to be raised, that causes some other issues in other areas, so it takes quite an extensive amount of time and tweaking on each server. We've done this on a couple server so far, and those that have it work very well.

Also just as a note, Joomla, wordpress, and mambo sites are being botnet scanned in a huge way of late due to a vast number of wholes in their addon components, so the amount of overall processing of PHP may be up even if you are not vulnerable to those exploits.
 
Crikey, well beyond my meagre understanding! Not sure what to do now - some clients screaming blue murder - I don't suppose upgrading to a different reseller package would make any difference? The service level guarantee of 99.9% does not apply to Web4 in my opinion - from the users point of view it is most definitely duff.
 
BluJag said:
Crikey, well beyond my meagre understanding! Not sure what to do now - some clients screaming blue murder - I don't suppose upgrading to a different reseller package would make any difference? The service level guarantee of 99.9% does not apply to Web4 in my opinion - from the users point of view it is most definitely duff.
Click to expand...
Oh I forgot to answer there, an in-place move and be done, you don't have to do much or anything really. It is just an account move needed. Ask for the move to happen and it takes from 24-36 hours in normal cases to complete. It locks the CP from making changes during this time.
 
We are also working on getting a schedule in place for the rollouts finally, it is not set yet but being discussed :)
 
Thanks cc9 - but unfortunately the forum won't let me in to view your post!

But, if the mighty Stephen is reading this what do you make of it? (MySQL8 that is?)
 
I have a customer on web13 with a phpBB forum database that was on mysql8. It was running extremely slow at times and suffering from a variety of sql errors. After moving the database to mysql9, the site has been running flawlessly. The website remains on web13.

The database move was quite painless. It was a simple case of creating a new database on mysql9, backing up the database on mysql8 to the webserver, then restoring it to mysql9. Downtime was minimal YMMV depending on the size of the database.
 
BluJag said:
Thanks cc9 - but unfortunately the forum won't let me in to view your post!

But, if the mighty Stephen is reading this what do you make of it? (MySQL8 that is?)
Click to expand...
send a PM with hosting username to me, and you can then be allowed access to the customer only section where that is...I am leaving this matter to the linux dept, it is out of my realm.
 
Thanks cc9 and nzkiwi - I've pm'd Stephen. You've both shed some light on this problem with my Joomla sites and I'm very grateful.

Thanks
Rob
 
You must log in or register to reply here.
Back
Top