FlightAware Discussions

PiAware 5.0 Update Problems

I updated to PiAware 5.0 and somehow lighttpd.service is now failing. Here is the info, but I don’t know what to do about it.

I updated 6 similar Pi’s and only this one has an issue. The others work perfectly.

See "systemctl status lighttpd.service" and "journalctl -xe" for details.
ERROR on line number 175



sudo systemctl status lighttpd.service
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2021-03-11 16:19:01 EST; 10min ago
  Process: 7843 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEP

Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Mar 11 16:19:01 cs1 systemd[1]: Stopped Lighttpd Daemon.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Start request repeated too quickly.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Mar 11 16:19:01 cs1 systemd[1]: Failed to start Lighttpd Daemon.



sudo journalctl -xe
Mar 11 16:30:01 cs1 sudo[11430]:       pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/bash vnstat
Mar 11 16:30:01 cs1 sudo[11431]:       pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/bash starti
Mar 11 16:30:01 cs1 sudo[11431]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 11 16:30:01 cs1 sudo[11430]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 11 16:30:01 cs1 sudo[11437]:     root : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/vnstati -hs
Mar 11 16:30:01 cs1 sudo[11437]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 11 16:30:01 cs1 sudo[11437]: pam_unix(sudo:session): session closed for user root
Mar 11 16:30:01 cs1 sudo[11431]: pam_unix(sudo:session): session closed for user root
Mar 11 16:30:01 cs1 CRON[11426]: pam_unix(cron:session): session closed for user pi
Mar 11 16:30:01 cs1 sudo[11439]:     root : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/vnstati -d
Mar 11 16:30:01 cs1 sudo[11439]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 11 16:30:01 cs1 sudo[11439]: pam_unix(sudo:session): session closed for user root
Mar 11 16:30:01 cs1 sudo[11441]:     root : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/vnstati -m
Mar 11 16:30:01 cs1 sudo[11441]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 11 16:30:01 cs1 sudo[11441]: pam_unix(sudo:session): session closed for user root
Mar 11 16:30:01 cs1 sudo[11443]:     root : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/vnstati --t
Mar 11 16:30:01 cs1 sudo[11443]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 11 16:30:01 cs1 sudo[11443]: pam_unix(sudo:session): session closed for user root
Mar 11 16:30:01 cs1 sudo[11430]: pam_unix(sudo:session): session closed for user root
Mar 11 16:30:01 cs1 CRON[11427]: pam_unix(cron:session): session closed for user pi
Mar 11 16:30:13 cs1 sudo[11128]: pam_unix(sudo:session): session closed for user root
Mar 11 16:30:50 cs1 sudo[11744]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/journalctl -x
Mar 11 16:30:50 cs1 sudo[11744]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
lines 2614-2636/2636 (END)

I think this is already being discussed here

1 Like

If you have tar1090 on that pi just rerun the install script for that.
I’ve added something to the install script that will fix this issue.
It’s not a bug of either tar1090 or dump1090-fa … it’s just an unfortunate combination of factors that produced the issue.

1 Like

I already tried that at 17:43 Eastern Time. Here are the results:

sudo bash -c “$(wget -q -O - https://raw.githubusercontent.com/wiedehopf/tar1090/master/install.sh)”

remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0

From GitHub - wiedehopf/tar1090-db: Database repo for tar1090 using the database maintained by https://github.com/Mictronics/readsb

  • branch master → FETCH_HEAD

HEAD is now at 244f86a db update

From GitHub - wiedehopf/tar1090: Provides an improved webinterface for use with ADS-B decoders readsb / dump1090-fa

  • branch master → FETCH_HEAD

HEAD is now at 775493c workaround for issues with dump1090-fa

I tried it again and got the following error:

sudo bash -c “$(wget -nv -O - https://raw.githubusercontent.com/wiedehopf/tar1090/master/install.sh)”

2021-03-11 17:51:03 URL:https://raw.githubusercontent.com/wiedehopf/tar1090/master/install.sh [15952/15952] → “-” [1]

remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0

From GitHub - wiedehopf/tar1090-db: Database repo for tar1090 using the database maintained by https://github.com/Mictronics/readsb

  • branch master → FETCH_HEAD

HEAD is now at 244f86a db update

From GitHub - wiedehopf/tar1090: Provides an improved webinterface for use with ADS-B decoders readsb / dump1090-fa

  • branch master → FETCH_HEAD

HEAD is now at 775493c workaround for issues with dump1090-fa

Those aren’t errors really.
But there should be more output.

Anyhow let’s check the lighttpd output:

sudo journalctl -u lighttpd | tail -n30
Mar 11 16:19:00 cs1 lighttpd[7829]: 2021-03-11 16:19:00: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 11 16:19:00 cs1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 11 16:19:00 cs1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Mar 11 16:19:00 cs1 systemd[1]: Failed to start Lighttpd Daemon.
Mar 11 16:19:00 cs1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 11 16:19:00 cs1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 3.
Mar 11 16:19:00 cs1 systemd[1]: Stopped Lighttpd Daemon.
Mar 11 16:19:00 cs1 systemd[1]: Starting Lighttpd Daemon...
Mar 11 16:19:01 cs1 lighttpd[7838]: Duplicate array-key '/data/'
Mar 11 16:19:01 cs1 lighttpd[7838]: 2021-03-11 16:19:00: (configfile.c.1296) source: /etc/lighttpd/conf-enabled/89-skyaware.conf line: 41 pos: 1 parser failed somehow near here: (EOL)
Mar 11 16:19:01 cs1 lighttpd[7838]: 2021-03-11 16:19:00: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Mar 11 16:19:01 cs1 systemd[1]: Failed to start Lighttpd Daemon.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 4.
Mar 11 16:19:01 cs1 systemd[1]: Stopped Lighttpd Daemon.
Mar 11 16:19:01 cs1 systemd[1]: Starting Lighttpd Daemon...
Mar 11 16:19:01 cs1 lighttpd[7843]: Duplicate array-key '/data/'
Mar 11 16:19:01 cs1 lighttpd[7843]: 2021-03-11 16:19:01: (configfile.c.1296) source: /etc/lighttpd/conf-enabled/89-skyaware.conf line: 41 pos: 1 parser failed somehow near here: (EOL)
Mar 11 16:19:01 cs1 lighttpd[7843]: 2021-03-11 16:19:01: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Mar 11 16:19:01 cs1 systemd[1]: Failed to start Lighttpd Daemon.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Mar 11 16:19:01 cs1 systemd[1]: Stopped Lighttpd Daemon.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Start request repeated too quickly.
Mar 11 16:19:01 cs1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Mar 11 16:19:01 cs1 systemd[1]: Failed to start Lighttpd Daemon.

Seems my autofix in the install script checked case sensitive so it didn’t do what it’s supposed to do.
Try one more time :slight_smile:

If that doesn’t work just fix it with this command:

sudo mv /etc/lighttpd/conf-available/89-dump1090-fa.conf.dpkg-dist /etc/lighttpd/conf-available/89-dump1090-fa.conf
sudo systemctl restart lighttpd

That should definitely work.

2 Likes

Issue fixed. Thank you. :slight_smile:

On 16494
After attempting piaware/dump1090 5.0 update and reinstalling tar1090 still having trouble with lighttpd

have you tried wiedehopf’s fix 3 posts up?

Updated piaware and dump1090 thru web page.
ran script to reinstall tar1090 still

● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-03-12 12:42:40 EST; 4h 59min ago
Process: 5248 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)

Mar 12 12:42:40 c16494 systemd[1]: lighttpd.service: Control process exited, code=exited status=255
Mar 12 12:42:40 c16494 systemd[1]: Failed to start Lighttpd Daemon.
Mar 12 12:42:40 c16494 systemd[1]: lighttpd.service: Unit entered failed state.
Mar 12 12:42:40 c16494 systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
Mar 12 12:42:40 c16494 systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
Mar 12 12:42:40 c16494 systemd[1]: Stopped Lighttpd Daemon.
Mar 12 12:42:40 c16494 systemd[1]: lighttpd.service: Start request repeated too quickly.
Mar 12 12:42:40 c16494 systemd[1]: Failed to start Lighttpd Daemon.
Mar 12 12:42:40 c16494 systemd[1]: lighttpd.service: Unit entered failed state.
Mar 12 12:42:40 c16494 systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
pi@c16494:~ $
login as: pi
pi@192.168.86.206’s password:
Linux c16494 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Mar 12 12:41:20 2021 from 192.168.86.30
pi@c16494:~

Blockquote

Yes, but have you tried wiedehopf’s fix mentioned in his last post on this topic?

Let’s see which config files there are:

ls /etc/lighttpd/conf-enabled/89*

ls /etc/lighttpd/conf-enabled/89*
/etc/lighttpd/conf-enabled/89-readsb.conf /etc/lighttpd/conf-enabled/89-skyaware978.conf /etc/lighttpd/conf-enabled/89-skyaware.conf
or ls /etc/lighttpd/conf-enabled/89*/etc/lighttpd/conf-enabled/89-readsb.conf / - Pastebin.com

Yeah don’t “update” dump1090-fa when using readsb.
One or the other, not both.

And sudo apt-get purge used with either readsb or dump1090-fa should do the trick … whichever you don’t want to use.

thanks
skyaware is working after sudo apt-get purge readsb tar1090 still unable to connect pi@c16494:~ $ sudo systemctl status lighttpd.service● lighttpd.service - Light - Pastebin.com

You need to rerun the tar1090 install when you change the decoder …

If you get data at /skyaware /tar1090 should be working with that log you showed as well.

If it’s not working … check the log for dump1090-fa then.
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub

Thanks again, like magic things are working this morning, seems like one of the previous browser tabs was stuck and needed to be opened in new browser tab. only exception is one graphs1090 data had a year of history before 5.0 update and now only has 1 day. pastebin with graphs1090 debug output pi@c5660:~ $ sudo journalctl --no-pager -u collectd-- Logs begin at Fri 2021-0 - Pastebin.com many already exists not overwritten messages

Did you run the install script?
Didn’t fix it?