yayitazale Posted July 7, 2019 Share Posted July 7, 2019 On 6/27/2019 at 7:53 PM, FoxxMD said: @yayitazale The first block you quoted about config is specific to setting up shinysdr. In that post you only need to follow through Step 5 in order to passthrough the device. I have not had the time to create templates for @ShoGinn's dockers yet. Can you post a more complete container log? It's hard to tell what is going on from the excerpt you gave. My guess is that you are missing some configuration or have not correctly passed through the device to the container. I'm following your stetps as you describe: Downloaded and edited the config.js changing only the LAT and LON values. Downloaded and edited the fr24feed.ini adding the fr24 key Downloaded and edited the piaware.conf adding the user password and ID Created a upintheair.json. The binding are host file path to your template defined container path, I didn't change anything. The port binding are untouched, as you can see at the screen capture. I attached the container log and the screen captures of what I'm getting. I can't understand what I'm doing wrong, I ust followed your steps one by one. Thanks log.txt Quote Link to comment
AcidReign Posted July 9, 2019 Share Posted July 9, 2019 Sorry for the Newbie-Question, but do I need a Antenna for this to make sense? My Server is in the basement and I have no Chance of reception down there. Quote Link to comment
FoxxMD Posted July 18, 2019 Author Share Posted July 18, 2019 @yayitazale from the logs you posted you can see piaware is not staying up 2019-07-07 20:27:35,450 INFO exited: piaware (exit status 4; not expected) Taking a look at the piaware source we see that exit code 4 is used when login fails. I'm guessing the container becomes unresponsive because supervisord is constantly trying to restart the process. Quote Link to comment
FoxxMD Posted July 18, 2019 Author Share Posted July 18, 2019 @khile Check the instructions. You need to go to the FR24 website, register an account, and apply for a key. Quote Link to comment
FoxxMD Posted July 18, 2019 Author Share Posted July 18, 2019 On 7/9/2019 at 4:13 PM, AcidReign said: Sorry for the Newbie-Question, but do I need a Antenna for this to make sense? My Server is in the basement and I have no Chance of reception down there. Yes, you need an antenna and a USB SDR, like this, in order to run this software. Quote Link to comment
yayitazale Posted July 18, 2019 Share Posted July 18, 2019 (edited) 58 minutes ago, FoxxMD said: @yayitazale from the logs you posted you can see piaware is not staying up 2019-07-07 20:27:35,450 INFO exited: piaware (exit status 4; not expected) Taking a look at the piaware source we see that exit code 4 is used when login fails. I'm guessing the container becomes unresponsive because supervisord is constantly trying to restart the process. Still having some trouble. The gmap.html gives a 404 not found error, MLAT is not starting and same error getting aircrafts GET /data/aircraft.json?_=1563474594589 HTTP/1.1" 404 - code 404, message File not found I have manually created the file on the /usr/lib/fr24/public_html/data path (by the way, the folder is empty) and the error disapears but the feeder is not writting anything on that file so there is no tracked planes... I think something is not being configured properly by the initial script.... Edited July 18, 2019 by yayitazale Quote Link to comment
craig_read Posted July 19, 2019 Share Posted July 19, 2019 (edited) Apologies because I am quite new to this too, but I've not managed to get the WebUI to work. I receive; Error response Error code 404. Message: File not found. Error code explanation: 404 = Nothing matches the given URI. I know it's working as I am tracking aircraft on both piaware and fr24, and I can view my tracking data in my account on both those websites. I followed your instructions, but I am not sure how to complete this part (I have already copied the file to the correct location though); "uncomment #COPY upintheair.json /usr/lib/fr24/... from Dockerfile." Where an how exactly do I do that (I appreciate that may be obvious to most and I have been googling but not managed it)... On piaware I am also getting no MLAT... Any pointer would be great, really glad I have this running though, saves me a separate box in the house! Thank you. Edited July 19, 2019 by craig_read Quote Link to comment
yayitazale Posted July 19, 2019 Share Posted July 19, 2019 1 hour ago, craig_read said: Apologies because I am quite new to this too, but I've not managed to get the WebUI to work. I receive; Error response Error code 404. Message: File not found. Error code explanation: 404 = Nothing matches the given URI. I know it's working as I am tracking aircraft on both piaware and fr24, and I can view my tracking data in my account on both those websites. I followed your instructions, but I am not sure how to complete this part (I have already copied the file to the correct location though); "uncomment #COPY upintheair.json /usr/lib/fr24/... from Dockerfile." Where an how exactly do I do that (I appreciate that may be obvious to most and I have been googling but not managed it)... On piaware I am also getting no MLAT... Any pointer would be great, really glad I have this running though, saves me a separate box in the house! Thank you. Seems we have the exactly the same issue then... I'm not alone! Quote Link to comment
FoxxMD Posted July 19, 2019 Author Share Posted July 19, 2019 @yayitazale @craig_read Here are the contents of my various files. I think maybe the repo author hasn't updated the samples in awhile. Maybe these will help you: fr24feed.ini receiver="dvbt" fr24key="your_key_here" bs="yes" raw="yes" logmode="1" mpx="no" mlat="yes" mlat-without-gps="yes" procargs="--net --write-json /usr/lib/fr24/public_html/data" the last argument, procargs, is what actually feeds data into the map. its important that it exists piaware.conf # This file configures piaware and related software. # You can edit it directly or use piaware-config from the command line # to view and change settings. # # If /boot/piaware-config.txt also exists, then settings present in # that file will override settings in this file. flightaware-user FoxxMD flightaware-password myPass feeder-id myId allow-mlat yes mlat-results yes My config.js is essentially the same and upinair.json is optional (and specific to your location) Quote Link to comment
yayitazale Posted July 20, 2019 Share Posted July 20, 2019 18 hours ago, FoxxMD said: @yayitazale @craig_read Here are the contents of my various files. I think maybe the repo author hasn't updated the samples in awhile. Maybe these will help you: fr24feed.ini receiver="dvbt" fr24key="your_key_here" bs="yes" raw="yes" logmode="1" mpx="no" mlat="yes" mlat-without-gps="yes" procargs="--net --write-json /usr/lib/fr24/public_html/data" the last argument, procargs, is what actually feeds data into the map. its important that it exists piaware.conf # This file configures piaware and related software. # You can edit it directly or use piaware-config from the command line # to view and change settings. # # If /boot/piaware-config.txt also exists, then settings present in # that file will override settings in this file. flightaware-user FoxxMD flightaware-password myPass feeder-id myId allow-mlat yes mlat-results yes My config.js is essentially the same and upinair.json is optional (and specific to your location) Thanks, but I get same results, no gmap.html and no aircraft.json.... I thinks this is something about permissions... but I can't figure it out how to solve it. Quote Link to comment
craig_read Posted July 21, 2019 Share Posted July 21, 2019 I am afraid the result is the same for me too.. Quote Link to comment
PSYCHOPATHiO Posted September 10, 2019 Share Posted September 10, 2019 (edited) did something change with the latest update? for some reason my flight24 feed is down while flightaware is still working! I'm looking into the fr24feed.ini but not sure where the problem lies. Nevermind, the problem was in a VLAN I added & also added a DNS entry in the main LAN DNS that rendered half my server useless. Edited September 10, 2019 by PSYCHOPATHiO Solved Quote Link to comment
PSYCHOPATHiO Posted December 9, 2019 Share Posted December 9, 2019 @FoxxMD There was a docker update this morning, any new changes? I checked the github & docker pages with no changes in the last 6 months. Quote Link to comment
FoxxMD Posted December 16, 2019 Author Share Posted December 16, 2019 @PSYCHOPATHiO I'd wager the change was an update to an intermediate layer in the build. I'm a little behind my expected time for working on getting @ShoGinn's repos written up as templates 😅 but I finally have some free time! Should probably have these up on CA in the next weekish. Hopefully their more up to date/modular approach will help solve some of the issues people have been having this thread. 1 Quote Link to comment
craig_read Posted March 2, 2020 Share Posted March 2, 2020 (edited) Hi, Yes I am having problems, I'm using the fr24feed-piaware docker image. I am able to send data to FlightAware, but no data is being sent to FlightRadar24. It would appear it's not been working for some time if I look at my statistics. Could someone provide me a pointer as to where to look to get this resolved? EDIT: It appears to be a know bug in the latest release of FlightRadar24... Thanks Craig Edited March 2, 2020 by craig_read Quote Link to comment
mihu Posted March 7, 2020 Share Posted March 7, 2020 (edited) Mine started crashing a lot after recent updates. Some weird behavior in logs. https://pastebin.com/gJB9Wa32 Edit: Seems to be fixed now Edit2: And gone crazy again. It's as if it stopped reading conf files properly. It shows center in weird place. Edit3: Well I need to look deeper into this. Mantainer of the github repo has done some breaking changes recently. I was thinking of moving to raspberry pi anyway as I don't like 3m usb cable going from my unraid server to window where my sdr is located Edit4: I decided to go with Shoginn's containers. I liked the idea of a single container but Shoginn's seem to work better anyway. Edited March 11, 2020 by mihu Quote Link to comment
timmo Posted March 12, 2020 Share Posted March 12, 2020 On 3/7/2020 at 8:14 AM, mihu said: Mantainer of the github repo has done some breaking changes recently. Can confirm. After updating the container is not functioning right. Even if I try to manually edit the receiver.json file, it still ignores the lat/lon and centers somewhere In Italy while I'm actually in Central US. Also went from an average of 40+ aircraft with positions to 2, I can't see any aircraft on the map anymore and I'm even near an airport. Quote Link to comment
FoxxMD Posted March 12, 2020 Author Share Posted March 12, 2020 @timmo I would suggest migrating to shoginn-dump1090 and related containers as they are better maintained (maintainer is an unraid user here!) and have more options for usage of your receiver data. 1 Quote Link to comment
timmo Posted March 12, 2020 Share Posted March 12, 2020 @FoxxMD Understood, I appreciate the guidance. I will try this. Quote Link to comment
cjhammel Posted June 16, 2020 Share Posted June 16, 2020 I can not get this docker to start. The docker app is creating folders in the appdata folder instead of files for the configurations. Quote Link to comment
nommiiss Posted June 18, 2020 Share Posted June 18, 2020 On 6/16/2020 at 2:55 AM, cjhammel said: I can not get this docker to start. The docker app is creating folders in the appdata folder instead of files for the configurations. I am getting the same and I am hoping that someone could help me out getting this app working for me... I have pasted my logs from the startup of the app below. Could someone who knows whats going on to have a look over the logs to see what I or the app is doing wrong Thanks Simon ************************************************************** [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-confd-fr24feed: executing... 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO Backend set to env 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO Starting confd 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO Backend source(s) set to 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO /etc/fr24feed.ini has UID 99 should be 0 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO /etc/fr24feed.ini has GID 100 should be 0 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO /etc/fr24feed.ini has mode drwxrwxrwx should be -rwxrwxrwx 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO /etc/fr24feed.ini has md5sum d41d8cd98f00b204e9800998ecf8427e should be 2e7f7b590f4170b8cef82c6eb6d68551 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: INFO Target config /etc/fr24feed.ini out of sync 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: ERROR rename /etc/.fr24feed.ini400967101 /etc/fr24feed.ini: file exists 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[235]: FATAL rename /etc/.fr24feed.ini400967101 /etc/fr24feed.ini: file exists [cont-init.d] 01-confd-fr24feed: exited 1. [cont-init.d] 02-confd-piaware: executing... 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO Backend set to env 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO Starting confd 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO Backend source(s) set to 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO /etc/piaware.conf has UID 99 should be 0 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO /etc/piaware.conf has GID 100 should be 0 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO /etc/piaware.conf has mode drwxrwxrwx should be -rwxrwxrwx 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO /etc/piaware.conf has md5sum d41d8cd98f00b204e9800998ecf8427e should be 02b68abf8a0d00b67789aeb454a293ab 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: INFO Target config /etc/piaware.conf out of sync 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: ERROR rename /etc/.piaware.conf514388129 /etc/piaware.conf: file exists 2020-06-18T08:51:02+01:00 a8ea57ca7040 /opt/confd/bin/confd[247]: FATAL rename /etc/.piaware.conf514388129 /etc/piaware.conf: file exists [cont-init.d] 02-confd-piaware: exited 1. [cont-init.d] 03-confd-html: executing... 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO Backend set to env 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO Starting confd 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO Backend source(s) set to 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO /usr/lib/fr24/public_html/config.js has UID 99 should be 0 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO /usr/lib/fr24/public_html/config.js has GID 100 should be 0 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO /usr/lib/fr24/public_html/config.js has mode drwxrwxrwx should be -rwxrwxrwx 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO /usr/lib/fr24/public_html/config.js has md5sum d41d8cd98f00b204e9800998ecf8427e should be 8c90370147ca6a93fcc8efcf65e94a6b 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: INFO Target config /usr/lib/fr24/public_html/config.js out of sync 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: ERROR rename /usr/lib/fr24/public_html/.config.js460137725 /usr/lib/fr24/public_html/config.js: file exists 2020-06-18T08:51:03+01:00 a8ea57ca7040 /opt/confd/bin/confd[261]: FATAL rename /usr/lib/fr24/public_html/.config.js460137725 /usr/lib/fr24/public_html/config.js: file exists [cont-init.d] 03-confd-html: exited 1. [cont-init.d] 04-upintheair: executing... [cont-init.d] 04-upintheair: exited 0. [cont-init.d] done. [services.d] starting services Thu Jun 18 08:51:03 2020 BST dump1090-fa v3.8.1 starting up. [services.d] done. [main]FR24 Feeder/Decoder [main]Version: 1.0.18-5/generic [main]Built on Mar 4 2016 16:26:55 (devel-d11ca48.git/Linux/x86_64) [main]Copyright 2012-2016 Flightradar24 AB [main]http://flightradar24.com [main]DNS mode: LIBC FR24 Feeder/Decoder usage: /fr24feed/fr24feed_amd64/fr24feed --fr24key=0123456789ABCDEF| Start feeding process manually /fr24feed/fr24feed_amd64/fr24feed --signup | Sign up and configure /fr24feed/fr24feed_amd64/fr24feed --reconfigure | Change configuration /fr24feed/fr24feed_amd64/fr24feed --version | Show binary version number rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000) s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. warning: /etc/piaware.conf: failed to read config file: error reading "file3": illegal operation on a directory **************************************************** piaware version 3.8.1 is running, process ID 310 your system info is: Linux a8ea57ca7040 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux [s6-finish] syncing disks. Found Rafael Micro R820T tuner rtlsdr: tuner gain set to 49.6 dB Allocating 4 zero-copy buffers [s6-finish] sending all processes the TERM signal. Reloading configuration and reconnecting. warning: /etc/piaware.conf: failed to read config file: error reading "file3": illegal operation on a directory piaware (process 310) is shutting down because it received a shutdown signal (SIGTERM) from the system... piaware (process 310) is exiting... [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-confd-fr24feed: executing... 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO Backend set to env 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO Starting confd 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO Backend source(s) set to 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO /etc/fr24feed.ini has UID 99 should be 0 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO /etc/fr24feed.ini has GID 100 should be 0 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO /etc/fr24feed.ini has mode drwxrwxrwx should be -rwxrwxrwx 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO /etc/fr24feed.ini has md5sum d41d8cd98f00b204e9800998ecf8427e should be 2e7f7b590f4170b8cef82c6eb6d68551 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: INFO Target config /etc/fr24feed.ini out of sync 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: ERROR rename /etc/.fr24feed.ini690184599 /etc/fr24feed.ini: file exists 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[238]: FATAL rename /etc/.fr24feed.ini690184599 /etc/fr24feed.ini: file exists [cont-init.d] 01-confd-fr24feed: exited 1. [cont-init.d] 02-confd-piaware: executing... 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO Backend set to env 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO Starting confd 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO Backend source(s) set to 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO /etc/piaware.conf has UID 99 should be 0 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO /etc/piaware.conf has GID 100 should be 0 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO /etc/piaware.conf has mode drwxrwxrwx should be -rwxrwxrwx 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO /etc/piaware.conf has md5sum d41d8cd98f00b204e9800998ecf8427e should be 02b68abf8a0d00b67789aeb454a293ab 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: INFO Target config /etc/piaware.conf out of sync 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: ERROR rename /etc/.piaware.conf598477025 /etc/piaware.conf: file exists 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[250]: FATAL rename /etc/.piaware.conf598477025 /etc/piaware.conf: file exists [cont-init.d] 02-confd-piaware: exited 1. [cont-init.d] 03-confd-html: executing... 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO Backend set to env 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO Starting confd 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO Backend source(s) set to 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO /usr/lib/fr24/public_html/config.js has UID 99 should be 0 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO /usr/lib/fr24/public_html/config.js has GID 100 should be 0 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO /usr/lib/fr24/public_html/config.js has mode drwxrwxrwx should be -rwxrwxrwx 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO /usr/lib/fr24/public_html/config.js has md5sum d41d8cd98f00b204e9800998ecf8427e should be 8c90370147ca6a93fcc8efcf65e94a6b 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: INFO Target config /usr/lib/fr24/public_html/config.js out of sync 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: ERROR rename /usr/lib/fr24/public_html/.config.js707951769 /usr/lib/fr24/public_html/config.js: file exists 2020-06-18T08:54:16+01:00 a8ea57ca7040 /opt/confd/bin/confd[263]: FATAL rename /usr/lib/fr24/public_html/.config.js707951769 /usr/lib/fr24/public_html/config.js: file exists [cont-init.d] 03-confd-html: exited 1. [cont-init.d] 04-upintheair: executing... [cont-init.d] 04-upintheair: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Thu Jun 18 08:54:16 2020 BST dump1090-fa v3.8.1 starting up. [main]FR24 Feeder/Decoder [main]Version: 1.0.18-5/generic [main]Built on Mar 4 2016 16:26:55 (devel-d11ca48.git/Linux/x86_64) [main]Copyright 2012-2016 Flightradar24 AB [main]http://flightradar24.com [main]DNS mode: LIBC FR24 Feeder/Decoder usage: /fr24feed/fr24feed_amd64/fr24feed --fr24key=0123456789ABCDEF| Start feeding process manually /fr24feed/fr24feed_amd64/fr24feed --signup | Sign up and configure /fr24feed/fr24feed_amd64/fr24feed --reconfigure | Change configuration /fr24feed/fr24feed_amd64/fr24feed --version | Show binary version number s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000) [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. warning: /etc/piaware.conf: failed to read config file: error reading "file3": illegal operation on a directory **************************************************** piaware version 3.8.1 is running, process ID 312 your system info is: Linux a8ea57ca7040 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux [s6-finish] syncing disks. Found Rafael Micro R820T tuner rtlsdr: tuner gain set to 49.6 dB Allocating 4 zero-copy buffers [s6-finish] sending all processes the TERM signal. Reloading configuration and reconnecting. warning: /etc/piaware.conf: failed to read config file: error reading "file3": illegal operation on a directory piaware (process 312) is shutting down because it received a shutdown signal (SIGTERM) from the system... piaware (process 312) is exiting... [s6-finish] sending all processes the KILL signal and exiting. Quote Link to comment
nickster Posted September 3, 2020 Share Posted September 3, 2020 (edited) On 6/18/2020 at 8:59 AM, nommiiss said: I am getting the same and I am hoping that someone could help me out getting this app working for me... I have pasted my logs from the startup of the app below. Could someone who knows whats going on to have a look over the logs to see what I or the app is doing wrong Thanks Simon ************************************************************** It looks like the ini files are created as a folder rather than files - I edited the .conf.txt and .ini.txt files, deleted the folders, and removed the .txt, and it now seems to be uploading to FlightAware, however the web interface doesn't seem to work - it first goes to gmap.html, which if you remove and just go directly to the port, it loads up SkyAware, but it just hangs on a spinny loading bar (not sure if this is because I changed the port). Going to the FlightAware site suggests that it's uploading, though. FR24 seems to state that there's no aircraft tracked on the web interface (and is also why when looking through the logs, there's an error 'rtlsdr: error opening the RTLSDR device: Device or resource busy')- EDIT: fixed this by following the instructions here: https://github.com/Thom-x/docker-fr24feed-piaware-dump1090/issues/21 and updating the fr24feed.ini file to use beast-tcp Edited September 3, 2020 by nickster fixed FR24 Quote Link to comment
djmattc Posted October 5, 2020 Share Posted October 5, 2020 Hello Did anyone get to the bottom of the container not starting? I'm having a similar issue as above where folder were being created instead of files. Now the image just bombs out. Logs below :- ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-confd-fr24feed: executing... [cont-init.d] 01-confd-fr24feed: exited 0. [cont-init.d] 02-confd-piaware: executing... [cont-init.d] 02-confd-piaware: exited 0. [cont-init.d] 03-confd-html: executing... [cont-init.d] 03-confd-html: exited 0. [cont-init.d] 04-upintheair: executing... [cont-init.d] 04-upintheair: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Mon Oct 5 21:00:40 2020 BST dump1090-fa v3.8.1 starting up. [main]FR24 Feeder/Decoder [main]Version: 1.0.18-5/generic [main]Built on Mar 4 2016 16:26:55 (devel-d11ca48.git/Linux/x86_64) [main]Copyright 2012-2016 Flightradar24 AB [main]http://flightradar24.com [main]DNS mode: LIBC FR24 Feeder/Decoder usage: /fr24feed/fr24feed/fr24feed --fr24key=0123456789ABCDEF| Start feeding process manually /fr24feed/fr24feed/fr24feed --signup | Sign up and configure /fr24feed/fr24feed/fr24feed --reconfigure | Change configuration /fr24feed/fr24feed/fr24feed --version | Show binary version number s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000) **************************************************** piaware version 3.8.1 is running, process ID 315 your system info is: Linux 73e9881530cc 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux [s6-finish] syncing disks. Found Rafael Micro R820T tuner rtlsdr: tuner gain set to 49.6 dB Allocating 4 zero-copy buffers 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 ed84c687-ccf6-44e1-89c1-f9911709960d [s6-finish] sending all processes the TERM signal. Reloading configuration and reconnecting. piaware (process 315) is shutting down because it received a shutdown signal (SIGTERM) from the system... piaware (process 315) is exiting... [s6-finish] sending all processes the KILL signal and exiting. Thanks, Quote Link to comment
TheNore Posted December 8, 2020 Share Posted December 8, 2020 I am having the same issue... I can get to the page still but it looks like this, and does not function. Quote Link to comment
polishprocessors Posted December 31, 2020 Share Posted December 31, 2020 (edited) Does anyone else have issues with unraid changing the USB device ID regularly? I keep getting notifications from FlightAware because my RTL device is moving around between devices on one USB bus. This occurs if I plug anything into another USB port or, sometimes, when I don’t. Is there a way to lock a device to a specific ID within unraid/the OS? Edit: found this which fixed it: Edited January 4, 2021 by polishprocessors Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.