On 7/18/2023 at 1:13 PM, MrAndyBurns said:

I have had a reoccurring issue where the container will just stop.

logs says

"send - failed to send 12 + 88 bytes in mode 0, code -1: Broken pipe"

" *** buffer overflow detected ***: terminated\n","stream":"stdout","time":"2023-07-17T12:16:03.9714032Z"

Got the same thing happen to my container like 1 or 2 times per month. Was to lazy (until now, see below) to get a workaround for that could be a shell script that once per day scrambles the docker log of the container and if the word terminated is found it restarts the container.

Until now (if thats enough for your problem solving): I've setup an offline notification (within flightradar24.com click on "My datasharing" and "Show statistics" where you can find a little switch to turn on "OFFLINE EMAIL". At least this way I get noticed that my fr24feed needs a restart.

Here is my shell script:
 

#!/bin/bash

# Define the name of your Docker container
CONTAINER_NAME="FR24FEED"

# Run the 'docker logs' command to fetch the container's logs
LOGS=$(docker logs "$CONTAINER_NAME" 2>&1)

# Define the regex pattern to search for
SEARCH_PATTERN="terminated"

# Use grep to search for the pattern in the logs
if [[ $LOGS =~ $SEARCH_PATTERN ]]; then
    echo "The word 'terminated' was found in the logs."

    # Restart the Docker container
    echo "Restarting the container..."
    docker restart "$CONTAINER_NAME"

    # You can also add additional actions or notifications here if needed
else
    echo "The word 'terminated' was not found in the logs."
fi

Don't forget to make it executable: chmod +x yourscript.sh
That could be run nightly with cronjob (crontab -e) or more modern with systemd timers.

 

Edited September 15, 20232 yr by HackHome

New to this and would like to use it to contribute FR24. Will this work or is there a newer one that would be compatible this docker image? I prefer plug and play type. I see that this was manufactured in 2014 and recommended earlier in this post in 2019..: 

https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-2.html

Edited May 22, 20242 yr by CyberMew

Well I switched to Proxmox in the meantime. Using another docker container that you UnRaid Guys could use of course too. Here is my docker-compose.yml
I am using an DVB-T stick connected to usb:

services:
    fr24feed:
        container_name: fr24feed
        restart: always
        devices:
            - /dev/bus/usb:/dev/bus/usb
        ports:
            - 8754:8754
        image: liggy1/fr24feed
        command: --fr24key=abcdefgh1234566

It can be that simple. Works like a charm
 

4 minutes ago, CyberMew said:

New to this and would like to use it to contribute FR24. Will this work or is there a newer one that would be compatible this docker image? I prefer plug and play type. I see that this was manufactured in 2014 and recommended earlier in this post in 2019..: 

https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-2.html

i have a rtl sdr v3, it works right away, i needed to have the official drivers so to enable bias tee, i did it by following a guide to clone a docker and create your custom one. so far it is perfect.

I’ve since moved on to using a turnkey VM image from here https://adsb.im/home

Hey all, I am having issues getting piaware to see my device. I purchased this receiver and antenna on Amazon. I can see the USB device

 

Bus 001 Device 017: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T

 

and when I run the following docker command 

docker run -it --rm \
	-e 'SERVICE_ENABLE_DUMP1090=false' \
	-e 'SERVICE_ENABLE_HTTP=false' \
	-e 'SERVICE_ENABLE_FR24FEED=false' \
	-e 'SERVICE_ENABLE_PIAWARE=false' \
	thomx/fr24feed-piaware /usr/bin/piaware -plainlog

I see the following

