Knownhost vz34-ca node down numerous times

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Knownhost vz34-ca node down numerous times

Posted by lottos, 03-04-2013, 04:21 PM
Sigh. I've been with KH for 6 years and I'm now wondering if they are not what they used to be.

My node went down for the second time within 12 hours, the third time was a week ago.

I guess KH have a better idea of what is going on but personally I wonder if they have grown too big (many customers, servers and rocketvps as well) and are human resource stretched, or whether the new plans around December caused some type of config issue.

I've also seen numerous issues reported on other nodes that have been put down to kernel issues.
Posted by KnownHost-Jonathan, 03-04-2013, 04:26 PM

Quote:

Originally Posted by lottos

Sigh. I've been with KH for 6 years and I'm now wondering if they are not what they used to be.

My node went down for the second time within 12 hours, the third time was a week ago.

I guess KH have a better idea of what is going on but personally I wonder if they have grown too big and are human resource stretched, or whether the new plans around December caused some type of config issue.

I've also seen numerous issues reported on other nodes that have been put down to kernel issues.

Sorry for the frustration regarding this node. I know it's a hassle.

Just wanted to make sure you've seen our forum post here: http://forums.knownhost.com/showthread.php?t=3746

We gathered data from the node prior to it's crash and have been sifting through it to isolate the issue that's been causing this on a couple of our nodes.
Posted by lottos, 03-04-2013, 04:41 PM

Quote:

Originally Posted by KnownHost-Jonathan

Sorry for the frustration regarding this node. I know it's a hassle.

Just wanted to make sure you've seen our forum post here: http://forums.knownhost.com/showthread.php?t=3746

We gathered data from the node prior to it's crash and have been sifting through it to isolate the issue that's been causing this on a couple of our nodes.

Thanks Jonathon. Given there was 12 hours between crashes, that just makes me wonder why the data was not actioned after the first crash yesterday where there was a 12 hour period rather than almost immediately after the second (ie - perhaps the 2nd crash could have been avoided). Assuming moving one of the VPS's as reported on http://forums.knownhost.com/showthread.php?t=3746 was the cause.
Posted by KnownHost-Jonathan, 03-04-2013, 04:43 PM

Quote:

Originally Posted by lottos

Thanks Jonathon. Given there was 12 hours between crashes, that just makes me wonder why the data was not actioned after the first crash yesterday where there was a 12 hour period rather than almost immediately after the second (ie - the 2nd crash could have been avoided).

Because the first time around the server was in such bad shape that it was all we could do to get into it and do a semi-clean shutdown to prevent data loss and FSCK.

We were monitoring it and caught it and got data from the most recent would-be crash and have taken action to hopefully correct the issue. Only time will tell now.
Posted by lottos, 04-19-2013, 02:33 AM
Sigh. Packet loss at CA.
Posted by KnownHost-Jonathan, 04-19-2013, 08:56 AM

Quote:

Originally Posted by lottos

Sigh. Packet loss at CA.

Quote:

Originally Posted by lottos

None in CA.

There was a DDoS attack against our CA network. We identified and null-routed the target IP within 30 minutes. Unfortunately we usually catch these much quicker but this one took a minute.

<<snipped>>