Too many accounts on the server, 543 to be exact

[Karl]

The issue that occurred earlier today only affected my account because my site is on a "dedicated IP" and somehow the IP became "unbound" from the network interface. Unfortunately, it didn't get fixed until I contacted support about an hour and a half later, although I definitely should have opened the ticket earlier.

The only reason I have a pingdom account is because I use it to monitor servers for clients and I have a few slots left so I added it.

OK, I had initially been confused, as the issues with web5 had been sorted out over a week ago. This is just evidence that if you're having problems, please contact us. We cannot possibly be able to help you if we are not made aware of the issue. Just as with this case, where it seems the issue was repaired shortly after we were contacted.

This is not a one way street, we do not know what the experience of each and every customer is. That means contact us if you have problems, contact us if things are going well. The more information we have, the better we can serve you.

[phaselight]

Same problem. Just contacted support. Mine has been down for 7 hrs and 20 mins and it's on web5. It's on a dedicated IP as well.

[Ray]

That means contact us if you have problems, contact us if things are going well. The more information we have, the better we can serve you.

Indeed. It's a lot easier to fix problems knowing that they exist. As much as I'd like there to be a way to constantly watch every single account with monitoring, it's just not feasible.

[The Universes]

OK, I had initially been confused, as the issues with web5 had been sorted out over a week ago. This is just evidence that if you're having problems, please contact us. We cannot possibly be able to help you if we are not made aware of the issue. Just as with this case, where it seems the issue was repaired shortly after we were contacted.

This is not a one way street, we do not know what the experience of each and every customer is. That means contact us if you have problems, contact us if things are going well. The more information we have, the better we can serve you.

Yeah, I understand, the issue wouldn't be obvious on your end and I don't think it was SF's fault.

However, the migration issues on web5 (which happened 1-2? weeks ago), which I was referring to, is.

Edit:
Maybe SF can setup some sort of hourly checks that make sure the dedicated IPs are bound properly and working.

[Karl]

As was posted in the announcement, https://support.steadfast.net/index....ews&newsid=175, the issue was actually a bug in Litespeed which happened to crop up at the same time as the migrations. We had initially assumed the issue was with the migrations, but the problem seemed to continue even when migrations weren't being performed. The issue was that when Litespeed was trying to gracefully restart it would just crash, etc. Without that issue, there should have been no real noticeable downtime from the migrations.