Strange timestamp from FLightRadar 2032-07-14 12:40:38 logs

[rvt]

Hey,

since a couple of weeks I think FR24 started to behave incorrectly so in result I started to see what was going on, mind you... my setup has been working without issues at all.

My Setup is a PI3 running everything in docker.

When flightradar startsup I get this:

2032-07-14 12:50:13 | [main][i]FR24 Feeder/Decoder
2032-07-14 12:50:48 | [main][i]Version: 1.0.27-2/generic
2032-07-14 12:52:05 | [main][i]Built on Mar 25 2021 14:17:10 (HEAD-76766f9.git/Linux/static_armel)
2032-07-14 12:39:50 | [main][i]Running on: debian10
2032-07-14 12:40:23 | [main][i]Local IP(s): 172.22.0.7
...
...
1964-10-24 12:16:29 | [reader][w]Global timeout exceeded, 17 msgs, 0 resyncs, reconnecting
2033-03-11 18:21:30 | [reader][i]Connection terminated
1964-10-24 12:16:07 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://rtlsdr_dump1090:30002)
1964-10-24 12:16:17 | [reader][i]Connected to the receiver, configuring
1964-10-24 12:16:48 | [reader][i]Configured, processing messages
1964-10-24 12:16:28 | [reader][w]Global timeout exceeded, 1 msgs, 0 resyncs, reconnecting
1964-10-24 12:16:37 | [reader][i]Connection terminated
1964-10-24 12:16:07 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://rtlsdr_dump1090:30002)
1964-10-24 12:16:55 | [reader][i]Connected to the receiver, configuring
1964-10-24 12:16:48 | [reader][i]Configured, processing messages
1964-10-24 12:16:28 | [reader][w]Global timeout exceeded, 34 msgs, 0 resyncs, reconnecting
1964-10-24 12:16:38 | [reader][i]Connection terminated
2033-03-11 18:21:40 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://rtlsdr_dump1090:30002)
1964-10-24 12:16:55 | [reader][i]Connected to the receiver, configuring
1964-10-24 12:16:48 | [reader][i]Configured, processing messages
1964-10-24 12:16:28 | [reader][w]Global timeout exceeded, 6 msgs, 0 resyncs, reconnecting
1964-10-24 12:16:38 | [reader][i]Connection terminated
1964-10-24 12:17:25 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://rtlsdr_dump1090:30002)
1964-10-24 12:16:16 | [reader][i]Connected to the receiver, configuring

When i log into the docker container I correctly see :

root@1fcc566c467f:/# date
Wed Apr 14 10:47:40 UTC 2021

My fr24 config looks like this:
root@1fcc566c467f:/etc# cat fr24feed.ini

receiver="sbs1tcp"
receiver="avr-tcp"
beasthost="rtlsdr_dump1090"
fr24key="XXXXXXXXXX"
host="rtlsdr_dump1090:30002"
bs="no"
raw="no"
logmode="1"
logpath="/var/log/fr24feed"
mpx="no"
mlat="yes"
mlat-without-gps="yes"

I have been playing around with the receiver type but so far not a lot of luck on that.

Dump1090 is compiled from

https://github.com/flightaware/dump1090

and I am using

V5.0

(upgraded, but V4 also did not work)
I am feeding flightaware and opensky, adsbhub without issues.

Question:
1) Where does FR24 get the time from? For sure not from the time of the unix machine, does it try to connect to dump1090?

[Oblivian]

If you're already feeding others. And adding fr24 DO NOT CHANGE THE FEEDER OPTION TO DVBT
from looking there I see issues

2 receiver's specified
Multiple hosts specified
AVr-tco is fussy.
specified source address that is doubtful fr24 recognises as valid ip from fdqn
Its raspbian version on full debian? So bound to have issues knowing how they work.
The full linux version is available. But well behind

Beast-tcp
127.0.0.1:30005