Announcing PiAware 3.8.1!

Is the one with 3.8.0 a Pi 4?

I seem to recall @obj saying that the ~bpo version was for the earlier Pi hardware? I have a 3B+, and that’s what mine shows.

bpo means something with back port to make it Stretch compatible as far as i remember.

But i have the same result while looking on my two devices. the 3B is on 3.8.0-bpo while the 4B shows 3.8.0 only.
Both are on Buster
the command "sudo apt dist-upgrade worked on 4B only. But as long as both are operating, i don’t care…

All of my RPis are 3B+

3.8.0~bpo9+1 is the Stretch package.

If you installed the 3.7.2 Stretch version on a Buster sdcard before Buster support was released, then upgraded to 3.8.0, then you should follow the instructions in the top post to get the correct repository package and upgrade to the Buster packages.

I’m tempted to purge and reload all three systems with fresh Raspbian and PiAware software (3.8.0). I just don’t want to lose my FA data over the last year.

I now followed the instructions on my RPi 3B (uninstall and reinstall) and now the device is also on V3.8.0

Thank you for these instructions!

"Cannot load plugin mod_setenv more than once, please fix your config"
Is this serious, or should be ignored?

please scroll right to see the in full

pi@piaware:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"

pi@piaware:~ $ sudo journalctl --no-pager -u lighttpd
-- Logs begin at Fri 2020-01-24 10:12:16 UTC, end at Fri 2020-01-24 18:53:40 UTC. --
Jan 24 10:12:34 piaware systemd[1]: Starting Lighttpd Daemon...
Jan 24 10:12:37 piaware lighttpd[587]: 2020-01-24 10:12:34: (plugin.c.190) Cannot load plugin mod_setenv more than once, please fix your config (lighttpd may not accept such configs in future releases)
Jan 24 10:12:37 piaware systemd[1]: Started Lighttpd Daemon.
Jan 24 10:12:39 piaware lighttpd[716]: 2020-01-24 10:12:37: (plugin.c.190) Cannot load plugin mod_setenv more than once, please fix your config (lighttpd may not accept such configs in future releases)

It might cause problems with some things - specifically it was hindering the loading of history files in tar1090. I found it was enabled twice in different .conf files in /etc/lighttpd, once in the dump1090-fa one and once in its own file that contained only that option. Deleted the duplicate and restarted lighttpd and everything works properly again.

Can you please tell me exact steps to do it?
I am facing problem in Fedora fetching files ( wget http://localhost/dump1090-fa/data/aircraft.json). Connects, but says Forbidden 403. May be what you have done will help on Fedora also

Try this to find out where the duplication is:

grep mod_setenv /etc/lighttpd/conf-enabled/*.conf

It should return the files which have that option in them. Then either edit one of them to remove that line or if it’s defined in its own conf file, just remove that one.

If I remember what @wiedehopf told me correctly, it’s possible that dump978 and dump1090 are both defining that option.

Not sure if the 403 error you are seeing is as a result of that though - could be file permissions or server config causing that. Double check the lighttpd user (www-data on raspbian, but could well be different on Fedora) has access.

2 Likes

The tar1090 install script fixes that issue if for Debian/Raspbian lighttpd installs.

You don’t have a duplicate mod_setenv on Fedora.

It’s a completely different problem.

Why don’t you install nginx and use the tar1090 interface exclusively, it provides an nginx configuration to put into the server section of /etc/nginx/sites-enabled/default

Some googling in regards to your Fedora issue: How to Disable SELinux Temporarily or Permanently

I’d suspect lighttpd is just not meant for Fedora …

1 Like

Tanks @caius & @wiedehopf for help.

Will try your tips on Fedora tonight.

@wiedehopf: I have already decided to uninstall lighttpd and install nginx, was going to do this tonight :slight_smile:

Can I just add Buster to my current SD card setup or do I need to start from scratch ?
Where can I find the code to install buster ?
Have been live for years and now I have no tracking.
Jpdies

Best to download the current sd-card image and write it to the sd-card, just start with number 2 on this page:
PiAware - build your own ADS-B ground station for integration with FlightAware - FlightAware

Then when before you put the sd-card into the RPi, add the feeder-id to your configuration:

For Beginners - How to Get Back Existing Station Number in A Fresh Install - #8 by abcd567

I wasted over 2 hours trying to get the pi to use a static IP - very frustrating. Honestly, I understand that they are trying to make it easier with the piaware-config.txt file but really? At least test it and release the bug fix immediately!

Two things:

  1. the line “wired-type static” is missing from the sample piaware-config.txt file. It should at least be there and commented out as is standard practice.
  2. generate-network-config has the stated bug, I fixed it, rebooted and it still didn’t work. Manually running generate-network-config gave another error (I think because it wasn’t called in the proper sequence when I invoked from the command line)

So, I gave up and renamed generate-network-config to generate-network-config.f**kme. I was then able to set the dhcpcd.conf file with a static IP and I finally got my static IP!

SO DAMN FRUSTRATED (and I’m an old UNIX guy!).

Just use Raspbian Lite then.

Never seen the appeal of the sd-card images.
(at least for those who can manage to set up Raspbian Lite)

It’s fixed in 3.8.1 but no idea when that’s being released. In the meantime can section 3 of the PiAware build instructions please highlight the bug and the workaround?

[ Workaround: Enable SSH and configure initially as dynamic IP. Apply fix as detailed by @nu3e. Then configure as static IP as originally desired. ]

I’d like to see all the piaware-config.txt options (and any hidden ones not listed there) placed into the file, commented out and explained in there, so they can be uncommented and edited as needed.

[Copied to feature requests]

1 Like