Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm not so sure that's an accurate diagnosis. But I agree it's certainly better than one can get from phoning support.




I can't speak to the accuracy of the diagnosis, but the claims about NTP are bizarre, and to the best of my knowledge, wrong. There's nothing specific about the times the incidents cluster around that would have anything to do with NTP. It doesn't work like that.

We're talking about this line, right?

>The precision of outages (at :29 and :44) matches a network-synchronized clock (NTP).

I think this just correctly points out that if the trigger was something unsynchronized like animals chewing on wires or someone digging underground, you wouldn't have 61% of events occurring at these two second markers. Even if the trigger was something digital but on a machine that isn't NTP synchronized, you would eventually have enough clock drift to move the events to other seconds. 61% combined at two markers (exactly 15 seconds apart) strongly suggests synchronized time.


Those are minutes not seconds.

Though, if I was the author the speculation about the restart time would have me breaking out a timer.

Customer support isn't allowed to tell you to attack the box with a hammer. But if they could be totally honest...

Oops, I accidentally destroyed your infrastructure with my car. Please roll a truck.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: