firstclass

Having spent a month or so without seeing this ugly error, its back with a vengeance today. All connections are closed, none are permanent. Back to the same old suspicions - this is not my site.

Thanks... I'll blame my daughter... maybe she decided to button mash F5! (she is only 19 months old)

Fixed... excellent - Thanks! Any hint what it was (for future reference?)

Been like this now for ~19 hours. Can't access my own site, let alone administer it. And it appears I'm not alone. I've logged in from my phone to grab a backup of the database... which isn't a good sign. Can we check if my IP is restricted please? 84.92.14.165 for info: username: fcricket site: firstclass.heliohost.org (but can't access any stevie site) server: stevie

yes. And different computers (on the same internet connection). And cleared the DNS cache just in case.

Very strange. Have I perhaps been IP locked? Though I have no idea why I might have been. I've not got a cached page etc, I have "took too long to respond" - but I have tried that. But as you say, it seems ok from elsewhere... my phone can access the site! Oh, and thanks for the really quick reply.

I can't access my site www.firstclass.heliohost.org, or login to cpanel (host taking too long to respond)... but the front page and server monitor seem to suggest no problem. Other stevie sites I know are having identical problems. What's going on?

It was, it's back.

Thank You for installing cPanel / WHM. This server is currently not licensed. Please contact the server administrator. Other services available on this server such as web services are likely functioning normally. (License has a future date) Once the license on this server is active, you will no longer see this message. If you have installed a license since loading this page, click here to reload.

Happened a couple of times again today. Again while the server was very slow, even when I have no other online users.

I've not seen it for a day or 2. And I found a bug in the code that potentially opened multiple (never more than 3) connections and only closed one of them (they all had the same identifier!) That can't happen now, hopefully that was the cause of the issues. But this forum isn't the most active place, it's difficult to know If I'm alone with the errors, particularly when they last for ~10 seconds (even if regularly), if no-one spots, or reports or does so here.

See first post, Stevie. I've made a change today that I hope will make a difference... time will tell.

So any more suggestions? I'm guessign I'm right and it's a global connection limit that's getting exceeded.

As I said I believe ALL connections are closed by our scripts, I've tried the switch to persistent connections but I expect the same result. I'm still left suspicious:

I don't think that can be the problem, they are closed in the php files, but should auto-close at the end of the PHP anyhow. NOTHING shows up when using "SHOW PROCESSLIST" except that command itself.