How do know its really working?

[Vlasta]

Just plugged in new DVB-T stick. Stastis page says the following - am I really running or not? What are the errors?

FR24 Link:	Connected via UDP
FR24 Radar Code:	T-VHST154
Local IP(s):	192.168.1.32
Aircraft Tracked: (ModeS & ADS-B)	0
Aircraft Uploaded:	0
Receiver:	dvbt, Connected
MLAT running:	N/A

Log says:-

2020-07-16 13:13:48 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --net-http-port 8080 --raw)
2020-07-16 13:13:48 | [reader][i]Connected to the receiver, configuring
2020-07-16 13:13:48 | [reader][i]Configured, processing messages
2020-07-16 13:13:49 | [reader][i]Connection terminated
2020-07-16 13:13:49 | [main][i]Terminating child process 6205 with SIGTERM
2020-07-16 13:13:54 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --net-http-port 8080 --raw)
2020-07-16 13:13:55 | [reader][i]Connected to the receiver, configuring
2020-07-16 13:13:55 | [reader][i]Configured, processing messages
2020-07-16 13:13:55 | [reader][i]Connection terminated
2020-07-16 13:13:55 | [main][i]Terminating child process 6216 with SIGTERM
2020-07-16 13:14:00 | [feed][n]ping 9
2020-07-16 13:14:01 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --net-http-port 8080 --raw)
2020-07-16 13:14:01 | [reader][i]Connected to the receiver, configuring
2020-07-16 13:14:01 | [reader][i]Configured, processing messages
2020-07-16 13:14:01 | [feed][n]syncing stream result: 1
2020-07-16 13:14:01 | [reader][i]Connection terminated
2020-07-16 13:14:01 | [main][i]Terminating child process 6232 with SIGTERM


Status says:

2020-07-16 13:13:48 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --net-http-port 8080 --raw)
2020-07-16 13:13:48 | [reader][i]Connected to the receiver, configuring
2020-07-16 13:13:48 | [reader][i]Configured, processing messages
2020-07-16 13:13:49 | [reader][i]Connection terminated
2020-07-16 13:13:49 | [main][i]Terminating child process 6205 with SIGTERM
2020-07-16 13:13:54 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --net-http-port 8080 --raw)
2020-07-16 13:13:55 | [reader][i]Connected to the receiver, configuring
2020-07-16 13:13:55 | [reader][i]Configured, processing messages
2020-07-16 13:13:55 | [reader][i]Connection terminated
2020-07-16 13:13:55 | [main][i]Terminating child process 6216 with SIGTERM
2020-07-16 13:14:00 | [feed][n]ping 9
2020-07-16 13:14:01 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --net-http-port 8080 --raw)
2020-07-16 13:14:01 | [reader][i]Connected to the receiver, configuring
2020-07-16 13:14:01 | [reader][i]Configured, processing messages
2020-07-16 13:14:01 | [feed][n]syncing stream result: 1
2020-07-16 13:14:01 | [reader][i]Connection terminated
2020-07-16 13:14:01 | [main][i]Terminating child process 6232 with SIGTERM


When I start fr24feed status I get

