I am using a bunch of generic TK103's and Telcel SIM cards in Mexico.
I am experiencing a big problem which only occurs when my SIM cards run out of credit... The phone operator (Telcel) keeps the SIM alive to a certain extent and tried to intercept web traffic and direct phone users to a page where they can top up their credit. Because this is not a "hard cut-off" of internet traffic is seems that at least some form of a request is able to reach my Traccar server.
I have updates sent every 20 seconds from my devices and approximately once every 5 minutes or so, enough data seems to be able to sneak through and I do receive an update with the location even though the SIM card is not paid for.
The problem is that is seems that every 20s the device is still able to reach my server to some extent, but with the data not sent correctly, Traccar keeps this momentary connection as ESTABLISHED (seemingly forever)... The problem is that just 20 seconds later, an additional connection will be made by the device and this is handled as another new connection. Eventually my serer ends up with over 3000 established connections and eventually Traccar will become unresponsive.
Is there any way to get Traccar to terminate/close the connections if it has received less than 20 bytes of data in the last 60 seconds??? That would be enough to clear out this problem causing connections...
The data hitting my server (captured by tshark)...
Capturing on 'eth0'
1 0.000000000 200.68.136.192 → 172.30.3.87 TCP 54 51768 → 5001 [RST, ACK] Seq=1 Ack=1 Win=10880 Len=0
2 0.036028571 200.68.137.163 → 172.30.3.87 TCP 54 41136 → 5001 [RST, ACK] Seq=1 Ack=1 Win=10880 Len=0
3 1.738283646 200.68.137.134 → 172.30.3.87 TCP 78 46117 → 5001 [SYN] Seq=0 Win=8160 Len=0 MSS=1360 WS=1 SACK_PERM=1 TSval=12474 TSecr=0
4 1.738314606 172.30.3.87 → 200.68.137.134 TCP 74 5001 → 46117 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=8961 SACK_PERM=1 TSval=6544034 TSecr=12474 WS=128
5 2.092865218 200.68.136.174 → 172.30.3.87 TCP 152 19583 → 5001 [PSH, ACK] Seq=1 Ack=1 Win=10880 Len=86 TSval=14055 TSecr=6539144
6 2.092891744 172.30.3.87 → 200.68.136.174 TCP 66 5001 → 19583 [ACK] Seq=1 Ack=87 Win=210 Len=0 TSval=6544123 TSecr=14055
7 2.238993869 200.68.137.134 → 172.30.3.87 TCP 66 46117 → 5001 [ACK] Seq=1 Ack=1 Win=8160 Len=0 TSval=12582 TSecr=6544034
8 2.360965520 200.68.137.129 → 172.30.3.87 TCP 161 25096 → 5001 [PSH, ACK] Seq=1 Ack=1 Win=10880 Len=95 TSval=28806 TSecr=6542440
9 2.361009510 172.30.3.87 → 200.68.137.129 TCP 66 5001 → 25096 [ACK] Seq=1 Ack=96 Win=210 Len=0 TSval=6544190 TSecr=28806
10 3.178387432 200.68.136.192 → 172.30.3.87 TCP 78 50314 → 5001 [SYN] Seq=0 Win=10880 Len=0 MSS=1360 WS=1 SACK_PERM=1 TSval=39636 TSecr=0
11 3.178412949 172.30.3.87 → 200.68.136.192 TCP 74 5001 → 50314 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=8961 SACK_PERM=1 TSval=6544395 TSecr=39636 WS=128
12 4.178403621 172.30.3.87 → 200.68.136.192 TCP 74 [TCP Retransmission] 5001 → 50314 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=8961 SACK_PERM=1 TSval=6544645 TSecr=39636 WS=128
13 4.456412858 200.68.136.192 → 172.30.3.87 TCP 66 50314 → 5001 [ACK] Seq=1 Ack=1 Win=10880 Len=0 TSval=39903 TSecr=6544395
14 4.517413205 200.68.136.192 → 172.30.3.87 TCP 92 50314 → 5001 [PSH, ACK] Seq=1 Ack=1 Win=10880 Len=26 TSval=39904 TSecr=6544395
15 4.517458903 172.30.3.87 → 200.68.136.192 TCP 66 5001 → 50314 [ACK] Seq=1 Ack=27 Win=26880 Len=0 TSval=6544729 TSecr=39904
16 4.518304383 172.30.3.87 → 200.68.136.192 TCP 70 5001 → 50314 [PSH, ACK] Seq=1 Ack=27 Win=26880 Len=4 TSval=6544729 TSecr=39904
17 4.568757180 200.68.136.153 → 172.30.3.87 TCP 78 28171 → 5001 [SYN] Seq=0 Win=8160 Len=0 MSS=1360 WS=1 SACK_PERM=1 TSval=10330 TSecr=0
18 4.568775242 172.30.3.87 → 200.68.136.153 TCP 74 5001 → 28171 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=8961 SACK_PERM=1 TSval=6544742 TSecr=10330 WS=128
19 4.898037962 200.68.136.192 → 172.30.3.87 TCP 66 [TCP Dup ACK 13#1] 50314 → 5001 [ACK] Seq=27 Ack=1 Win=10880 Len=0 TSval=39968 TSecr=6544645
20 5.189986914 200.68.136.153 → 172.30.3.87 TCP 66 28171 → 5001 [ACK] Seq=1 Ack=1 Win=8160 Len=0 TSval=10437 TSecr=6544742
21 7.338625362 200.68.137.129 → 172.30.3.87 TCP 54 25096 → 5001 [RST, ACK] Seq=96 Ack=1 Win=10880 Len=0
22 7.454400783 172.30.3.87 → 200.68.136.192 TCP 70 [TCP Retransmission] 5001 → 50314 [PSH, ACK] Seq=1 Ack=27 Win=26880 Len=4 TSval=6545464 TSecr=39968
23 8.174570584 200.68.136.192 → 172.30.3.87 TCP 66 50314 → 5001 [ACK] Seq=27 Ack=5 Win=10880 Len=0 TSval=40054 TSecr=6544729
24 8.257984295 200.68.136.192 → 172.30.3.87 TCP 66 [TCP Dup ACK 23#1] 50314 → 5001 [ACK] Seq=27 Ack=5 Win=10880 Len=0 TSval=40718 TSecr=6545464
25 12.275065418 200.68.136.174 → 172.30.3.87 TCP 158 19583 → 5001 [PSH, ACK] Seq=87 Ack=1 Win=10880 Len=92 TSval=15570 TSecr=6544123
26 12.275086456 172.30.3.87 → 200.68.136.174 TCP 66 5001 → 19583 [ACK] Seq=1 Ack=179 Win=210 Len=0 TSval=6546669 TSecr=15570
27 12.370898326 200.68.136.174 → 172.30.3.87 TCP 158 [TCP Spurious Retransmission] 19583 → 5001 [PSH, ACK] Seq=87 Ack=1 Win=10880 Len=92 TSval=15973 TSecr=6544123
28 12.370911509 172.30.3.87 → 200.68.136.174 TCP 78 [TCP Dup ACK 26#1] 5001 → 19583 [ACK] Seq=1 Ack=179 Win=210 Len=0 TSval=6546693 TSecr=15973 SLE=87 SRE=179
29 14.094036080 200.68.136.174 → 172.30.3.87 TCP 158 19583 → 5001 [PSH, ACK] Seq=179 Ack=1 Win=10880 Len=92 TSval=16654 TSecr=6546693
30 14.094062653 172.30.3.87 → 200.68.136.174 TCP 66 5001 → 19583 [ACK] Seq=1 Ack=271 Win=210 Len=0 TSval=6547123 TSecr=16654
31 14.955118447 200.68.137.231 → 172.30.3.87 TCP 152 22640 → 5001 [PSH, ACK] Seq=1 Ack=1 Win=8160 Len=86 TSval=269918 TSecr=6542324
32 14.955144002 172.30.3.87 → 200.68.137.231 TCP 66 5001 → 22640 [ACK] Seq=1 Ack=87 Win=210 Len=0 TSval=6547339 TSecr=269918
33 15.053746502 200.68.136.192 → 172.30.3.87 TCP 156 50314 → 5001 [PSH, ACK] Seq=27 Ack=5 Win=10880 Len=90 TSval=42138 TSecr=6545464
34 15.090421807 172.30.3.87 → 200.68.136.192 TCP 66 5001 → 50314 [ACK] Seq=5 Ack=117 Win=26880 Len=0 TSval=6547373 TSecr=42138
35 17.095767752 200.68.136.201 → 172.30.3.87 TCP 152 28115 → 5001 [PSH, ACK] Seq=1 Ack=1 Win=10880 Len=86 TSval=265600 TSecr=6542924
36 17.095792803 172.30.3.87 → 200.68.136.201 TCP 66 5001 → 28115 [ACK] Seq=1 Ack=87 Win=210 Len=0 TSval=6547874 TSecr=265600
37 17.773247616 200.68.137.163 → 172.30.3.87 TCP 78 14006 → 5001 [SYN] Seq=0 Win=10880 Len=0 MSS=1360 WS=1 SACK_PERM=1 TSval=47922 TSecr=0
38 17.773276690 172.30.3.87 → 200.68.137.163 TCP 74 5001 → 14006 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=8961 SACK_PERM=1 TSval=6548043 TSecr=47922 WS=128
39 18.770461063 172.30.3.87 → 200.68.137.163 TCP 74 [TCP Retransmission] 5001 → 14006 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=8961 SACK_PERM=1 TSval=6548293 TSecr=47922 WS=128
40 18.933629931 200.68.137.163 → 172.30.3.87 TCP 66 14006 → 5001 [ACK] Seq=1 Ack=1 Win=10880 Len=0 TSval=48165 TSecr=6548043
41 19.010673344 200.68.137.163 → 172.30.3.87 TCP 92 14006 → 5001 [PSH, ACK] Seq=1 Ack=1 Win=10880 Len=26 TSval=48165 TSecr=6548043
42 19.010699037 172.30.3.87 → 200.68.137.163 TCP 66 5001 → 14006 [ACK] Seq=1 Ack=27 Win=26880 Len=0 TSval=6548353 TSecr=48165
43 19.011497015 172.30.3.87 → 200.68.137.163 TCP 70 5001 → 14006 [PSH, ACK] Seq=1 Ack=27 Win=26880 Len=4 TSval=6548353 TSecr=48165
44 19.116985273 200.68.136.174 → 172.30.3.87 TCP 163 19583 → 5001 [PSH, ACK] Seq=271 Ack=1 Win=10880 Len=97 TSval=17737 TSecr=6547123
45 19.116997835 172.30.3.87 → 200.68.136.174 TCP 66 5001 → 19583 [ACK] Seq=1 Ack=368 Win=210 Len=0 TSval=6548379 TSecr=17737
46 19.457980931 200.68.137.163 → 172.30.3.87 TCP 66 [TCP Dup ACK 40#1] 14006 → 5001 [ACK] Seq=27 Ack=1 Win=10880 Len=0 TSval=48247 TSecr=6548293
47 20.297245725 200.68.137.163 → 172.30.3.87 TCP 66 14006 → 5001 [ACK] Seq=27 Ack=5 Win=10880 Len=0 TSval=48324 TSecr=6548353
48 20.739710335 200.68.137.129 → 172.30.3.87 TCP 78 36825 → 5001 [SYN] Seq=0 Win=10880 Len=0 MSS=1360 WS=1 SACK_PERM=1 TSval=32846 TSecr=0
49 20.739740510 172.30.3.87 → 200.68.137.129 TCP 74 5001 → 36825 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=8961 SACK_PERM=1 TSval=6548785 TSecr=32846 WS=128
Tracker-Server.log while some trackers are paid, some are un-paid
2020-03-12 08:44:40 INFO: [b7d6fa12] connected
2020-03-12 08:44:41 WARN: [c3c2eb69] error - Connection reset by peer - IOException (...)
2020-03-12 08:44:41 INFO: [c3c2eb69] disconnected
2020-03-12 08:44:42 INFO: [b08654e2: gps103 < 200.68.137.216] HEX: 696d65693a3836343839333033303431393534362c747261636b65722c3230303331323136343434302c2c462c3038343434312e30302c412c323034302e39363139372c4e2c30383730322e38373135342c572c$
2020-03-12 08:44:42 INFO: Position filtered by Distance filters from device: 864893030419546
2020-03-12 08:44:44 INFO: [4b9fbb81] connected
2020-03-12 08:44:51 INFO: [8216379a] connected
2020-03-12 08:44:51 INFO: [8216379a: gps103 < 200.68.136.153] HEX: 23232c696d65693a3836343839353033323836353732352c413b
2020-03-12 08:44:51 INFO: [8216379a: gps103 > 200.68.136.153] HEX: 4c4f4144
2020-03-12 08:44:52 INFO: [3745f131] connected
2020-03-12 08:44:52 INFO: [3745f131: t55 < 5.8.18.88] HEX: 0300002f2ae00000000000436f6f6b69653a206d737473686173683d41646d696e697374720d0a0100080003000000
2020-03-12 08:44:56 INFO: [8216379a: gps103 < 200.68.136.153] HEX: 696d65693a3836343839353033323836353732352c747261636b65722c2c2c4c2c2c2c316533372c2c363166632c2c2c3b
2020-03-12 08:44:56 INFO: Position filtered by Distance filters from device: 864895032865725
2020-03-12 08:44:57 INFO: [acf60869] connected
2020-03-12 08:44:58 INFO: [991b2dee: gps103 < 200.68.137.152] HEX: 696d65693a3836343839333033373633323930312c747261636b65722c3230303331323038343435362c2c462c3038343435362e30302c412c323033372e31323535382c4e2c30383730362e32343036392c572c$
2020-03-12 08:44:58 INFO: Position filtered by Distance filters from device: 864893037632901
2020-03-12 08:44:59 INFO: [01b3df92] connected
2020-03-12 08:45:00 INFO: [b08654e2: gps103 < 200.68.137.216] HEX: 3836343839333033303431393534363b
2020-03-12 08:45:00 INFO: [b08654e2: gps103 > 200.68.137.216] HEX: 4f4e
2020-03-12 08:45:02 INFO: [b08654e2: gps103 < 200.68.137.216] HEX: 696d65693a3836343839333033303431393534362c747261636b65722c3230303331323136343530302c2c462c3038343530312e30302c412c323034302e39363139372c4e2c30383730322e38373135
2020-03-12 08:45:02 INFO: [b08654e2: gps103 < 200.68.137.216] HEX: 342c572c2c3b
2020-03-12 08:45:02 INFO: Position filtered by Distance filters from device: 864893030419546
2020-03-12 08:45:03 INFO: [cf8bcfaa] connected
2020-03-12 08:45:04 INFO: [f19b02f1] connected
2020-03-12 08:45:04 INFO: [f19b02f1: gps103 < 200.68.137.184] HEX: 23232c696d65693a3836343138303033353933353837382c413b
2020-03-12 08:45:04 INFO: [f19b02f1: gps103 > 200.68.137.184] HEX: 4c4f4144
2020-03-12 08:45:06 INFO: [f19b02f1: gps103 < 200.68.137.184] HEX: 696d65693a3836343138303033353933353837382c747261636b65722c3230303331323135303231322c2c462c3037303230392e3030302c412c323033382e313435302c4e2c30383730332e343836312c572c30$
2020-03-12 08:45:06 INFO: Position filtered by Distance filters from device: 864180035935878
2020-03-12 08:45:10 INFO: [f22fce07] connected
2020-03-12 08:45:11 WARN: [f19b02f1] error - Connection reset by peer - IOException (...)
2020-03-12 08:45:11 INFO: [f19b02f1] disconnected
2020-03-12 08:45:14 INFO: [5a106d0a] connected
2020-03-12 08:45:14 INFO: [991b2dee: gps103 < 200.68.137.152] HEX: 3836343839333033373633323930313b
2020-03-12 08:45:14 INFO: [991b2dee: gps103 > 200.68.137.152] HEX: 4f4e
2020-03-12 08:45:16 WARN: [8216379a] error - Connection reset by peer - IOException (...)
2020-03-12 08:45:16 INFO: [8216379a] disconnected
2020-03-12 08:45:18 INFO: [991b2dee: gps103 < 200.68.137.152] HEX: 696d65693a3836343839333033373633323930312c747261636b65722c3230303331323038343531362c2c462c3038343531362e30302c412c323033372e31323535382c4e2c30383730362e32343036392c572c$
2020-03-12 08:45:18 INFO: Position filtered by Distance filters from device: 864893037632901
2020-03-12 08:45:21 INFO: [930e821f] connected
2020-03-12 08:45:21 INFO: [930e821f: gps103 < 200.68.136.153] HEX: 23232c696d65693a3836343839353033323836353732352c413b
2020-03-12 08:45:21 INFO: [930e821f: gps103 > 200.68.136.153] HEX: 4c4f4144
2020-03-12 08:45:22 INFO: [b08654e2: gps103 < 200.68.137.216] HEX: 696d65693a3836343839333033303431393534362c747261636b65722c3230303331323136343532302c2c462c3038343532312e30302c412c323034302e39363139372c4e2c30383730322e38373135342c572c$
2020-03-12 08:45:22 INFO: Position filtered by Distance filters from device: 864893030419546
2020-03-12 08:45:28 INFO: [e79d123a] connected
2020-03-12 08:45:29 INFO: [1463cba3] connected
2020-03-12 08:45:33 INFO: [738f1b7b] connected
2020-03-12 08:45:34 INFO: [7ea6fd63] connected
Tracker-Server.log pretty much at the moment the website became unresponsive
2020-03-12 11:47:22 INFO: [ff0ede0d: gps103 < 200.68.136.153] HEX: 23232c696d65693a3836343839353033323836353732352c413b
2020-03-12 11:47:22 INFO: [ff0ede0d: gps103 > 200.68.136.153] HEX: 4c4f4144
2020-03-12 11:47:29 INFO: [67a6da7e: gps103 < 200.68.137.162] HEX: 3836343839333033373633323930313b
2020-03-12 11:47:29 INFO: [67a6da7e: gps103 > 200.68.137.162] HEX: 4f4e
2020-03-12 11:47:29 INFO: [67a6da7e: gps103 < 200.68.137.162] HEX: 696d65693a3836343839333033373633323930312c747261636b65722c3230303331323131343732382c2c462c3131343732382e30302c412c323033372e31323731352c4e2c30383730362e32343134342c572c$
2020-03-12 11:47:29 INFO: Position filtered by Distance filters from device: 864893037632901
2020-03-12 11:47:29 INFO: [d65f3918] connected
2020-03-12 11:47:35 INFO: [5c9e7e9f: gps103 < 200.68.137.198] HEX: 696d65693a3836343839333033303431393534362c747261636b65722c3230303331323139343733332c2c462c3131343733342e30302c412c323034302e39363039332c4e2c30383730322e38373235
2020-03-12 11:47:35 INFO: [5c9e7e9f: gps103 < 200.68.137.198] HEX: 352c572c2c3b
2020-03-12 11:47:35 INFO: Position filtered by Distance filters from device: 864893030419546
2020-03-12 11:47:37 INFO: [d8525606] connected
2020-03-12 11:47:37 INFO: [579bd6fd] connected
2020-03-12 11:47:39 INFO: [ff0ede0d: gps103 < 200.68.136.153] HEX: 696d65693a3836343839353033323836353732352c747261636b65722c2c2c4c2c2c2c316533372c2c363166632c2c2c3b
2020-03-12 11:47:39 INFO: Position filtered by Distance filters from device: 864895032865725
2020-03-12 11:47:40 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:41 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:41 WARN: [5ca23446] error - Connection reset by peer - IOException (...)
2020-03-12 11:47:41 INFO: [5ca23446] disconnected
2020-03-12 11:47:42 INFO: [447d2463] connected
2020-03-12 11:47:42 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:43 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:44 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:45 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:46 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:47 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:48 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:49 INFO: [67a6da7e: gps103 < 200.68.137.162] HEX: 696d65693a3836343839333033373633323930312c747261636b65722c3230303331323131343734382c2c462c3131343734382e30302c412c323033372e31323731352c4e2c30383730362e32343134342c572c$
2020-03-12 11:47:49 INFO: Position filtered by Distance filters from device: 864893037632901
2020-03-12 11:47:49 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:50 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:51 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:52 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:53 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:54 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:55 INFO: [5c9e7e9f: gps103 < 200.68.137.198] HEX: 696d65693a3836343839333033303431393534362c747261636b65722c3230303331323139343735332c2c462c3131343735342e30302c412c323034302e39363032362c4e2c30383730322e38373333332c572c$
2020-03-12 11:47:55 INFO: Position filtered by Distance filters from device: 864893030419546
2020-03-12 11:47:55 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:56 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:57 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:58 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2020-03-12 11:47:59 WARN: [ff0ede0d] error - Connection reset by peer - IOException (...)
2020-03-12 11:47:59 INFO: [ff0ede0d] disconnected
A few notes...
- I can't pay my SIM card automatically, monthly to avoid this
- I have tried setting gprsmode123456 1 to set the trackers to UDP, but they don't seem to support this
- I have read other threads about this IOException and it seems to be an issue with many trackers, I only have a few and the main issue here is these useless ESTABLISHED connections never timing out and being dropped
I am using a bunch of generic TK103's and Telcel SIM cards in Mexico.
I am experiencing a big problem which only occurs when my SIM cards run out of credit... The phone operator (Telcel) keeps the SIM alive to a certain extent and tried to intercept web traffic and direct phone users to a page where they can top up their credit. Because this is not a "hard cut-off" of internet traffic is seems that at least some form of a request is able to reach my Traccar server.
I have updates sent every 20 seconds from my devices and approximately once every 5 minutes or so, enough data seems to be able to sneak through and I do receive an update with the location even though the SIM card is not paid for.
The problem is that is seems that every 20s the device is still able to reach my server to some extent, but with the data not sent correctly, Traccar keeps this momentary connection as ESTABLISHED (seemingly forever)... The problem is that just 20 seconds later, an additional connection will be made by the device and this is handled as another new connection. Eventually my serer ends up with over 3000 established connections and eventually Traccar will become unresponsive.
Is there any way to get Traccar to terminate/close the connections if it has received less than 20 bytes of data in the last 60 seconds??? That would be enough to clear out this problem causing connections...
The data hitting my server (captured by tshark)...
Tracker-Server.log while some trackers are paid, some are un-paid
Tracker-Server.log pretty much at the moment the website became unresponsive
A few notes...