Major Logging Outage Disrupts Thousands of Drivers and Carriers
Source: Transportation Nation Network
Minnetonka, MN Thousands of drivers and carriers are once again being disrupted by a major electronic logging devices (ELD) outage.
PeopleNets on-board ELD devices operating on its g3 system began experiencing rebooting issues as the clock struck midnight on January 1 GMT (which is December 31, 2019 at approximately 7 p.m. EDT), according to a Trimble Transportation company spokesperson.
Truckers quickly began reporting the problems such as slow log-ins and other malfunctions, which has led to customer support wait times as high as four hours.
A company representative explained the problems were caused by a discrepancy between the GPS satellite time and the g3s internal clock.
The outage is being described as a repeat of Y2K.
Essentially, the devices had an operating range between 2007 and 2019. When the calendar rolled into 2020, the servers could no longer recognize the date of the affected ELDs. Diagnostic notification messages began appearing on the devices displays which read, This device is not functioning as an ELD. Paper logs may be required as back up. Check manual for instructions.
As of Sunday morning, a recorded message from the company says a fix has been identified, but customer action is required to completely resolve the issue. A company representative says an email has been sent to customers containing the resolution steps.
Read more: https://transportationnation.com/breaking-major-eld-outage-disrupts-thousands-of-drivers-and-carriers/
Interesting.
How do we know this is a faulty log, and not a major cyber attack by Iran? Or Russia?
Affects much of the Trucking system nation wide.
Recursion
(56,582 posts)We do that all on our own
Quackers
(2,256 posts)And theyve already identified the cause. The internal clock does not match the GPS networks time clocks.
Its kind of like if you change your phones clock to manual and change the date and time. Some things still work but it causes all kinds of issues on your phone and with apps. Ironically, you can use this trick to hack certain game prizes that are based on time. For example, opening a reward early by fooling the game into thinking the wait time has already passed.
csziggy
(34,139 posts)While on a cruise I had a problem using their system, the public computers were reset to "original condition" every night. Problem was, it also reset the date and time to whenever that backup had been made. This meant that web sites that checked for certification rejected access since the computer's date and time did not match reality.
The other problem was that they had changed the printer for the computers in the ship's library. The printer on the backup was a completely different brand and model than the one actually at the physical location. Since they had locked out administrator access, every day their IT guys had to come in and reset the date and reload the printer drivers.
At the end of the cruise many passengers were trying to print their account or tickets for the next leg of their trips and it was chaos. I had to make five trips to the library just to print one document - first, because of the date/time glitch, I couldn't log into my email, next time the printer glitch showed up, then they were out of paper, next day date/time AND printer redux. Finally I managed to print the pages I needed. The irony was that I ended up not needing those pages at all.
2naSalit
(86,878 posts)event but automation of this sort is dangerous and doesn't save us as much time nor does it give us the conveniences promised since it's all so vulnerable. How will we be able to function if computer systems go down for long periods?
mwooldri
(10,303 posts)However we don't appear to have experienced this problem. Probably because we're operating on a different system and we graduated from AOBRD electronic logs to ELD last year (all motor carriers were required to have ELD by some date end of last year). I needed new hardware for the ELD to function correctly.
From the driver's point of view, having to go to paper backup instead of ELD can be a plus point. Drivers have Hours of Service rules to work to... once you run out of time the ELD device is enforcing the proper restrictions (and in a way I do like this). However there are times that it is useful to push the limits beyond the official hours and with a paper log one can put down fictitious data and say they drove 11 hours (the max) when they drove 13 or 14 hours. It's why in CB slang the log book is referred to as the "comic book".
dware
(12,449 posts)Paper logs were a pain in the ass at times, but I could fudge them if I accidently went over my HOS, with the ELD, no chance of that.
MineralMan
(146,339 posts)Occam's Razor.
Ziggysmom
(3,429 posts)Very true. The simplest explanation IS most often the correct explanation.
As an IT analyst who also worked during the Y2K era, I am appalled that the company did not see this as a potential problem.
One issue I see in the IT field now is working alongside H2B Visa workers corporations hire on to complete projects with cheap labor. Now dont get me wrong, I am not against immigration, but it is often challenging to communicate business and technology terms to coworkers where English is their 2nd language.
We are the United Corporations of Americas now, where profits come before people.
Rural_Progressive
(1,107 posts)and am constantly amazed at the ignorance of both the public and professionals.
Was there a great deal of fraud and inefficiency involved in the Y2K fix? Absolutely!!
Would much of the world's computer systems and networks have failed had those fixes not been implemented? No doubt about it!!
Problem is if you prevent a catastrophe from happening you can never prove it would have without the steps being taken to prevent it.
Oh well, apparently we will continue to stumble our way through disaster after disaster until one finally bites us in the butt so badly that we go down as a result.