"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
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.
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 ā¦
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
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:
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.
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!
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.
I use the MAC binding facility on my router to bind the Piās MAC address to a fixed IP. Itās quite handy having a one stop shop to manage all my fixed IPs.
I went a bit further in having the first 20 IP addresses on the router subnet outside of the DHCP scope, reserved for fixed IPs
Aye thatās a good way to manage it if the DHCP interface supports it ā you end up with permanently assigned dymanic IPs for the hosts that need it, so they can just stay configured as DHCP clients as standard, and you also have a small range reserved for genuine static IPs if needed.
Exactly - it seemed the most fuss free way of doing it. Also handy when firing up a cloned card on a test Pi as itās not configured for a fixed IP in the image, clashing with a live device. Admittedly, Iām not sure how common MAC address binding is in āhomeā routers these days.
Also it is not good idea for assigning fixed IP to distros in Virtual Machine.
I installed Red Hat Enterprise Linux x86_64 and through router I assigned it a fixed IP using MAC. As I was experimenting to build & install dump1090 and piawre from source-code, after lots of trials-and-errors, I had to delete itās hard disk (RHEL 8.1.vdi), then recreate a fresh hard disk. This I had to do several times, and each time VM assigned it a new MAC.
I then stopped configuring fixed IP in router. Instead I created a fixed IP through Gnomeās Settings window.
I am using a AVM router (popular in Germany) with the option āAlways assign the same IP adressā after i set it fixed for this device. This is a āquasiā fixed IP.
Whenever the device starts i am getting exactly this one. And even a reinstall of the RPi does not matter.
And i did not need to reset the router to factory the last three years
