I started to get this messages in log file, don't have an idea what it is
It says autotrack, but can't figure what is and why is there.
This is a sample test server that had no devices currently reporting to it when this started.
2025-02-21 04:35:35 INFO: [Tf27d8c5b] connected
2025-02-21 04:35:35 INFO: [Tf27d8c5b: autotrack < 127.0.0.1] d8efdf35a44a480b1e86de5aa24839e43a7a057202e4bbb80d6e9c33adcb128f1268f7a024a8c4c80536f2c7af20148a1e252c2b68088ecef781dc7c5f8fcaadc6e156a5c79de1a951f6628b23ff90e5b5c5bfbcf1b0ffd686413aeeaed43e40c90bef3667ffa5a10b59c4546958e8683602fbfca57dc7ecbad00c90827537d7f077054538626115843cfa6d31e4d36c2c7b7c1e994e6f363bfc3b76611ec0dcbabaa0707713933bb56f3f739d4b45dfb23ddf0b38eeb2de377befd14310a9807f547f3df93bd4a99bc595505c3a712fd9aa1882f83f18054cffd8db9c165ba9e292cbddc08e898656a3c937b10ec215f03354eea66ec099f112dc559c6435d3b9ea80a4c76f69763324d3dda834e3086010053e7e081ecac1d519abac97fb4d0174ab3f290a57743400b43800526ed47155d78c898523a1ec348fe70989d592517eb662dc54cc49c2ca9f43e569152e6853e90a3bc91b40f19936a69878e665def050c758d41f0f131ae30402cc2278dbb29ac121243ae854cf8c6eb0ef5f41f8f97bff205144bc6c24f4c9b46b7ed2f483cd57b64204fa659e4996331cdc8e351f801279fd0af3effb4632cafac2eb956b7202e26da89dcbc0c915fd555e0aae8e2bb62e6ee7833461b8ae1cafad9c02562f62b076d51cd6e7b7bccd0ac9a4b5
2025-02-21 04:35:35 WARN: [Tf27d8c5b] error - Adjusted frame length exceeds 1024: 18515 - discarded - TooLongFrameException (... < WrapperInboundHandler:56 < ... < StandardLoggingHandler:62 < ... < NetworkMessageHandler:36 < ...)
2025-02-21 04:35:35 INFO: [Tf27d8c5b] disconnected
If you're not using that port, then it's probably just noise from the internet.
Server is behind a firewall and most ports are closed.
This must be then from the local network, but there's nothing reporting to it.
Perhaps a chinese tvbox fiddling around to see if there's something worth spying...
I just found out that there's plenty stuff roaming around and probing ports then sadly traccar answers when an ID is coincidental, so "stuff" starts trial and error to see how to communicate with what was found.
Some "stuff" sent ID/s that coincided with some of my devices and finally found their protocol, so traccar stopped talking with MY devices and kept talking with "stuff" so some of my devices appeared nowhere near their real location while some others just seemd frozen because "stuff" sent wrong data and traccar never went back to speak with my trackers instead.
This is a HUGE security flaw and to much of an issue to ignore.
I had to take several diferent paliative measures, but if in the future this can't be properly addressed, I think traccar days are numbered.
Do you have some suggestions?
I started to get this messages in log file, don't have an idea what it is
It says autotrack, but can't figure what is and why is there.
This is a sample test server that had no devices currently reporting to it when this started.