Hi!
I have beed feeding FR24 for data since 14th aug last year with a 100% uptime until yesterday with a Raspberry Pi and a dvbt dongle. What happend yesterday was that I performed a "apt-get upgrade" because that there was some software that needed to be upgraded.
After the upgrade the fr24feed was upgraded and worked good for a couple of hours. 6 hrs later my feed went offline. I rebooted my feed (Raspberry Pi) and the feed went online again. But just for a couple of minutes until it went offline again. I restarted the fr24feed service and after a few minutes it went back online and a couple of minutes later offline after uploading some hits and planes.
If I don't restart the service it sometimes go back online again after 10-20 minutes and offline again after a couple of minutes.
I havn't changed anything in the configuration. The only thing is the upgrade. I can't find the problem with the Global timeout exceeded and the feed going offline.
In the log file i found this:
fr24feed.ini
Current fr24feed.txt
I have beed feeding FR24 for data since 14th aug last year with a 100% uptime until yesterday with a Raspberry Pi and a dvbt dongle. What happend yesterday was that I performed a "apt-get upgrade" because that there was some software that needed to be upgraded.
After the upgrade the fr24feed was upgraded and worked good for a couple of hours. 6 hrs later my feed went offline. I rebooted my feed (Raspberry Pi) and the feed went online again. But just for a couple of minutes until it went offline again. I restarted the fr24feed service and after a few minutes it went back online and a couple of minutes later offline after uploading some hits and planes.
If I don't restart the service it sometimes go back online again after 10-20 minutes and offline again after a couple of minutes.
I havn't changed anything in the configuration. The only thing is the upgrade. I can't find the problem with the Global timeout exceeded and the feed going offline.
In the log file i found this:
Code:
2016-04-27 12:34:12 | [reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting
2016-04-27 12:34:12 | [reader][i]Connection terminated
2016-04-27 12:34:12 | [main][i]Terminating child process 4163 with SIGETERM
2016-04-27 12:34:18 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090 --raw)
2016-04-27 12:34:18 | [reader][i]Connected to the receiver, configuring
2016-04-27 12:34:18 | [reader][i]Configured, processing messagesCode:
receiver="dvbt"
fr24key="XXXXXXXXXXX"
path="/usr/lib/fr24/dump1090"
bs="yes"
raw="yes"
logmode="2"
windowmode="0"
mpx="no"
mlat="no"
mlat-without-gps="no"Code:
ac_map_size="3072"
build_arch="armv7l"
build_flavour="generic"
build_os="Linux"
build_revision="HEAD-d11ca48.git"
build_timetamp="Mar 4 2016 15:21:10"
build_version="1.0.18-5"
cfg_baudrate=""
cfg_bs="yes"
cfg_host=""
cfg_mpx="no"
cfg_path="/usr/lib/fr24/dump1090"
cfg_raw="yes"
cfg_receiver="dvbt"
cfg_windowmode="0"
d11_map_size="0"
feed_alias="T-ESMS12"
feed_configured_mode="UDP"
feed_current_mode="UDP"
feed_current_server="83.140.21.112"
feed_last_ac_sent_num="0"
feed_last_ac_sent_time="1461751987"
feed_last_attempt_time="1461749431"
feed_last_config_attempt="1461749431"
feed_last_config_info=""
feed_last_config_result="success"
feed_last_connected_time="1461749431"
feed_num_ac_tracked="1"
feed_status="connected"
feed_status_message=""
fr24key="XXXXXXXXXXXXX"
gps_tods="0"
last_json_utc="1461753044"
last_rx_connect_status="OK"
last_rx_connect_time="1461752637"
last_rx_connect_time_s="2016-04-27 10:23:57"
last_rx_global_timeout="1461752631"
local_tods="36814"
msg_ring_full="0"
msg_ring_length="0"
num_global_timeouts="3"
num_messages="74"
num_resyncs="0"
offline-mode="no"
rx_connected="1"
shutdown="no"
time_update_utc="1461753064"
time_update_utc_s="2016-04-27 10:31:04"
timing_is_valid="1"
timing_last_drift="-0.0020"
timing_last_offset="-0.0005"
timing_last_result="success"
timing_source="NTP"
timing_time_last_attempt="1461753056"
timing_time_last_success="1461753056"
timing_time_since_last_success="604"