Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method arrays::explode_key() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_entry.php on line 254
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method fileio::file_listing() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 29
Strict Standards: Non-static method fileio::file_listing() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 29
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method fileio::write_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 17
Strict Standards: Non-static method fileio::make_dir() should not be called statically in /www/htdocs/sgraman/blog/scripts/classes/fileio.php on line 70
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method arrays::explode_key() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_entry.php on line 254
Strict Standards: Non-static method fileio::strip_extension() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 41
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method arrays::explode_key() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_entry.php on line 254
Strict Standards: Non-static method fileio::strip_extension() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 41
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Browsing the internet I stumbled across this article from ZD-Net Australia regarding the top 10 worst IT disasters of all time. Being a computer guy I found it rather amusing although some of them - like No. 1 - is rather scary. My favorite disasters are No. 4 and 5, so clumsy... Enjoy the somewhat lenghly reading.1. Faulty Soviet early warning system nearly causes WWIII (1983)
The threat of computers purposefully starting World War III is still the stuff of science fiction, but accidental software glitches have brought us worryingly close in the past. Although there are numerous alleged events of this ilk, the secrecy around military systems makes it hard to sort the urban myths from the real incidents.
However, one example that is well recorded happened back in 1983, and was the direct result of a software bug in the Soviet early warning system. The Russians' system told them that the US had launched five ballistic missiles. However, the duty officer for the system, one Lt Col Stanislav Petrov, claims he had a "...funny feeling in my gut", and reasoned if the US was really attacking they would launch more than five missiles.
The trigger for the near apocalyptic disaster was traced to a fault in software that was supposed to filter out false missile detections caused by satellites picking up sunlight reflections off cloud-tops.
2. The AT&T network collapse (1990)
In 1990, 75 million phone calls across the US went unanswered after a single switch at one of AT&T's 114 switching centres suffered a minor mechanical problem, which shut down the centre. When the centre came back up soon afterwards, it sent a message to other centres, which in turn caused them to trip and shut down and reset.
The culprit turned out to be an error in a single line of code -- not hackers, as some claimed at the time -- that had been added during a highly complex software upgrade. American Airlines alone estimated this small error cost it 200,000 reservations.
3. The explosion of the Ariane 5 (1996)
In 1996, Europe's newest and unmanned satellite-launching rocket, the Ariane 5, was intentionally blown up just seconds after taking off on its maiden flight from Kourou, French Guiana. The European Space Agency estimated that total development of Ariane 5 cost more than US$8bn. On board Ariane 5 was a US$500m set of four scientific satellites created to study how the Earth's magnetic field interacts with Solar Winds.
According to a piece in the New York Times Magazine, the self-destruction was triggered by software trying to stuff "a 64-bit number into a 16-bit space".
"This shutdown occurred 36.7 seconds after launch, when the guidance system's own computer tried to convert one piece of data -- the sideways velocity of the rocket -- from a 64-bit format to a 16-bit format. The number was too big, and an overflow error resulted. When the guidance system shut down, it passed control to an identical, redundant unit, which was there to provide backup in case of just such a failure. But the second unit had failed in the identical manner a few milliseconds before. And why not? It was running the same software," the article stated.
4. Airbus A380 suffers from incompatible software issues (2006)
The Airbus issue of 2006 highlighted a problem many companies can have with software: what happens when one program doesn't talk to another. In this case, the problem was caused by two halves of the same program, the CATIA software that is used to design and assembly of one of the world's largest aircraft, the Airbus A380.
This was a major European undertaking and, according to Business Week, the problem arose with communications between two organisations in the group: the French Dassault Aviation and a Hamburg factory.
Put simply, the German system used an out-of-date version of CATIA and the French system used the latest version. So when Airbus was bringing together two halves of the aircraft, the different software meant that the wiring on one did not match the wiring in the other. The cables could not meet up without being changed.
The problem was eventually fixed, but only at a cost that nobody seems to want to put an absolute figure on. But all agreed it cost a lot, and put the project back a year or more.
5. Mars Climate Observer metric problem (1998)
Two spacecraft, the Mars Climate Orbiter and the Mars Polar Lander, were part of a space program that, in 1998, was supposed to study the Martian weather, climate, and water and carbon dioxide content of the atmosphere. But a problem occurred when a navigation error caused the lander to fly too low in the atmosphere and it was destroyed.
What caused the error? A sub-contractor on the Nasa programme had used imperial units (as used in the US), rather than the Nasa-specified metric units (as used in Europe).
6. EDS and the Child Support Agency (2004)
Business services giant EDS waded in with this spectacular disaster, which assisted in the destruction of the Child Support Agency (CSA) and cost the taxpayer over a billion pounds.
EDS's CS2 computer system somehow managed to overpay 1.9 million people and underpay around 700,000, partly because the Department for Work and Pensions (DWP) decided to reform the CSA at the same time as bringing in CS2.
Edward Leigh, chairman of the Public Accounts Committee, was outraged when the National Audit Office subsequently picked through the wreckage: "Ignoring ample warnings, the DWP, the CSA and IT contractor EDS introduced a large, complex IT system at the same time as restructuring the agency. The new system was brought in and, as night follows day, stumbled and now has enormous operational difficulties."
7. The two-digit year-2000 problem (1999/2000)
A lot of IT vendors and contractors did very well out of the billions spent to avoid what many feared would be the disaster related to the Millennium Bug. Rumours of astronomical contract rates and retainers abounded.
And the sound of clocks striking midnight in time zones around the world was followed by... not panic, not crashing computer systems, in fact nothing more than new year celebrations.
So why include it here? That the predictions of doom came to naught is irrelevant, as we're not talking about the disaster that was averted, but the original disastrous decision to use and keep using for longer than was either necessary or prudent double digits for the date field in computer programs. A report by the House of Commons Library pegged the cost of fixing the bug at 400 billion pounds. And that is why the Millennium Bug deserves a place in the top 10.
8. When the laptops exploded (2006)
It all began simply, but certainly not quietly, when a laptop manufactured by Dell burst into flames at a trade show in Japan. There had been rumours of laptops catching fire, but the difference here was that the Dell laptop managed to do it in the full glare of publicity and video captured it in full colour.
"We have captured the notebook and have begun investigating the event," a Dell spokesperson reported at the time, and investigate Dell did. At the end of these investigations the problem was traced to an issue with the battery/power supply on the individual laptop that had overheated and caught fire.
It was an expensive issue for Dell to sort out. As a result of its investigation Dell decided that it would be prudent to recall and replace 4.1 million laptop batteries.
Company chief executive Michael Dell eventually laid the blame for the faulty batteries with the manufacturer of the battery cells -- Sony. But that wasn't the end of it. Apple reported issues for iPods and Macbooks and many PC suppliers reported the same. Matsushita alone has had to recall around 54 million devices. Sony estimated at the time that the overall cost of supporting the recall programmes of Apple and Dell would amount to between 20bn yen and 30bn yen
9. Siemens and the passport system (1999)
It was the summer of 1999, and half a million British citizens were less than happy to discover that their new passports couldn't be issued on time because the Passport Agency had brought in a new Siemens computer system without sufficiently testing it and training staff first.
Hundreds of people missed their holidays and the Home Office had to pay millions in compensation, staff overtime and umbrellas for the poor people queuing in the rain for passports. But why such an unexpectedly huge demand for passports? The law had recently changed to demand, for the first time, that all children under 16 had to get one if they were travelling abroad.
Tory MP Anne Widdecombe summed it up well while berating the then home secretary, Jack Straw, over the fiasco: "Common sense should have told him that to change the law on child passports at the same time as introducing a new computer system into the agency was storing up trouble for the future."
10. LA Airport flights grounded (2007)
Some 17,000 planes were grounded at Los Angeles International Airport earlier this year because of a software problem. The problem that hit systems at United States Customs and Border Protection (USCBP) agency was a simple one caused in a piece of lowly, inexpensive equipment.
The device in question was a network card that, instead of shutting down as perhaps it should have done, persisted in sending the incorrect data out across the network. The data then cascaded out until it hit the entire network at the USCBP and brought it to a standstill. Nobody could be authorised to leave or enter the US through the airport for eight hours. Passengers were not impressed.
Source: ZD-Net Australia
i need more related information
interesting
Add Comment
Fill out the form below to add your own comments.Strict Standards: Non-static method fileio::read_file() should not be called statically in /www/htdocs/sgraman/blog/scripts/sb_fileio.php on line 13
Calendar