piaware version 9.0.1 is running, process ID 213
your system info is: Linux 36c4029f021a 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux
Connecting to FlightAware adept server at piaware.flightaware.com/1200
Connection with adept server at piaware.flightaware.com/1200 established
TLS handshake with adept server at piaware.flightaware.com/1200 completed
FlightAware server certificate validated
encrypted session established with FlightAware
logged in to FlightAware as user guest
my feeder ID is c852714e-7c92-4f82-ad60-xxxxx
no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
UAT support disabled by local configuration setting: uat-receiver-type
0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s
no ADS-B data program seen listening on port 30005 for 183 seconds, next check in 60s
no ADS-B data program seen listening on port 30005 for 243 seconds, next check in 60s
no ADS-B data program seen listening on port 30005 for 303 seconds, next check in 60s
0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
no ADS-B data program seen listening on port 30005 for 363 seconds, trying to start it...
attempting to start dump1090.. 
can't start dump1090, no services that look like dump1090 found

When I visit https://fr.flightaware.com/adsb/piaware/claim, it never shows me a device. 

 

Any ideas? Thanks for any help you can offer!

Edited October 1, 20241 yr by Kash76

Update - Someone in the flightaware forum helped me force the claim command by adding /feeder_id to the claim URL. 

I have the container up and running but flight aware is not seeing any data. I find it interesting the ini and conf 'files' are directories?! Does this log look normal? There are lots of errors. 

 

2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Backend set to env
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Starting confd
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Backend source(s) set to 
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Backend set to env
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Starting confd
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Backend source(s) set to 
s6-rc: info: service adsbexchange-stats successfully started
s6-rc: info: service adsbexchange-mlat successfully started
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has UID 99 should be 0
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has GID 100 should be 0
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has mode drwxr-xr-x should be -rwxr-xr-x
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has md5sum yyyy should be xxx
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Target config /usr/lib/fr24/public_html/config.js out of sync
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: ERROR rename /usr/lib/fr24/public_html/.config.js735717544 /usr/lib/fr24/public_html/config.js: file exists
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: FATAL rename /usr/lib/fr24/public_html/.config.js735717544 /usr/lib/fr24/public_html/config.js: file exists
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has UID 99 should be 0
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has GID 100 should be 0
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has mode drwxr-xr-x should be -rwxr-xr-x
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has md5sum d41d8cd98f00b204e9800998ecf8427e should be 580dbab8e19fa85c97e7bb3603840914
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Target config /etc/fr24feed.ini out of sync
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: ERROR rename /etc/.fr24feed.ini803908162 /etc/fr24feed.ini: file exists
2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: FATAL rename /etc/.fr24feed.ini803908162 /etc/fr24feed.ini: file exists
s6-rc: warning: unable to start service confd-html: command exited 1
s6-rc: warning: unable to start service confd-fr24feed: command exited 1
[dump1090] Mon Sep 30 23:12:30 2024 CDT  dump1090-fa v9.0 starting up.
[dump1090] rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
[dump1090] Found Rafael Micro R820T tuner
[dump1090] rtlsdr: tuner gain set to 49.6 dB (gain step 28)
[dump1090] Allocating 4 zero-copy buffers

Thanks!

Hi. Just getting into this... having two issues:

First, I keep gettng this "Unfortunately, FlightAware hasn't found a new, unclaimed PiAware feeder to claim."

Second, neither the 8080 or the 8754 page will load. I get a refused connection message.

Any advice or guidance would be appreciated.

Thanks!

I never got it working; I used my Raspberry Pi.

7 hours ago, Kash76 said:

I never got it working; I used my Raspberry Pi.

Some aspects are working others are not. Its very odd.

Also, can't get it to talk to Plane Feeder.

I think I might try this as an alternative if I cannot get it working:
https://www.squaredx.dev/how-to-setup-flight-tracking-on-an-unraid-server/

Failing that, Raspberry Pi it is.

Edited August 15, 2025Aug 15 by NJAtlow

On 8/15/2025 at 8:09 PM, NJAtlow said:

I think I might try this as an alternative if I cannot get it working:
https://www.squaredx.dev/how-to-setup-flight-tracking-on-an-unraid-server/

I wasn’t seeing a map in dump1090, but after setting up Docker Compose exactly as described on this site, the map finally appeared.
Thank you!