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)
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.
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:~
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