Slashdot Mirror


Software Update Shuts Down Nuclear Power Plant

Garabito writes "Hatch Nuclear Power Plant near Baxley, Georgia was forced into a 48-hour emergency shutdown when a computer on the plant's business network was rebooted after an engineer installed a software update. The Washington Post reports, 'The computer in question was used to monitor chemical and diagnostic data from one of the facility's primary control systems, and the software update was designed to synchronize data on both systems. According to a report filed with the Nuclear Regulatory Commission, when the updated computer rebooted, it reset the data on the control system, causing safety systems to errantly interpret the lack of data as a drop in water reservoirs that cool the plant's radioactive nuclear fuel rods. As a result, automated safety systems at the plant triggered a shutdown.' Personally, I don't think letting devices on a critical control system accept data values from the business network is a good idea."

6 of 355 comments (clear)

  1. Critical Updates by Zekasu · · Score: 0, Redundant

    Critical Updates are ready to be installed on your nuclear reactor. You must restart to complete them.

    That's what you get for using Microsoft.

  2. Obligatory by Enderandrew · · Score: 0, Redundant

    I for one welcome our new radioactive overlords.

    Press hot grits to continue.

    In Soviet Russia, reactor reboots you.

    Yes, but does the reactor run Linux?

    1) Break crucial system on reactor with update
    2) Sell real update
    3) Profit!

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  3. Maybe this was a case of... by arhhook · · Score: 0, Redundant

    Patch Tuesday?

    --
    [Insert signature here]

  4. Re:Oblig Simpsons reference by truthsearch · · Score: 1, Redundant

    Hey! All I have to type is Y. (To Marge) Hey, Miss Doesn't-find-me-attractive-sexually-anymore: I just tripled my productivity!

  5. Where is the redundancy? by JSBiff · · Score: 1, Redundant

    The thing I'm a bit puzzled about. . . if this system has data which is so important that the whole plant must be SHUT DOWN for two days if it fails, then why aren't there *at least* TWO of them (I'd say there's a good argument for 3 or 4, but. . .)? That way, you can take one out of the loop for updates, verify the update didn't hose your data, sync the data from the 'live' system, then put it online, take the other one offline, and complete the update on it.

    If I were the power co owning this plant, I'd be ticked if the plant was dark for 2 days. With the price of energy these days, and the amount of energy a single Nuclear plant can generate, you're talking some real serious cash when the thing is down for 2 days. Especially if I have to look forward to the same thing happening again, potentially every time our systems need updating (not that it necessarily would happen every time, I would sure hope it wouldn't, but with only one system, every update is a potential for the whole plant to go down for some period of time).

  6. Re:Fail-Safe by Sitnalta · · Score: 0, Redundant

    That's my point. I don't want a reactor with ANY flaws. No matter how safe its default shutdown threasholds are.