FlightAware Discussions

Upgrade to latest versions now local webpage does not work

I updated my with the latest PiAware file and also purged dump-mutibility out of my system and installed dump-fa

The system is talking to the website but i cannot get the skyview webpage at the local address at all.

here is the status in terminal

piaware-status
PiAware master process (piaware) is running with pid 671.
PiAware ADS-B client (faup1090) is running with pid 1129.
PiAware mlat client (fa-mlat-client) is running with pid 1076.
Local ADS-B receiver (dump1090-fa) is running with pid 976.

dump1090-fa (pid 976) is listening for connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is producing data on localhost:30005.

i tried going to the local webpage in my case 192.168.1.200/dump1090-fa but i don’t get any webpage from that address now.

Try 192.168.1.200:8080
KB4ERT

show the output of

ls /etc/lighttpd/conf-enabled

probably you need to do those commands:

sudo lighty-disable-mod dump1090-mutability
sudo lighty-enable-mod dump1090-fa
sudo service lighttpd force-reload

@VE3SJK

Want an easy, headache free solution?

Option 1

Download and write latest Piaware SD card image to your microSD card.

Download page:
https://flightaware.com/adsb/piaware/build
Scroll down to find download link.
OR
Direct download link:
PiAware on Raspbian Linux 3.6.3 ZIP

Option 2

2.1 - Download and write latest Raspbian Stretch Lite image to your microSD card
https://www.raspberrypi.org/downloads/raspbian/

2.2 - Install Piaware data feeder and dump1090-fa

Steps (2), (3), and (4) on this page
https://flightaware.com/adsb/piaware/install

here is the output requested

ls /etc/lighttpd/conf-enabled
89-dump1090.conf 89-dump1090-fa.conf 90-javascript-alias.conf

192.168.1.200:8080 does not go anywhere either.

To answer another reply i cannot reload the whole image this unit is not dedicated to this function and all the other stuff is working fine.

@VE3SJK

Try this:

Step 1 - Purge All and reboot

sudo dpkg --purge piaware

sudo dpkg --purge dump1090-fa

sudo dpkg --purge lighttpd

sudo reboot

Step 2 - Install All and reboot

2.1

wget http://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_3.6.3_all.deb 

sudo dpkg -i piaware-repository_3.6.3_all.deb

sudo apt-get update 

.

2.2

sudo apt-get install piaware

sudo piaware-config allow-auto-updates yes 

sudo piaware-config allow-manual-updates yes

.

2.3

sudo apt-get install dump1090-fa

sudo reboot

.

sudo lighty-disable-mod dump1090
sudo service lighttpd force-reload

Execute those two commands that should do it. And try ctrl-F5 on the webpage after that :slight_smile:

(The webserver config for dump1090 is still active and it interferes with the config dump1090-fa has there)

1 Like

@VE3SJK

Disabling dump1090 module proposed by @wiedehopf is most likely correct solution. Let us wait and see

I did the two commands as suggest but i am still getting errors does see we are on the right track as a problem with lighttpd service.

root@daqsrv6:~# ls /etc/lighttpd/conf-enabled

89-dump1090.conf 90-javascript-alias.conf
root@daqsrv6:~# service lighttpd force-reload
Job for lighttpd.service failed. See ‘systemctl status lighttpd.service’ and ‘journalctl -xn’ for details.
root@daqsrv6:~# systemctl status lighttpd.service
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled)
Active: failed (Result: exit-code) since Mon 2018-12-17 18:37:24 EST; 19s ago
Process: 2263 ExecStartPre=/usr/sbin/lighttpd -t -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)

Dec 17 18:37:24 daqsrv6 lighttpd[2263]: 2018-12-17 18:37:23: (configfile.c.1003) opening configfile /etc/lighttpd/conf-enabled/89-dump1090.conf failed: No such file or directory
Dec 17 18:37:24 daqsrv6 lighttpd[2263]: 2018-12-17 18:37:23: (configfile.c.957) source: /usr/share/lighttpd/include-conf-enabled.pl line: 2 pos: 8 parser failed somehow near here: (EOL)
Dec 17 18:37:24 daqsrv6 lighttpd[2263]: 2018-12-17 18:37:23: (configfile.c.957) source: /etc/lighttpd/lighttpd.conf line: 29 pos: 1 parser failed somehow near here: (EOL)
Dec 17 18:37:24 daqsrv6 systemd[1]: lighttpd.service: control process exited, code=exited status=255
Dec 17 18:37:24 daqsrv6 systemd[1]: Failed to start Lighttpd Daemon.
Dec 17 18:37:24 daqsrv6 systemd[1]: Unit lighttpd.service entered failed state.
root@daqsrv6:~# journalctl -xn
– Logs begin at Wed 1969-12-31 19:00:04 EST, end at Mon 2018-12-17 18:37:24 EST. –
Dec 17 18:36:44 daqsrv6 systemd[1]: lighttpd.service: control process exited, code=exited status=255
Dec 17 18:36:44 daqsrv6 systemd[1]: Failed to start Lighttpd Daemon.
– Subject: Unit lighttpd.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit lighttpd.service has failed.

