News: 1694050155

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Toyota servers ran out of storage, crashed production at 14 plants in Japan

(2023/09/07)


Toyota has revealed a server running out of disk space after botched maintenance was the cause of an outage that forced it to shut down 14 manufacturing plants across Japan last week.

“The system malfunction was caused by the unavailability of some multiple servers (sic) that process parts orders,” states a company [1]announcement posted on Wednesday.

Those servers went down after regular maintenance work was performed on August 27. But [2]someone botched that job.

[3]

"During the maintenance procedure, data that had accumulated in the database was deleted and organized, and an error occurred due to insufficient disk space, causing the system to stop," Toyota’s announcement explains.

[4]

[5]

"Since these servers were running on the same system, a similar failure occurred in the backup function, and a switchover could not be made. We think that means Toyota's production and backup servers are identical, so failover failed because the backup rig was also out of space."

Whatever the exact circumstances, the mess led to the plug being pulled on vehicle production.

[6]Microsoft admits slim staff and broken automation contributed to Azure outage

[7]UK flights disrupted by 'technical issue' with air traffic computer system

[8]Bank of Ireland outage sees customers queue for 'free' cash – or maybe any cash

[9]Voyager 2 found! Deep Space Network hears it chattering in space

The fix?

"The system was restored after the data was transferred to a server with a larger capacity on August 29," Toyota's statement reveals. But by then around 36 hours of production time had been lost.

[10]

The Register feels on solid ground suggesting that Toyota – a master of just-in-time manufacturing – has a recovery time objective rather shorter than 36 hours.

The Japanese auto giant's techies have determined the root cause of the issue, and developed countermeasures to prevent its recurrence. The Corolla-maker has pledged to "review our maintenance work procedures and strengthen our efforts to prevent recurrence in order to deliver as many cars as possible to our customers as quickly as possible.”

A small piece of good news to emerge from the mess is that Toyota's original assertion it was not the victim of a cyber attack has proved correct. ®

Get our [11]Tech Resources



[1] https://global.toyota/en/newsroom/corporate/39732568.html

[2] https://www.theregister.com/2023/08/30/toyota_japan_production_resumes/

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZPlK4UbFYr6@9hZkNEJv8wAAA1Y&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZPlK4UbFYr6@9hZkNEJv8wAAA1Y&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZPlK4UbFYr6@9hZkNEJv8wAAA1Y&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://www.theregister.com/2023/09/04/microsoft_australia_outage_incident_report/

[7] https://www.theregister.com/2023/08/28/uk_flights_disrupted/

[8] https://www.theregister.com/2023/08/16/bank_of_ireland_outage/

[9] https://www.theregister.com/2023/08/02/voyager_2_signal_detected/

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZPlK4UbFYr6@9hZkNEJv8wAAA1Y&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[11] https://whitepapers.theregister.com/



Lost in Translation?

An_Old_Dog

From TFA: data that had accumulated in the database was deleted and organized

How does one "organize" data which has been "deleted" from a database? (I'm presuming "organized" in this case means, "re-organized".)

* JHM wonders what Joey did to earn "I'd just like to say, for the record,
that Joey rules."
-- Seen on #Debian