Mapping issue or GPS issue

I got a weird one for you, some of our cars have been having the following issue:
They "lock" on the map displaying online with the state time as "2020-11-XX 18:59:54" which is in the future from the actual time...which explain why they lock because the server thinks that's the NEWEST position. However if you open the logs and read the incoming positions they are correct, and if you run a route history the position are fully correct and updated. I can't tell if the GPS units (though not all of them are doing this) is giving out this date/time issue or the server is freaking on something. I went to poke around the DB to see if I could find the 2020-11-XX 18:59:54 entry but I can't figure out which table it would be in.
This only started after the upgrade to 4.11.

Thoughts or theories? Or what table I can look in and see the "time" this time is coming in at (like maybe when the GPS boots it sends that time).

It's pretty common situation when you get a single position "from the future". You need to find the place where it all started and check if it's an invalid position device reported or it's a server decoding issue.

In the log file or the db?

In the log. Otherwise how would you know if it's a decoding issue?

Good point...thanks!

2020-11-19 19:00:41  INFO: [be75acfc] id: Car 05, time: 2020-11-20 18:59:10, lat: x long

Based on that I'm going to say device issue correct?

You need to look at the HEX.

2447504747412c3233353835322e30302c343030322e3438333832332c4e2c30373631382e3437373438382c572c312c30362c302e372c3131362e382c4d2c2d34302e302c4d2c2c2a35420d0a2447505654472c3234392e342c542c3235382e342c4d2c302e302c4e2c302e302c4b2c412a32330d0a244750524d432c3233353835322e30302c412c343030322e3438333832332c4e2c30373631382e3437373438382c572c302e302c3234392e342c3139313132302c392e302c572c412a33450d0a2450435054492c4361722030362c3233353835322c3233353835322a30340d0a

$GPGGA,235852.00,4002.483823,N,07618.477488,W,1,06,0.7,116.8,M,-40.0,M,,*5B
$GPVTG,249.4,T,258.4,M,0.0,N,0.0,K,A*23
$GPRMC,235852.00,A,4002.483823,N,07618.477488,W,0.0,249.4,191120,9.0,W,A*3E
$PCPTI,Car 06,235852,235852*04

I see. Most likely the issue is that Traccar appended current date to the device time.

Should I roll back? Do you want to see more logs?

I don't think it's something new. It always worked like this.

I wonder why it just started to display though because we've been using traccar for years.

Roll backed just to test something and still doing it. So I have NO idea ... is there anything I can do to stop/fix this?

There an option to override time and always use server time.

Used override and it seems to be working well...Thanks

 <entry key='time.override'>serverTime</entry>