Thanks for the patience with the server errors on match days for the past month.
There's been a few more config changes - I'd appreciate if you could report any specific server error messages or server issues in this thread for the server technicians. The comments/screenshots you've all shared have been used by server folk to work to resolve the issue.
If we get any more errors, it'll likely be Saturday so can you please reply with any screenshots/comments if you get any?
We have a brilliant hosting company.
We're on a very good dedicated server that can handle 10x the traffic we see at our busiest period.
It's not a case of 'putting another 50p in the meter' - for those who have kindly shared their insights to help troubleshoot, the last update is;
Lets see how we go.
There's been a few more config changes - I'd appreciate if you could report any specific server error messages or server issues in this thread for the server technicians. The comments/screenshots you've all shared have been used by server folk to work to resolve the issue.
If we get any more errors, it'll likely be Saturday so can you please reply with any screenshots/comments if you get any?
We have a brilliant hosting company.
We're on a very good dedicated server that can handle 10x the traffic we see at our busiest period.
It's not a case of 'putting another 50p in the meter' - for those who have kindly shared their insights to help troubleshoot, the last update is;
As the problem started when we did the Ubuntu upgrade I’m certain that a limit or setting we had set before has been overwritten however as the above is a fairly generic Apache error it doesn’t tell us exactly what limit is being hit. I’ve made a couple of changes for you this morning, firstly I’ve increased the global Apache timeout from 300 seconds to 600 seconds. I’ve also increased the MaxKeepAlive setting from 100 to 500. I’ll keep an eye on the logs for you but we may need the site to get busy again for us to see if the changes have worked.
Lets see how we go.