Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Browser Connections to RPi Stopped Working

  1. #1
    Passenger
    Join Date
    Apr 2015
    Posts
    5

    Browser Connections to RPi Stopped Working

    The browser connections to my RPi stopped working. The connection to <host name>:8754 still works but the connection to <host name>/dump1090/gmap.html fails with a 404 error. The same happens to the graphs1090 page. If I use the ip address instead of the host name the results are the same. The Rpi is still feeding data to multiple sites without any issues. Is there a way to diagnose and fix the problem? I'm a total Raspbian noob.

  2. #2
    Captain
    Join Date
    Apr 2018
    Posts
    752
    What did you do before it stopped working?

    Anyway let's check this:

    ls /etc/lighttpd/conf-enabled/

    sudo journalctl -u lighttpd --no-pager

  3. #3
    Passenger
    Join Date
    Apr 2015
    Posts
    5
    Quote Originally Posted by wiedehopf View Post
    What did you do before it stopped working?

    Anyway let's check this:

    ls /etc/lighttpd/conf-enabled/

    sudo journalctl -u lighttpd --no-pager
    I updated from Stretch to Buster. I'm not sure of all the other things. I ran the command for the graphics1090 install, but I believe it didn't complete. I did the same stuff on my other RPi (CS3) and it all works. CS3 runs 1 dongle and CS5 runs two dongles.

    I have no idea what the command output means other than something is very wrong.
    Code:
    pi@CS5:~ $ ls /etc/lighttpd/conf-enabled/
    88-dump1090-fa-statcache.conf  89-dump1090-2.conf     89-dump1090-fa.conf
    88-graphs1090.conf             89-dump1090.conf.save  90-javascript-alias.conf
    pi@CS5:~ $
    
    I truncated the beginning of the log due to posting size constraints.
    
    Jul 28 10:14:58 CS5 systemd[1]: Starting Lighttpd Daemon...
    Jul 28 10:14:58 CS5 lighttpd[2971]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
    Jul 28 10:14:58 CS5 lighttpd[2971]: 2019-07-28 10:14:58: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090-2.conf line: 34 pos: 1 parser failed somehow near here: (EOL)
    Jul 28 10:14:58 CS5 lighttpd[2971]: 2019-07-28 10:14:58: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Jul 28 10:14:58 CS5 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Jul 28 10:14:58 CS5 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Jul 28 10:14:58 CS5 systemd[1]: Failed to start Lighttpd Daemon.
    Jul 28 10:14:58 CS5 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Jul 28 10:14:58 CS5 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 8.
    Jul 28 10:14:58 CS5 systemd[1]: Stopped Lighttpd Daemon.
    Jul 28 10:14:58 CS5 systemd[1]: Starting Lighttpd Daemon...
    Jul 28 10:14:59 CS5 lighttpd[2994]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
    Jul 28 10:14:59 CS5 lighttpd[2994]: 2019-07-28 10:14:58: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090-2.conf line: 34 pos: 1 parser failed somehow near here: (EOL)
    Jul 28 10:14:59 CS5 lighttpd[2994]: 2019-07-28 10:14:58: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Jul 28 10:14:59 CS5 systemd[1]: Failed to start Lighttpd Daemon.
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 9.
    Jul 28 10:14:59 CS5 systemd[1]: Stopped Lighttpd Daemon.
    Jul 28 10:14:59 CS5 systemd[1]: Starting Lighttpd Daemon...
    Jul 28 10:14:59 CS5 lighttpd[3029]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
    Jul 28 10:14:59 CS5 lighttpd[3029]: 2019-07-28 10:14:59: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090-2.conf line: 34 pos: 1 parser failed somehow near here: (EOL)
    Jul 28 10:14:59 CS5 lighttpd[3029]: 2019-07-28 10:14:59: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Jul 28 10:14:59 CS5 systemd[1]: Failed to start Lighttpd Daemon.
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 10.
    Jul 28 10:14:59 CS5 systemd[1]: Stopped Lighttpd Daemon.
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Start request repeated too quickly.
    Jul 28 10:14:59 CS5 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Jul 28 10:14:59 CS5 systemd[1]: Failed to start Lighttpd Daemon.
    Jul 28 11:00:11 CS5 systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
    Jul 28 11:00:18 CS5 systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
    Jul 28 11:00:20 CS5 systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
    Jul 28 11:00:24 CS5 systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
    pi@CS5:~ $

  4. #4
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,008
    Despite advice, left @ symbols present.

    Sent from my EML-L09 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  5. #5
    Captain
    Join Date
    Apr 2018
    Posts
    752
    Thanks for greenlighting the post.


    ua549: use the following commands:

    cd /etc/lighttpd/conf-enabled/
    sudo rm 89-dump1090-2.conf 89-dump1090.conf.save
    sudo systemctl restart lighttpd

    Somehow there are bogus configurations left over from dump1090 despite you using dump1090-fa obviously.
    (those commands remove the bogus configuration, then lighttpd should work again)

  6. #6
    Passenger
    Join Date
    Apr 2015
    Posts
    5
    Thanks wiedehoph, unfortunately I still get 404 messages. I'm going to re-image CS5 without FlightRadar24.

    Oblivian has deleted some of my posts and publicly insulted me by stating that I am unable to read non-existent posting rules. As a result I have decided to terminate all feeding to the FlightRadar24 site even though I was ranked in the top 110 contributors worldwide and the top 10 in the US. This is my last post here. I'll see you on Flight Aware.

    UA

  7. #7
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,008
    Quote Originally Posted by ua549 View Post
    Thanks wiedehoph, unfortunately I still get 404 messages. I'm going to re-image CS5 without FlightRadar24.

    Oblivian has deleted some of my posts and publicly insulted me by stating that I am unable to read non-existent posting rules. As a result I have decided to terminate all feeding to the FlightRadar24 site even though I was ranked in the top 110 contributors worldwide and the top 10 in the US. This is my last post here. I'll see you on Flight Aware.

    UA
    I'm sorry. Where?

    I've not deleted any.

    And wiedhopf mentioned in his replies a few times not to us @s. As it will likely be anti spammed.

    Which is also suggested here https://forum.flightradar24.com/thre...-ask-questions!

    NEW USERS TRYING TO PASTE ERRORS/LOGS -
    @, http:// www. , common script/web code (FR24 logs included), or other key characters may trigger moderation and will not show until approved.
    Do NOT post random replies to avoid - Edit code and links to plain text, remove @s, or await approval
    I'm not going to write a novel when I'm on my phone so answers are always going to be short and directive

    There was 3 posts you have made doing @s to try tag people that were sitting in moderation. I can't edit the forum settings. I can't make it not do it. I can only advise people not to use @s and have in as many places I can.



    Sent from my EML-L09 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  8. #8
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,008
    And for the record. The one you quoted also got slammed.

    But hey. Take it out on someone who can't do anything about it all you like.

    Sent from my EML-L09 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  9. #9
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,768
    Quote Originally Posted by wiedehopf View Post
    What did you do before it stopped working?
    ....

    if it ain't broke, dont fix it
    Last edited by abcd567; 2019-07-29 at 00:00.

  10. #10
    Captain
    Join Date
    Apr 2018
    Posts
    752
    Well, no need to blame Oblivian really.
    That "despite advice" wasn't meant as an insult, i'm sure.
    The forum antispam is annoying for everyone, no use getting angry about it with moderators or newbies.

    Your post didn't get deleted by Oblivian. Instead it was never really posted because of the stupid forum anti-spam.
    (you quoted the @ sign and have less than 10 posts, which is the criterion for "new")

    It's probably just best to start with a fresh Buster image indeed.
    Could have most likely fixed the problems, but it would have taken some more trial and error.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •