Why did my feeder stop working and won't start again?

[DJ1MV]

I had sent a support request to FR24 and sent more data recently, so they hopefully can find the reason.
I like the idea of supporting more services with my receiver(s). I'll try to contact you (wiedehopf) via github, because I would prefer to get an image for the SD card. Thanks!

oops: can not contact you via github (or do not find how to do it). Can you send me an email to dj1mv@darc.de ?

[wiedehopf]

Just start with a regular RPi image, this guide outlines the process: https://github.com/wiedehopf/adsb-wi...ADS-B-receiver

I'm not aware of an image with multiple feed client on it.

[mensa]

What is the solution for my problem?
I am running it on a Debian Linux VM.

[wiedehopf]

The guide i posted is useful in any case, it separates the decoder / feed client and shows how to look at the log for the decoder.

https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb

The SDR only working intermittently can be USB voltage issues, often caused by USB extensions ...
Anyhow the decoder linked above will have better logs than fr24feed ... (the install also reconfigures fr24feed to use it as a data source).

[mensa]

Hello, today I bought a completely new DVB-T stick. The same model which has worked 2 years without problems for me: https://www.amazon.de/gp/product/B013Q94CT6

I still get the same errors as before. So the problem must be the software. Can someone please help me to fix the fr24 software on my Linux installation? What have chaged here??

root@Server:~# fr24feed-status
FR24 Feeder/Decoder Process: running.
FR24 Stats Timestamp: 2022-01-26 12:00:38.
FR24 Link: connected [UDP].
FR24 Radar: T-LOWL177.
FR24 Tracked AC: 0.
Receiver: down ... failed!
FR24 MLAT: not running ... failed!

[mensa]

The guide i posted is useful in any case, it separates the decoder / feed client and shows how to look at the log for the decoder.

https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb

The SDR only working intermittently can be USB voltage issues, often caused by USB extensions ...
Anyhow the decoder linked above will have better logs than fr24feed ... (the install also reconfigures fr24feed to use it as a data source).

I have installed mine on a Debian Linux VM. Can I use your guide 1:1?

[wiedehopf]

I did read that you are on a debian vm ... the guide also says it works on different architectures.

Just the part about installing fr24feed is incorrect as it assumes arm.

[mensa]

Ok. Can you please explain me, how I can uninstall my current installation?

[wiedehopf]

Just run the script for the readsb autoinstall, it will reconfigure the existing fr24feed install.
In the best case it will just start working.

[mensa]

Good morning,

I think that worked, see log below.


fr24feed-status says this now:

FR24 Feeder/Decoder Process: running.
FR24 Stats Timestamp: 2022-01-27 08:35:32.
FR24 Link: connected [UDP].
FR24 Radar: T-LOWL177.
FR24 Tracked AC: 0.
Receiver: connected (0 MSGS/ SYNC).
FR24 MLAT: not running ... failed!

FR24 WebInterface at http://192.168.1.7:8754
vCjiNKb.png



Tar1090 seems not to work at http://192.168.1.7/tar1090
2oAv4yh.png

I did set my location. Anything else necessary?
How to fix that tar1090?


readsb autoinstall output:

https://pastebin.com/ysJFF2HY

[mensa]

It seems to be running, but not receiving/uploading anything, caus since 2 hours I still have 0 aircrafts uploaded:

R7fqaeW.png

How may I check now, what's the problem?

[wiedehopf]

Very likely you have an issue with the SDR ....

Really you're looking at the wrong thing.
The readsb auto install has a command to look at the logs ... please post those relevant logs.
(sudo journalctl --no-pager -u readsb)

[mensa]

Ok, what is "SDR"?

Here are the logs:

root@Server:~# journalctl --no-pager -u readsb
-- Journal begins at Tue 2021-12-21 11:14:58 CET, ends at Thu 2022-01-27 12:25:27 CET. --
Jan 27 09:25:41 Server systemd[1]: Started readsb ADS-B receiver.
Jan 27 09:25:41 Server readsb[352075]: readsb version: wiedehopf git: f1dc5f4 (commited: Tue Jan 25 19:59:03 2022 0100)
Jan 27 09:25:41 Server readsb[352075]: 30002: Raw TCP output port 30005: Beast TCP output port
Jan 27 09:25:41 Server readsb[352075]: 30003: SBS TCP output ALL port 30004: Beast TCP input port
Jan 27 09:25:41 Server readsb[352075]: 30104: Beast TCP input port
Jan 27 09:25:41 Server readsb[352075]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Jan 27 09:25:42 Server readsb[352075]: Found Fitipower FC0012 tuner
Jan 27 09:25:42 Server readsb[352075]: rtlsdr: enabling tuner AGC
Jan 27 09:25:42 Server readsb[352075]: [FC0012] no valid PLL combination found for 1090000000 Hz!
Jan 27 09:25:42 Server readsb[352075]: Allocating 16 zero-copy buffers
Jan 27 09:26:15 Server readsb[352075]: Thu Jan 27 09:26:15 2022 CET Caught SIGTERM, shutting down...
Jan 27 09:26:15 Server systemd[1]: Stopping readsb ADS-B receiver...
Jan 27 09:26:16 Server readsb[352075]: Thu Jan 27 09:26:16 2022 CET Normal exit.
Jan 27 09:26:16 Server systemd[1]: readsb.service: Succeeded.
Jan 27 09:26:16 Server systemd[1]: Stopped readsb ADS-B receiver.
Jan 27 09:26:16 Server systemd[1]: readsb.service: Consumed 1.818s CPU time.
Jan 27 09:26:16 Server systemd[1]: Started readsb ADS-B receiver.
Jan 27 09:26:16 Server readsb[353235]: readsb version: wiedehopf git: f1dc5f4 (commited: Tue Jan 25 19:59:03 2022 0100)
Jan 27 09:26:16 Server readsb[353235]: 30002: Raw TCP output port 30005: Beast TCP output port
Jan 27 09:26:16 Server readsb[353235]: 30003: SBS TCP output ALL port 30004: Beast TCP input port
Jan 27 09:26:16 Server readsb[353235]: 30104: Beast TCP input port
Jan 27 09:26:16 Server readsb[353235]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Jan 27 09:26:17 Server readsb[353235]: Found Fitipower FC0012 tuner
Jan 27 09:26:17 Server readsb[353235]: rtlsdr: enabling tuner AGC
Jan 27 09:26:17 Server readsb[353235]: [FC0012] no valid PLL combination found for 1090000000 Hz!
Jan 27 09:26:17 Server readsb[353235]: Allocating 16 zero-copy buffers
Jan 27 09:33:31 Server readsb[353235]: Thu Jan 27 09:33:31 2022 CET Caught SIGTERM, shutting down...
Jan 27 09:33:31 Server systemd[1]: Stopping readsb ADS-B receiver...
Jan 27 09:33:33 Server readsb[353235]: Thu Jan 27 09:33:33 2022 CET Normal exit.
Jan 27 09:33:33 Server systemd[1]: readsb.service: Succeeded.
Jan 27 09:33:33 Server systemd[1]: Stopped readsb ADS-B receiver.
Jan 27 09:33:33 Server systemd[1]: readsb.service: Consumed 20.463s CPU time.
Jan 27 09:33:33 Server systemd[1]: Started readsb ADS-B receiver.
Jan 27 09:33:33 Server readsb[356077]: readsb version: wiedehopf git: f1dc5f4 (commited: Tue Jan 25 19:59:03 2022 0100)
Jan 27 09:33:33 Server readsb[356077]: Using lat: 48.3145, lon: 14.2835
Jan 27 09:33:33 Server readsb[356077]: 30002: Raw TCP output port 30005: Beast TCP output port
Jan 27 09:33:33 Server readsb[356077]: 30003: SBS TCP output ALL port 30004: Beast TCP input port
Jan 27 09:33:33 Server readsb[356077]: 30104: Beast TCP input port
Jan 27 09:33:33 Server readsb[356077]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Jan 27 09:33:33 Server readsb[356077]: Found Fitipower FC0012 tuner
Jan 27 09:33:33 Server readsb[356077]: rtlsdr: enabling tuner AGC
Jan 27 09:33:33 Server readsb[356077]: [FC0012] no valid PLL combination found for 1090000000 Hz!
Jan 27 09:33:33 Server readsb[356077]: Allocating 16 zero-copy buffers
Jan 27 09:52:43 Server readsb[356077]: Thu Jan 27 09:52:43 2022 CET Caught SIGTERM, shutting down...
Jan 27 09:52:43 Server systemd[1]: Stopping readsb ADS-B receiver...
Jan 27 09:52:44 Server readsb[356077]: Thu Jan 27 09:52:44 2022 CET Normal exit.
Jan 27 09:52:44 Server systemd[1]: readsb.service: Succeeded.
Jan 27 09:52:44 Server systemd[1]: Stopped readsb ADS-B receiver.
Jan 27 09:52:44 Server systemd[1]: readsb.service: Consumed 54.561s CPU time.
-- Boot 18b4bbb2ede049d7be738a4455280f58 --
Jan 27 09:53:26 Server systemd[1]: Started readsb ADS-B receiver.
Jan 27 09:53:30 Server readsb[460]: readsb version: wiedehopf git: f1dc5f4 (commited: Tue Jan 25 19:59:03 2022 0100)
Jan 27 09:53:30 Server readsb[460]: Using lat: 48.3145, lon: 14.2835
Jan 27 09:53:30 Server readsb[460]: 30002: Raw TCP output port 30005: Beast TCP output port
Jan 27 09:53:30 Server readsb[460]: 30003: SBS TCP output ALL port 30004: Beast TCP input port
Jan 27 09:53:30 Server readsb[460]: 30104: Beast TCP input port
Jan 27 09:53:30 Server readsb[460]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Jan 27 09:53:30 Server readsb[460]: Found Fitipower FC0012 tuner
Jan 27 09:53:30 Server readsb[460]: rtlsdr: enabling tuner AGC
Jan 27 09:53:30 Server readsb[460]: [FC0012] no valid PLL combination found for 1090000000 Hz!
Jan 27 09:53:30 Server readsb[460]: Allocating 16 zero-copy buffers

[wiedehopf]

Jan 27 09:53:30 Server readsb[460]: Found Fitipower FC0012 tuner

The USB device to receive stuff.
This tuner is a bad model, it can't receiver 1090 MHz at all, buy another receiver.
If you bought something labeled R820T .... return it and complain.

[mensa]

Exactly that model was receiving and uploading aircrafts now for over 2 years without problems. Why should I exchange it now?
I think that won't solve the problem.
Why should it just suddenly stop uploading, only cause it is a "bad model"?