SITE5 Down ?

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > SITE5 Down ?

Posted by enricoeur, 07-31-2009, 09:35 AM
Hi,

i cannot reach any of my accounts on site5 from 1 hour....

Do you know what is happen ?

Thanks
Posted by Sparrow-Sean, 07-31-2009, 09:39 AM
Yes it seems down to me aswell.. I am not sure of the situation over there at the moment.

Sean
Posted by sirius, 07-31-2009, 09:41 AM
http://twitter.com/site5

Sirius
Posted by The-Pixel, 07-31-2009, 10:17 AM
It's still not loading for me. I see they are updating Twitter regularly which is always nice to see. I wouldn't stress or worry I don't recall Site5 going down alot. I hope it gets resolved quickly. Best of luck!
Posted by stablehost, 07-31-2009, 11:03 AM
Looks like they had an issue with named.pid having the wrong permission which made bind fail when they updated to the new version.

Surprised they didn't do one nameserver at a time, rookie move, Site 5.
Posted by The-Pixel, 07-31-2009, 12:03 PM

Quote:

Originally Posted by nerdie

Looks like they had an issue with named.pid having the wrong permission which made bind fail when they updated to the new version.

Surprised they didn't do one nameserver at a time, rookie move, Site 5.

Very good point.
Posted by FastServ, 07-31-2009, 12:07 PM
We didn't have any issues with CentOS RPM update for bind* on dozens of servers. Blaming it on RHEL/CentOS is low; they must have had a misconfiguration to begin with.
Posted by JohnCrowley, 07-31-2009, 01:27 PM

Quote:

Originally Posted by FastServ

We didn't have any issues with CentOS RPM update for bind* on dozens of servers. Blaming it on RHEL/CentOS is low; they must have had a misconfiguration to begin with.

Agreed. We updated 100+ servers without any issues using both centOS and RHEL 3/4/5.

- John C.
Posted by stablehost, 07-31-2009, 01:31 PM

Quote:

Originally Posted by JohnCrowley

Agreed. We updated 100+ servers without any issues using both centOS and RHEL 3/4/5.

- John C.

It must have been the current version they were migrating to because a few of our servers had a permission problem too.

Hopefully, it didn't cause downtime... because we prepare..
Posted by MikeDVB, 07-31-2009, 08:57 PM
We had some issues with bind after updating however we tested the new version on our dev boxes before we rolled it out to our production servers.

Had Site5 tested this update before rolling it out to their services they could have avoided this issue imho.
Posted by bwb, 08-02-2009, 02:01 AM

Quote:

Originally Posted by nerdie

Looks like they had an issue with named.pid having the wrong permission which made bind fail when they updated to the new version.

Surprised they didn't do one nameserver at a time, rookie move, Site 5.

Correct, it was a failure on our part, there was a major miscommunication on the backside with our change management procedures. And instead of one server being upgraded and tested before a full rollout two were done at the same time. It should never happen again after this and I apologize for the downtime.

Let me know if you have any Qs,
Thanks, Ben