– The result is failed.
Dec 17 18:36:44 daqsrv6 systemd[1]: Unit lighttpd.service entered failed state.
Dec 17 18:37:23 daqsrv6 systemd[1]: Starting Lighttpd Daemon…
– Subject: Unit lighttpd.service has begun with start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit lighttpd.service has begun starting up.
Dec 17 18:37:24 daqsrv6 lighttpd[2263]: 2018-12-17 18:37:23: (configfile.c.1003) opening configfile /etc/lighttpd/conf-enabled/89-dump1090.conf failed: No such file or directory
Dec 17 18:37:24 daqsrv6 lighttpd[2263]: 2018-12-17 18:37:23: (configfile.c.957) source: /usr/share/lighttpd/include-conf-enabled.pl line: 2 pos: 8 parser failed somehow near here: (EOL)
Dec 17 18:37:24 daqsrv6 lighttpd[2263]: 2018-12-17 18:37:23: (configfile.c.957) source: /etc/lighttpd/lighttpd.conf line: 29 pos: 1 parser failed somehow near here: (EOL)
Dec 17 18:37:24 daqsrv6 systemd[1]: lighttpd.service: control process exited, code=exited status=255
Dec 17 18:37:24 daqsrv6 systemd[1]: Failed to start Lighttpd Daemon.
– Subject: Unit lighttpd.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit lighttpd.service has failed.

– The result is failed.
Dec 17 18:37:24 daqsrv6 systemd[1]: Unit lighttpd.service entered failed state.

you disabled the dump1090-fa instead of dump1090 config file

sudo lighty-disable-mod dump1090
sudo lighty-enable-mod dump1090-fa
service lighttpd force-reload

do this. don’t mistype :slight_smile:

@wiedehopf
The folder /etc/lighttpd/conf-available/ should have following two files.

88-dump1090-fa-statcache.conf
89-dump1090-fa.conf

I think the file 89-dump1090-fa.conf is missing, possibly did not get installed during installation of dump1090-fa.

@VE3SJK
Please post the output of following command:

ls /etc/lighttpd/conf-available/

.

I was talking conf-enabled folder not conf-available.
And that folder only has those files after you enable them with lighty-enable-mod.

Running

sudo lighty-enable-mod dump1090-fa-statcache

is a good idea as well but the webpage usually works without it. (maybe with some hiccups)

Edit: this command and another reload will fix those ajax errors

Yes one file was missing i had to copy dump1090-fa into the mods available folder and rename it 89-dump1090 i was then able to disable mod dump1090 which finally got that file out of the available list. Then i enabled dump1090-fa and restarted the server. I can not see the page as normal,

I see another issue when watching the page, i am getting two orange pop up boxes at the bottom of the page on a regular basis but they pop up and disappear to quickly to read the error. Both have something to do with ajax calls. Is there a way to log those pop ups or read a log if already logged somewhere

here is my ls now

ls /etc/lighttpd/conf-enabled
89-dump1090-fa.conf 90-javascript-alias.conf

ls /etc/lighttpd/conf-enabled
88-dump1090-fa-statcache.conf 89-dump1090-fa.conf 90-javascript-alias.conf

If the disable-mod doesn’t work you can just delete the file

sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf

But i guess you found a workaround already :wink:

Also enablying the statcache mod will fix the ajax errors.

sudo lighty-enable-mod dump1090-fa-statcache
service lighttpd force-reload

The errors did seem to go away after enabling statcache option although i have less flights in the view right now, i did notice that one of those errors was showing a syntax error in a file somewhere it just disappeared before i could fully read it. It seems to be when i had greater than 70 planes in view. Right now i have 40. Is there a place to log those pop ups to have a look at what it was saying if it comes back.

Those errors are parsing errors for the json file that happen when the webserver does not realize the file was updated and cuts off the file or something.
(Also make sure you did the lighttpd reload)

Apart from that you can always make a screenshot of the error.

thank you to all those that replied to the problem seems everything is up and running now, its nice to actually see a map again since my previous installation was stuck on the “for development only” watermark on the old google maps.