website saying "Offline" but local page and systemd status saying all is ok.

[RunnerFL]

I'm hoping someone can help me out here. I just setup my Raspberry Pi 3 to share data with flightradar24.com and at first everything seemed fine. However If I go to the "My Sharing Data" section of my account info I show "offline". If I go to the pi on port 8754 it shows that I'm connected and flat is running. Also, running "service fr24feed status" shows the service active.

Restarting the service on my pi brings me back "online" in "My Sharing Data", for a little while at least.

Any suggestions?

I saw no other threads on my exact issue but if someone can point me to one that has this issue and a resolution I'd appreciate it.

[abcd567]

What OS image have you installed?
Pi24, or Raspbian, or Piaware or something else?

[RunnerFL]

What OS image have you installed?
Pi24, or Raspbian, or something else?

I installed using the Pi24 image I downloaded from here.

[abcd567]

I installed using the Pi24 image I downloaded from here.

Did you install any other software like dump1090 or modesDeco2?

[RunnerFL]

Did you install any other software like dump1090 or modesDeco2?

No, I only dd'd the image to my sd card booted up and used the link on the "Build your own ADS-B receiver – Pi24" to register it. Nothing else.

Checking the "My Sharing Data" screen a few times today I see it flapping between online and offline.

[abcd567]

Please check pages
(1) ip-of-pi:8754/settings.html
(2) ip-of-pi:8754
Compare with following screenshots. Do you notice anything different?

Screenshot from 2017-11-21 11-19-54.png


Screenshot from 2017-11-21 11-26-55.png

[RunnerFL]

Please check pages
(1) ip-of-pi:8754/settings.html
(2) ip-of-pi:8754
Compare with following screenshots. Do you notice anything different?

[ATTACH=CONFIG]8964[/ATTACH]


[ATTACH=CONFIG]8965[/ATTACH]

The settings.html differences on mine are:

"process arguments" is blank
"RAW data" is "YES"
"Decoded Data" is "YES"
"Logfile Mode" is "Disabled"
"Log file location" is blank

The only differences on the "Feeder/Decoder" page are the "aircraft tracked" and "aircraft uploaded" values.

[abcd567]

1. The settings seem OK for feeding data to FR24.
   The problem may be in connection to FR24. You have to enable log to find problems.
   First change
   "Logfile Mode" to "keep upto 48 hrs..."
   "Log file location" to /var/log/
   After making changes, click "Save" and "Restart" buttons at bottom-right of settings page.
   
   Wait for 10 minutes for log to build-up, then SSH to Pi, and give following command to check the log:
   

   cat /var/log/fr24feed.log

2. If "process arguments" is blank, you wont see a map with planes at ip-of-pi:8080 (try it).
   Add --net in the process argument, and you will see the map at ip-of-pi:8080 (try it after adding --net)
   NOTE: After adding --net, click "Save" and "Restart" buttons at bottom-right of settings page.
   
   
3. "RAW data" is "YES", "Decoded Data" is "YES" is not required. better change these to NO

[RunnerFL]

ok, changes made and restarted. I'll let you know if it makes a difference.

Thanks!

[abcd567]

The only differences on the "Feeder/Decoder" page are the "aircraft tracked" and "aircraft uploaded" values.

Do you see "N/A" for any of these two values, or see some numbers?

[RunnerFL]

I'm seeing a lot of what appear to be missed pings.

2017-11-21 17:46:38 | [mlat][i]Pinging the server
2017-11-21 17:46:38 | [mlat][i]Stats 17/0
2017-11-21 17:46:48 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:46:58 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:46:58 | [mlat][i]Pinging the server
2017-11-21 17:46:58 | [mlat][i]Stats 17/0
2017-11-21 17:47:01 | [feed][n]ping 13
2017-11-21 17:47:02 | [feed][n]syncing stream result: 1
2017-11-21 17:47:08 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:47:18 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:47:18 | [mlat][i]Pinging the server
2017-11-21 17:47:18 | [mlat][i]Stats 17/0
2017-11-21 17:47:28 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:47:31 | [feed][n]ping 14
2017-11-21 17:47:32 | [feed][n]syncing stream result: 1
2017-11-21 17:47:38 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:47:38 | [mlat][i]Pinging the server
2017-11-21 17:47:38 | [mlat][i]Stats 17/0
2017-11-21 17:47:48 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:47:58 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:47:58 | [mlat][i]Pinging the server
2017-11-21 17:47:59 | [mlat][i]Stats 17/0
2017-11-21 17:48:01 | [feed][n]ping 15
2017-11-21 17:48:02 | [feed][n]syncing stream result: 1
2017-11-21 17:48:08 | [mlat][i]No ADS-B time reference available (0/0)

[RunnerFL]

Do you see "N/A" for any of these two values, or see some numbers?

I see numbers, small numbers but numbers none the less.

[RunnerFL]

And I just saw this before "My Data Sharing" changed to "offline".