pi@raspberrypi:~ $ fr24feed status
/dev/shm/decoder.txt: Permission denied
[main][e]Could not create monitor file!
Could not open /var/log/fr24feed/fr24feed.log for writing!
______ _ _ _ _ _ _____ ___
| ___|| |(_) | | | | | | / __ \ / |
| |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
| _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
| | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
\_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
__/ |
|___/
[main][i]FR24 Feeder/Decoder
[main][i]Version: 1.0.25-3/generic
[main][i]Built on Apr 8 2020 07:06:55 (HEAD-5e8ef0c.git/Linux/static_armel)
[main][i]Running on: pi24-raspbian10
[main][i]Local IP(s): 192.168.1.32
[main][i]Copyright 2012-2020 Flightradar24 AB
[main][i]https://www.flightradar24.com
[main][i]DNS mode: PING
[main][i]Automatic updates are ENABLED
ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
[httpd][w]bind function failed, errno: 98, waiting 1 seconds
[i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
[httpd][w]bind function failed, errno: 98, waiting 6 seconds
[d]TLSConnection::ctor(): Enable verify_peer in production code!
[main][i]Reader thread started
[time][i]Synchronizing time via NTP
[master][i]Starting processing thread
[reader][i]Initializing reader
[reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
Thu Jul 16 13:17:31 2020 BST EB_SOURCE EB_VERSION starting up.
Using sample converter: UC8, integer/table path
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
[time][i]Time synchronized correctly, offset -0.020 seconds
[main][i]Feed Network client started
[feed][i]Downloading configuration
[feed][d]fetching configuration
Found Fitipower FC0012 tuner
Max available gain is: 19.20 dB
Setting gain to: 19.20 dB
[FC0012] no valid PLL combination found for 1090000000 Hz!
Gain reported by device: 19.20 dB
Allocating 15 zero-copy buffers
error | write - missing monitor file pointer
error | write - missing monitor file pointer
[feed][i]configuring decoder
[feed][c]Max range AIR: 350.0nm
[feed][c]Max range GND: 100.0nm
error | write - missing monitor file pointer
error | write - missing monitor file pointer
[feed][i]configuration changed
[feed][i]defined 3 servers
[feed][c]Timestamps: optional
info | Stopping ReceiverACSender threads for feed
info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: VHST154, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
info | [stats]Stats thread started
info | Network thread connecting to 185.218.24.22:8099 for feed VHST154
[feed][n]VHST154@185.218.24.22:8099/UDP
error | write - missing monitor file pointer
error | write - missing monitor file pointer
error | write - missing monitor file pointer
[feed][n]connecting
[feed][n]connected via UDP (fd 25)
[feed][i]Feed connected
[feed][n]working
error | write - missing monitor file pointer
error | write - missing monitor file pointer
error | write - missing monitor file pointer
error | write - missing monitor file pointer
error | write - missing monitor file pointer
error | write - missing monitor file pointer
^C[main][i]Terminating on user request
[main][i]Terminating worker threads
error | write - missing monitor file pointer
error | write - missing monitor file pointer

[Oblivian]

2 issues.

1, need to start with SUDO before commands

2, and the biggest. Wrong type of stick:

Found Fitipower FC0012 tuner

[wiedehopf]

3, it's fr24feed-status not fr24feed status

anyhow ... using the wrong command showed that it's the wrong tuner, your SDR won't be able to receive 1090 MHz.
(so maybe it was the right command, unending questions!)

you'll need to buy a new SDR that isn't using the Fitipower tuner but the RTL820 tuner.

[Oblivian]

I will admit, I was scrolling all that going... It's the same thing twice?

The
2020-07-16 13:13:48 | [reader][i]Configured, processing messages
2020-07-16 13:13:49 | [reader][i]Connection terminated

Was sticking out most, Was about to suggest disabling of service, reboot and run manually to see a cleaner output

then I spotted it actually try to load the stick among it.

[Vlasta]

OK so I have a shiny new dongle, a new dipole antennae and the log looks like this - is it working?

2020-07-30 11:26:48 | [main][i]FR24 Feeder/Decoder
2020-07-30 11:26:48 | [main][i]Version: 1.0.25-3/generic
2020-07-30 11:26:48 | [main][i]Built on Apr 8 2020 07:06:55 (HEAD-5e8ef0c.git/Linux/static_armel)
2020-07-30 11:26:48 | [main][i]Running on: pi24-raspbian10
2020-07-30 11:26:48 | [main][i]Local IP(s): 192.168.1.32
2020-07-30 11:26:48 | [main][i]Copyright 2012-2020 Flightradar24 AB
2020-07-30 11:26:48 | [main][i]https://www.flightradar24.com
2020-07-30 11:26:48 | [main][i]DNS mode: PING
2020-07-30 11:26:48 | [main][i]Automatic updates are ENABLED
2020-07-30 11:26:48 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
2020-07-30 11:26:48 | info | [httpd]Server started, listening on 0.0.0.0:8754
2020-07-30 11:26:50 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2020-07-30 11:26:51 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2020-07-30 11:26:51 | [main][i]Reader thread started
2020-07-30 11:26:51 | [time][i]Synchronizing time via NTP
2020-07-30 11:26:51 | [master][i]Starting processing thread
2020-07-30 11:26:51 | [reader][i]Initializing reader
2020-07-30 11:26:51 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:26:51 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:26:51 | [reader][i]Configured, processing messages
2020-07-30 11:26:51 | [time][i]Time synchronized correctly, offset -0.005 seconds
2020-07-30 11:26:51 | [main][i]Feed Network client started
2020-07-30 11:26:51 | [feed][i]Downloading configuration
2020-07-30 11:26:51 | [feed][d]fetching configuration
2020-07-30 11:26:51 | [reader][i]Connection terminated
2020-07-30 11:26:51 | [main][i]Terminating child process 2597 with SIGTERM
2020-07-30 11:26:53 | [feed][i]configuring decoder
2020-07-30 11:26:53 | [feed][c]Max range AIR: 350.0nm
2020-07-30 11:26:53 | [feed][c]Max range GND: 100.0nm
2020-07-30 11:26:53 | [feed][i]configuration changed
2020-07-30 11:26:53 | [feed][i]defined 3 servers
2020-07-30 11:26:53 | [feed][c]Timestamps: optional
2020-07-30 11:26:53 | info | Stopping ReceiverACSender threads for feed
2020-07-30 11:26:53 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: VHST154, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
2020-07-30 11:26:53 | info | [stats]Stats thread started
2020-07-30 11:26:53 | info | Network thread connecting to 185.218.24.22:8099 for feed VHST154
2020-07-30 11:26:53 | [feed][n]VHST154@185.218.24.22:8099/UDP
2020-07-30 11:26:53 | [feed][n]connecting
2020-07-30 11:26:53 | [feed][n]connected via UDP (fd 41)
2020-07-30 11:26:53 | [feed][i]Feed connected
2020-07-30 11:26:53 | [feed][n]working
2020-07-30 11:26:57 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:26:57 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:26:57 | [reader][i]Configured, processing messages
2020-07-30 11:26:57 | [reader][i]Connection terminated
2020-07-30 11:26:57 | [main][i]Terminating child process 2615 with SIGTERM
2020-07-30 11:27:03 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:03 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:03 | [reader][i]Configured, processing messages
2020-07-30 11:27:03 | [reader][i]Connection terminated
2020-07-30 11:27:03 | [main][i]Terminating child process 2629 with SIGTERM
2020-07-30 11:27:09 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:09 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:09 | [reader][i]Configured, processing messages
2020-07-30 11:27:09 | [reader][i]Connection terminated
2020-07-30 11:27:09 | [main][i]Terminating child process 2644 with SIGTERM
2020-07-30 11:27:14 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:14 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:14 | [reader][i]Configured, processing messages
2020-07-30 11:27:15 | [reader][i]Connection terminated
2020-07-30 11:27:15 | [main][i]Terminating child process 2658 with SIGTERM
2020-07-30 11:27:20 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:20 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:20 | [reader][i]Configured, processing messages
2020-07-30 11:27:21 | [reader][i]Connection terminated
2020-07-30 11:27:21 | [main][i]Terminating child process 2673 with SIGTERM
2020-07-30 11:27:23 | [feed][n]ping 1
2020-07-30 11:27:24 | [feed][n]syncing stream result: 1
2020-07-30 11:27:26 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:26 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:26 | [reader][i]Configured, processing messages
2020-07-30 11:27:27 | [reader][i]Connection terminated
2020-07-30 11:27:27 | [main][i]Terminating child process 2685 with SIGTERM
2020-07-30 11:27:32 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:32 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:32 | [reader][i]Configured, processing messages
2020-07-30 11:27:33 | [reader][i]Connection terminated
2020-07-30 11:27:33 | [main][i]Terminating child process 2702 with SIGTERM
2020-07-30 11:27:38 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:38 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:38 | [reader][i]Configured, processing messages
2020-07-30 11:27:38 | [reader][i]Connection terminated
2020-07-30 11:27:38 | [main][i]Terminating child process 2713 with SIGTERM
2020-07-30 11:27:44 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:44 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:44 | [reader][i]Configured, processing messages
2020-07-30 11:27:44 | [reader][i]Connection terminated
2020-07-30 11:27:44 | [main][i]Terminating child process 2728 with SIGTERM
2020-07-30 11:27:50 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2020-07-30 11:27:50 | [reader][i]Connected to the receiver, configuring
2020-07-30 11:27:50 | [reader][i]Configured, processing messages
2020-07-30 11:27:50 | [reader][i]Connection terminated
2020-07-30 11:27:50 | [main][i]Terminating child process 2742 with SIGTERM

[Oblivian]

Nope.

Which is why this is repeating.

2020-07-30 11:27:44 | [reader][i]Connection terminated
2020-07-30 11:27:44 | [main][i]Terminating child process 2728 with SIGTERM
2020-07-30 11:27:50 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)

How are you getting this screen?

I suspect you are running it twice. It stars silent on boot. And this looks like you are starting it once again ontop.

The correct check is
Sudo fr24feed-status

No spaces

Or, stopping the auto started copy and then starting it in terminal so you see the full messages as it connects to the usb

https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/9479-fr24feed-uploader-additional-info?p=89018#post89018

[Vlasta]

OK - I restarted the Pi and SSH to it. I still get the same logging like above about terminating child process etc. What am I doing wrong ?

I run the command as follows and get...

pi@raspberrypi:~ $ sudo fr24feed-status

[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp:.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-VHST154.
[ ok ] FR24 Tracked AC: 0.
[FAIL] Receiver: down ... failed!
[FAIL] FR24 MLAT: not running ... failed!

pi@raspberrypi:~ $ ps -ef | grep -i fr24

fr24 402 1 2 12:10 ? 00:00:02 /usr/bin/fr24feed
pi 837 769 0 12:11 pts/1 00:00:00 tail -f fr24feed.log
pi 879 478 0 12:11 pts/0 00:00:00 grep --color=auto -i fr24

[Oblivian]

It may need contacts received to show receiver ok..or its erroring out
so follow instructions on that link

Sudo systemctl stop fr24feed
Sudo fr24feed

It will start only the once and report the stick discovery as it starts

Or once stopped. Run rtl_test and post output

[Vlasta]

OK - I start is as standalone and not as a service and it seems to be working

2020-07-30 12:38:05 | [feed][i]sent 1,0 AC
2020-07-30 12:38:06 | [feed][i]filtering out 4 overlapping AC (saving bandwidth)
2020-07-30 12:38:10 | [feed][i]sent 0,1 AC
2020-07-30 12:38:16 | [feed][i]sent 0,2 AC
2020-07-30 12:38:21 | [feed][i]sent 0,1 AC
2020-07-30 12:38:27 | [feed][i]sent 0,3 AC
2020-07-30 12:38:33 | [feed][i]sent 0,2 AC
2020-07-30 12:38:38 | [feed][i]sent 0,1 AC
2020-07-30 12:38:43 | [feed][i]sent 0,1 AC
2020-07-30 12:38:49 | [feed][i]sent 1,1 AC
2020-07-30 12:38:54 | [feed][i]sent 1,0 AC
2020-07-30 12:39:00 | [feed][i]sent 1,0 AC
2020-07-30 12:39:05 | [feed][i]sent 1,0 AC
2020-07-30 12:39:06 | [feed][i]filtering out 4 overlapping AC (saving bandwidth)
2020-07-30 12:39:10 | [feed][i]sent 1,1 AC
2020-07-30 12:39:15 | [feed][i]sent 1,2 AC
2020-07-30 12:39:21 | [feed][i]sent 1,1 AC
2020-07-30 12:39:26 | [feed][i]sent 1,0 AC
2020-07-30 12:39:31 | [feed][i]sent 1,0 AC
2020-07-30 12:39:36 | [feed][i]sent 1,0 AC
2020-07-30 12:39:41 | [feed][i]sent 1,0 AC
2020-07-30 12:39:46 | [feed][i]sent 1,0 AC
2020-07-30 12:39:51 | [feed][i]sent 1,0 AC
2020-07-30 12:39:51 | [feed][n]syncing stream async: 1
2020-07-30 12:39:52 | [feed][n]syncing stream result: 1
2020-07-30 12:39:56 | [feed][i]sent 1,0 AC
2020-07-30 12:40:02 | [feed][i]sent 1,0 AC
2020-07-30 12:40:07 | [feed][i]sent 1,0 AC
2020-07-30 12:40:08 | [feed][i]filtering out 3 overlapping AC (saving bandwidth)
2020-07-30 12:40:12 | [feed][i]sent 0,1 AC
2020-07-30 12:40:17 | [feed][i]sent 0,1 AC
2020-07-30 12:40:23 | [feed][i]sent 0,1 AC
2020-07-30 12:40:28 | [feed][i]sent 0,1 AC
2020-07-30 12:40:34 | [feed][i]sent 0,1 AC
2020-07-30 12:40:36 | info | [stats]sent 503 bytes
2020-07-30 12:40:39 | [feed][i]sent 0,1 AC
2020-07-30 12:40:44 | [feed][i]sent 0,1 AC
2020-07-30 12:40:50 | [feed][i]sent 0,1 AC
2020-07-30 12:40:55 | [feed][i]sent 0,1 AC
2020-07-30 12:41:01 | [feed][i]sent 0,1 AC
2020-07-30 12:41:06 | [feed][i]sent 0,1 AC
2020-07-30 12:41:11 | [feed][i]sent 1,1 AC
2020-07-30 12:41:12 | [feed][i]filtering out 2 overlapping AC (saving bandwidth)

[Oblivian]

Yep 1 aircraft now. So was poss why fr24feed-status was not OK earlier

ctrl-z to stop that.

And do run rtl_test to make sure you have the right chipset this time

sudo systemctl start fr24feed

will start it (hidden) once more

[Vlasta]

Nope - as soon as I start it as a service the errors come back. I tried sudo systemctl start fr24feed - errors in log.

I am not sure how to run rtl_test

[Oblivian]

just as it is

sudo rtl_test

But it needs ALL fr24feed stopped or you will see claim_6

[Vlasta]

sudo rtl_test - command not found

[Oblivian]

Then somethings lacking from your install for whatever reason

pi@raspberrypi:~ $ sudo rtl_test
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM


But you will see the same detection phase during the startup like your log had previously

reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
Thu Jul 16 13:17:31 2020 BST EB_SOURCE EB_VERSION starting up.
Using sample converter: UC8, integer/table path
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
[time][i]Time synchronized correctly, offset -0.020 seconds

Followed by the tuner detection.


As to why you are getting errors and can't run as systemctl. I have no answer. But your original logs have all sorts of permission errors

[abcd567]

(1) Download fresh copy of Pi24 image
(2) Re-image microSD card using fresh copy of Pi24 image.