Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blank piaware but working site #8

Closed
Technikte opened this issue Jun 22, 2019 · 1 comment
Closed

Blank piaware but working site #8

Technikte opened this issue Jun 22, 2019 · 1 comment

Comments

@Technikte
Copy link

Hi again,
since I got a "empty" default piaware.conf I thought that flightaware would not work and I got not working site in the tab "my ADS-B", but I saw I its running all day without username/password/feeder-id.

2019-06-22 18:39:14,274 CRIT Supervisor running as root (no user in config file)
2019-06-22 18:39:14,274 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2019-06-22 18:39:14,278 INFO RPC interface 'supervisor' initialized
2019-06-22 18:39:14,278 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-06-22 18:39:14,278 INFO supervisord started with pid 6
2019-06-22 18:39:15,280 INFO spawned: 'python' with pid 9
2019-06-22 18:39:15,281 INFO spawned: 'fr24feed' with pid 10
2019-06-22 18:39:15,282 INFO spawned: 'piaware' with pid 11
2019-06-22 18:39:15 | [main][i]FR24 Feeder/Decoder
2019-06-22 18:39:15 | [main][i]Version: 1.0.18-5/generic
2019-06-22 18:39:15 | [main][i]Built on Mar 4 2016 16:26:55 (devel-d11ca48.git/Linux/x86_64)
2019-06-22 18:39:15 | [main][i]Copyright 2012-2016 Flightradar24 AB
2019-06-22 18:39:15 | [main][i]http:https://flightradar24.com
2019-06-22 16:39:15Z warning: /etc/piaware.conf:9: invalid value for option feeder-id: YOUR_FEEDER_ID
2019-06-22 18:39:15 | [main][i]DNS mode: LIBC
2019-06-22 18:39:15 | [main][i]Automatic updates are DISABLED
2019-06-22 18:39:15 | ERROR
2019-06-22 18:39:15 | [w]Detected --net argument for dump1090, disabling internal RAW feed!
2019-06-22 18:39:15 | [w]Detected --net argument for dump1090, disabling internal BS feed!
2019-06-22 18:39:15 | [httpd][i]Server started, listening on 0.0.0.0:8754
2019-06-22 18:39:15 | [main][i]Reader thread started
2019-06-22 18:39:15 | [master][i]Starting processing thread
2019-06-22 18:39:15 | [reader][i]Initializing reader
2019-06-22 18:39:15 | [main][i]MLAT data feed started
2019-06-22 18:39:15 | [reader][i]Connecting to Beast receiver via (exe:https:///usr/lib/fr24/dump1090 --net --write-json /usr/lib/fr24/public_html/data --raw --mlat)
2019-06-22 18:39:15 | [mlat][i]Waiting for MLAT configuration
2019-06-22 18:39:15 | [reader][i]Connected to the receiver, configuring
2019-06-22 18:39:15 | [reader][i]Configured, processing messages
Sat Jun 22 18:39:15 2019 CEST dump1090-fa starting up.
rtlsdr: using device #0: Generic RTL2832U (Generic, RTL2832U, SN 77771111153705700)
Found Rafael Micro R820T tuner
rtlsdr: tuner gain set to 49.6 dB
Allocating 4 zero-copy buffers
2019-06-22 18:39:16 | [reader][w]Setting new UTC offset: 0!
2019-06-22 18:39:16 | [time][i]Synchronizing time via NTP
2019-06-22 18:39:16,380 INFO success: python entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-06-22 18:39:16,380 INFO success: fr24feed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-06-22 18:39:16,380 INFO success: piaware entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-06-22 18:39:21 | [time][i]Time synchronized correctly, offset +0.0009 seconds
2019-06-22 18:39:21 | [main][i]Feed Network client started
2019-06-22 18:39:21 | [feed][i]Downloading configuration
2019-06-22 18:39:22 | [feed][c]Interval: 5s
2019-06-22 18:39:22 | [feed][c]Latitude: 52.5935
2019-06-22 18:39:22 | [feed][c]Longitude: 11.8577
2019-06-22 18:39:22 | [feed][c]GND: YES
2019-06-22 18:39:22 | [feed][c]NonADSB: YES
2019-06-22 18:39:22 | [feed][c]Timestamps: optional
2019-06-22 18:39:22 | [feed][c]Max range AIR: 350.0nm
2019-06-22 18:39:22 | [feed][c]Max range GND: 100.0nm
2019-06-22 18:39:22 | [feed][i]defined 4 servers
2019-06-22 18:39:22 | [stats][i]Stats thread started
2019-06-22 18:39:22 | [feed][n][email protected]:8099/UDP
2019-06-22 18:39:22 | [feed][n]connecting
2019-06-22 18:39:22 | [feed][n]connected via UDP (fd 8)
2019-06-22 18:39:22 | [feed][n]working
2019-06-22 18:39:22 | [mlat][i]MLAT configuration received, service ENABLED
2019-06-22 18:39:22 | [mlat][i]Starting MLAT with preconfigured position: 52.59,11.86,108.0
2019-06-22 18:39:22 | [mlat][i]MLAT bandwidth reduction active, level 1
2019-06-22 18:39:22 | [mlat][i]Configuring UDP connection udp:https://mlat-1.fr24.com:19788
2019-06-22 18:39:22 | [mlat][i]Registering MLAT station
2019-06-22 18:39:22 | [feed][i]sent 1, filtered 0 AC in 1 packet
2019-06-22 18:39:22 | [mlat][i]Registering MLAT station: SUCCESS
2019-06-22 18:39:26 | [mlat][i]Received ADS-B time references AC:
2019-06-22 18:39:26 | [mlat][i] 896479

After that I tried to paste in my stuff into piaware.conf and restarted the docker but then piaware quits after seconds with exit code 4. So any way to stop feeding that automatically or how my login data can work ?

@Thom-x
Copy link
Owner

Thom-x commented Jun 22, 2019

If it working without any conf I think it send anonymous data to piaware.
You could try to edit https://github.com/Thom-x/docker-fr24feed-piaware-dump1090/blob/master/supervisord.conf end remove :

[program:piaware]
command=/usr/bin/piaware
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants