Cannot recover feed after obviously corrupted fr24feed.ini file

[OmniJet]

I look forward to receive some help on this problem:

My Pi 3b+ did stop feeding Flightradar24. The installation uses dump1090-fa and feeds to Flightradar24, Flightaware, Adsbexchange and OpenSky.
All feeds are working fine except the Flightradar24.

I found that the fr24feed.ini file was obviously corrupted as it contained lots of text and unprintable symbols which surely do not belong there.

After editing the fr24feed.ini file with what should in it I did a reboot but with no effect.

Stopping and restarting the service did not help either.
pi@piaware:~ $ sudo systemctl restart fr24feed
pi@piaware:~ $ fr24feed-status
[FAIL] FR24 Feeder/Decoder Process ... failed!
pi@piaware:~ $


pi@piaware:~ $ apt-cache policy fr24feed
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/flightaware.com_mirror_raspbian_raspbian_dists_str etch_main_binary-armhf_Packages
E: The package lists or status file could not be parsed or opened.
pi@piaware:~ $


Next step was to re-install Flightradar24 using
sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"

The result was:

pi@piaware:~ $ sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"
--2021-02-01 16:51:15-- https://repo-feed.flightradar24.com/install_fr24_rpi.sh
Resolving repo-feed.flightradar24.com (repo-feed.flightradar24.com)... 104.17.45.52, 104.17.42.52, 104.17.43.52, ...
Connecting to repo-feed.flightradar24.com (repo-feed.flightradar24.com)|104.17.45.52|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1284 (1.3K) [text/x-sh]
Saving to: ‘STDOUT’

- 100%[================================================== ============>] 1.25K --.-KB/s in 0.001s

2021-02-01 16:51:16 (874 KB/s) - written to stdout [1284/1284]

Hit:1 http://flightaware.com/mirror/raspbian/raspbian stretch InRelease
Hit:2 http://repo.feed.flightradar24.com flightradar24 InRelease
Hit:3 http://flightaware.com/adsb/piaware/files/packages stretch InRelease
Get:4 http://flightaware.com/mirror/raspberrypi/debian stretch InRelease [25.3 kB]
Fetched 25.3 kB in 2s (11.5 kB/s)
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/flightaware.com_mirror_raspbian_raspbian_dists_str etch_main_binary-armhf_Packages
E: The package lists or status file could not be parsed or opened.
pi@piaware:~ $

After the new installation didn't work I tried to find within this forum and elsewhere hints on how to de-install FR24, but no success.

I would be happy to if someone has a solution.

[Oblivian]

I'm no expert. But run out of space?, Reads like it is a Flightaware fixed image that doesn't want to update sources - they may also be corrupted.

https://raspberrypi.stackexchange.com/questions/93604/raspberry-pi-sudo-apt-get-update-not-working/93630#93630

[abcd567]

"pi@piaware" shows you were using Piaware sd card image from flightaware.

Download its latest version, and re-image your microSD card with it. Then install FR24 feeder on it.

.

[wiedehopf]

After the new installation didn't work I tried to find within this forum and elsewhere hints on how to de-install FR24, but no success.

I would be happy to if someone has a solution.

sudo apt purge fr24feed
That should remove it.

The issues with apt point to a whole different problem with the system that may stem for example from an sd-card going bad.

My recommendations:
Use a new sd-card
Start fresh either with a piaware sd-card image or just Raspbian Buster: https://github.com/wiedehopf/adsb-wi...ADS-B-receiver

[OmniJet]

Thank you all for the quick replies.

@Oblivian:
card usage is 33%

@wiedehopf:
pi@piaware:~ $ sudo apt purge fr24feed
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/flightaware.com_mirror_raspbian_raspbian_dists_str etch_main_binary-armhf_Packages
E: The package lists or status file could not be parsed or opened.
pi@piaware:~ $

@adcd567 & @wiedehopf:
The hours spent on fixing the problem were a bad investment.
I took a new card and started all over which now works perfectly again and the time spent on this was shorter then time spent on fixing.

Thank you all.