Microsoft server crash leaves 800 planes with no contact with ATC

#1

Post by vmcodes » Mon, Aug 24, 2009, 9:00 PM UTC

... The servers are timed to shut down after 49.7 days of use in order to prevent a data overload, a union official told the LA Times. To avoid this automatic shutdown, technicians are required to restart the system manually every 30 days.

Microsoft server crash leaves 800 planes with no contact with ATC
news.techworld.com

Re: Microsoft server crash leaves 800 planes with no contact with ATC

#2

Post by username » Mon, Aug 24, 2009, 9:34 PM UTC

Desmond?

Re: Microsoft server crash leaves 800 planes with no contact with ATC

#3

Post by param » Mon, Aug 24, 2009, 9:46 PM UTC

Sounds more like a fault of the application than the OS. M$ in the title seems to be there for page views

Re: Microsoft server crash leaves 800 planes with no contact with ATC

#4

Post by russss » Mon, Aug 24, 2009, 10:03 PM UTC

It's worth noting that this article is from September 2004.

49.7 days is 2^32 milliseconds. Although this used to cause issues with Win98, they claimed to be using 2000, so it was probably an application-related bug rather than anything Microsoft should be blamed for.

Re: Microsoft server crash leaves 800 planes with no contact with ATC

#5

Post by devicenull » Tue, Aug 25, 2009, 12:22 AM UTC

So this is essentially human error because someone failed to restart the server. The same thing would have happened if it was running Linux, Unix, etc.

Re: Microsoft server crash leaves 800 planes with no contact with ATC

#6

Post by fatdog789 » Tue, Aug 25, 2009, 3:00 AM UTC

This is both inaccurate and out-dated.

Re: Microsoft server crash leaves 800 planes with no contact with ATC

#7

Post by ryanpetrich » Tue, Aug 25, 2009, 10:55 PM UTC

russss wrote: post #4

It's worth noting that this article is from September 2004. 49.7 days is 2^32 milliseconds. Although this used to cause issues with Win98, they claimed to be using 2000, so it was probably an application-related bug rather than anything Microsoft should be blamed for.

GetTickCount() wraparound bug.