Traccar on AWS EC2 instance Status=1/Failure issue

Nightwolve4 years ago

yes, that is indeed the correct IMEI

Slawek4 years ago

and did you add device with this ID ?

Nightwolve4 years ago

I did add the device within Traccar on this ID. I even copied this IMEI again and added this in the Identifier field when you add another device

Nightwolve4 years ago

It appears the device is registered after removing and adding it again:

    37  2021-02-04 15:38:09  INFO: [07dd1886: eelink > 188.188.127.92] HEX: 67670300020013
    38  2021-02-04 15:39:25  INFO: user: 2, action: remove, object: device, id: 1
    39  2021-02-04 15:39:30  INFO: user: 2, action: create, object: device, id: 2
    40  2021-02-04 15:39:30  INFO: user: 2, action: link, owner: user, id: 2, property: device, id: 2
    41  2021-02-04 15:41:11  INFO: [07dd1886: eelink < 188.188.127.92] HEX: 67670300040014046b
    42  2021-02-04 15:41:11  INFO: [07dd1886: eelink > 188.188.127.92] HEX: 67670300020014
    43  2021-02-04 15:44:13  INFO: [07dd1886: eelink < 188.188.127.92] HEX: 67670300040015046b
    44  2021-02-04 15:44:13  INFO: [07dd1886: eelink > 188.188.127.92] HEX: 67670300020015

values are just still in HEX so perhaps a wrong port?

Anton Tananaev4 years ago

You have to register device before it connects to the server.

Nightwolve4 years ago

Anton, I forgot to add the IMEI after I let it send to the server, now I added it again but the data seems to be in HEX. Device is indeed registered on the Traccar web application under the add device section with the IMEI in the Identifier field.

Anton Tananaev4 years ago

Now you have to reconnect the device.

Nightwolve4 years ago

It appears a device reboot fixed the issue, device appears online with location on the server but i get following warning:

   97  2021-02-04 16:21:29  WARN: Failed to store position - Data truncation: Incorrect datetime value: '1970-01-01 00:00:00.0' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:452 < DataManager:458 < DefaultDataHandler:40 < ...)
    98  2021-02-04 16:21:29  INFO: [9311791d] id: 865284042934723, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
    99  2021-02-04 16:21:52  INFO: [9311791d: eelink < 188.189.127.4] HEX: 67671200430003601c1f1e0305779c7d009cae06002d000000000700ce001404ed000065942c046b10bb01f000000000000002e502d6000000000000000000000000000000000000
   100  2021-02-04 16:21:52  INFO: [9311791d: eelink > 188.189.127.4] HEX: 67671200020003
   101  2021-02-04 16:21:52  INFO: [9311791d] id: 865284042934723, time: 2021-02-04 16:21:50, lat: 50.95829, lon: 5.70454, course: 0.0
root@ip-172-31-0-242:/opt/traccar/logs#     96  2021-02-04 16:21:29  INFO: [9311791d: eelink > 188.189.127.4] HEX: 67671500020001
    99  2021-02-04 16:21:52  INFO: [9311791d: eelink < 188.189.127.4] HEX: 67671200430003601c1f1e0305779c7d009cae06002d000000000700ce001404ed000065942c046b10bb01f000000000000002e502d6000000000000000000000000000000000000
   100  2021-02-04 16:21:52  INFO: [9311791d: eelink > 188.189.127.4] HEX: 67671200020003
   101  2021-02-04 16:21:52  INFO: [9311791d] id: 865284042934723, time: 2021-02-04 16:21:50, lat: 50.95829, lon: 5.70454, course: 0.0

Something seems to be incorrect with the time for data base storing?

Anton Tananaev4 years ago

You can safely ignore it. It just means that you received some data without location info first, but it's working after that.