2017-11-21 17:50:38 | [mlat][i]Pinging the server
2017-11-21 17:50:38 | [mlat][i]Stats 17/0
2017-11-21 17:50:48 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:50:50 | [reader][w]Global timeout exceeded, 185 msgs, 0 resyncs, reconnecting
2017-11-21 17:50:50 | [reader][i]Connection terminated
2017-11-21 17:50:50 | [main][i]Terminating child process 2971 with SIGTERM
2017-11-21 17:50:56 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --net --raw --mlat)
2017-11-21 17:50:56 | [reader][i]Connected to the receiver, configuring
2017-11-21 17:50:56 | [reader][i]Configured, processing messages
2017-11-21 17:50:58 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:50:58 | [mlat][i]Pinging the server
2017-11-21 17:50:58 | [mlat][i]Stats 17/0
2017-11-21 17:51:01 | [feed][n]ping 21
2017-11-21 17:51:02 | [feed][n]syncing stream result: 1
2017-11-21 17:51:08 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-21 17:51:18 | [mlat][i]No ADS-B time reference available (0/0)

[RunnerFL]

I seem to have gotten rid of "No ADS-B time reference available" by running "sudo fr24feed --reconfigure --fr24key=YOUR SHARING KEY", which I found in another thread. "My Sharing Data" is only showing me as "offline" now though.


2017-11-21 18:02:11 | [httpd][i]Server started, listening on 0.0.0.0:8754
2017-11-21 18:02:11 | [master][i]Starting processing thread
2017-11-21 18:02:11 | [main][i]Reader thread started
2017-11-21 18:02:11 | [reader][i]Initializing reader
2017-11-21 18:02:11 | [main][i]MLAT data feed started
2017-11-21 18:02:11 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --net --raw --mlat)
2017-11-21 18:02:11 | [mlat][i]Waiting for MLAT configuration
2017-11-21 18:02:11 | [reader][i]Connected to the receiver, configuring
2017-11-21 18:02:11 | [reader][i]Configured, processing messages
2017-11-21 18:02:12 | [time][i]Synchronizing time via NTP
2017-11-21 18:02:28 | [time][i]Time synchronized correctly, offset +0.0000 seconds
2017-11-21 18:02:28 | [main][i]Feed Network client started
2017-11-21 18:02:28 | [feed][i]Downloading configuration
2017-11-21 18:02:29 | [feed][c]Interval: 5s
2017-11-21 18:02:29 | [feed][c]Latitude: 26.6214
2017-11-21 18:02:29 | [feed][c]Longitude: -80.1065
2017-11-21 18:02:29 | [feed][c]GND: YES
2017-11-21 18:02:29 | [feed][c]NonADSB: YES
2017-11-21 18:02:29 | [feed][c]Timestamps: optional
2017-11-21 18:02:29 | [feed][c]Max range AIR: 350.0nm
2017-11-21 18:02:29 | [feed][c]Max range GND: 100.0nm
2017-11-21 18:02:29 | [feed][i]defined 5 servers
2017-11-21 18:02:29 | [feed][n]KPBI10@83.140.21.68:8099/UDP
2017-11-21 18:02:29 | [feed][n]connecting
2017-11-21 18:02:29 | [stats][i]Stats thread started
2017-11-21 18:02:29 | [feed][n]connected via UDP (fd 8)
2017-11-21 18:02:29 | [feed][n]working
2017-11-21 18:02:59 | [feed][n]ping 1
2017-11-21 18:03:00 | [feed][n]syncing stream result: 1
2017-11-21 18:03:29 | [feed][n]ping 2
2017-11-21 18:03:30 | [feed][n]syncing stream result: 1
2017-11-21 18:03:59 | [feed][n]ping 3
2017-11-21 18:04:00 | [feed][n]syncing stream result: 1
2017-11-21 18:04:29 | [feed][n]ping 4
2017-11-21 18:04:30 | [feed][n]syncing stream result: 1
2017-11-21 18:04:59 | [feed][n]ping 5
2017-11-21 18:05:00 | [feed][n]syncing stream result: 1
2017-11-21 18:05:29 | [feed][n]ping 6
2017-11-21 18:05:30 | [feed][n]syncing stream result: 1
2017-11-21 18:05:59 | [feed][n]ping 7
2017-11-21 18:06:00 | [feed][n]syncing stream result: 1
2017-11-21 18:06:29 | [feed][n]ping 8
2017-11-21 18:06:30 | [feed][n]syncing stream result: 1
2017-11-21 18:06:59 | [feed][n]ping 9
2017-11-21 18:07:00 | [feed][n]syncing stream result: 1
2017-11-21 18:07:29 | [feed][n]ping 10
2017-11-21 18:07:30 | [feed][n]syncing stream result: 1
2017-11-21 18:07:59 | [feed][n]ping 11
2017-11-21 18:08:00 | [feed][n]syncing stream result: 1
2017-11-21 18:08:29 | [feed][n]ping 12
2017-11-21 18:08:30 | [feed][n]syncing stream result: 1

[Oblivian]

There is no trackable aircraft within range/uploaded. So the server sends a kill command to restart it.

Pings are keep alive. Too many means no data received

Sent from my XT1092 using Tapatalk