Announcement

Collapse
No announcement yet.

FR24 stopped; ExecStart=/usr/bin/fr24feed (code=killed, signal=SEGV)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • FR24 stopped; ExecStart=/usr/bin/fr24feed (code=killed, signal=SEGV)

    Hi there,

    since this morning FR24 wont work and i have no idea, whats happened.

    If i use "sudo service fr24feed status" i get:

    ● fr24feed.service - Flightradar24 Decoder & Feeder
    Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
    Active: failed (Result: signal) since Thu 2019-02-28 14:52:41 UTC; 1min 14s ago
    Process: 683 ExecStart=/usr/bin/fr24feed (code=killed, signal=SEGV)
    Process: 678 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=0/SUCCESS)
    Process: 672 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
    Process: 666 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
    Main PID: 683 (code=killed, signal=SEGV)

    Feb 28 14:52:41 raspberrypi systemd[1]: fr24feed.service: Failed with result 'signal'.
    Feb 28 14:52:41 raspberrypi systemd[1]: fr24feed.service: Service hold-off time over, scheduling restart.
    Feb 28 14:52:41 raspberrypi systemd[1]: Stopped Flightradar24 Decoder & Feeder.
    Feb 28 14:52:41 raspberrypi systemd[1]: fr24feed.service: Start request repeated too quickly.
    Feb 28 14:52:41 raspberrypi systemd[1]: Failed to start Flightradar24 Decoder & Feeder.
    Feb 28 14:52:41 raspberrypi systemd[1]: fr24feed.service: Unit entered failed state.
    Feb 28 14:52:41 raspberrypi systemd[1]: fr24feed.service: Failed with result 'signal'.

    What can i do? And please, as easy as possible, i am not the youngest and my last englisch lesson is 30 years ago.

    As additional information: FlightAware and my own radar with ip is running.

    Thanks and greetings
    Stefan

  • #2
    It is crashing on start for an unknown reason.

    Let's check the config with

    cat /etc/fr24feed.ini
    (redact the key)

    Also do a reboot:
    sudo reboot

    Comment


    • #3
      Here is the result:

      pi@raspberrypi:~ $ cat /etc/fr24feed.ini
      receiver="avr-tcp"
      fr24key="XXX" (The key is correct)
      host="192.168.1.XX:30002" (IP is correct)
      path="/usr/bin/dump1090"
      bs="yes"
      raw="yes"
      logmode="1"
      procargs="--net --net-bi-port 30104"
      windowmode="0"
      logpath="/var/log/fr24feed"
      mpx="no"
      mlat="yes"
      mlat-without-gps="yes"

      After reboot the same issue.
      ExecStart=/usr/bin/fr24feed (code=killed, signal=SEGV)
      raspberrypi systemd[1]: fr24feed.service: Failed with result 'signal'.
      raspberrypi systemd[1]: Failed to start Flightradar24 Decoder & Feeder.

      What irritates me: FlightAware and adsbScope are working well.

      Comment


      • #4
        You are using a network source. Presumably from the other feeders. They will also be opening ports and have their own argument's set. Fr2r won't like this as you have them turned on too.

        Remove path,
        Adjust to beast tcp
        127.0.0.1:30005
        Turn off base station out
        Turn off raw out


        Sent from my EML-L09 using Tapatalk
        Last edited by Oblivian; 2019-02-28, 18:36.
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #5
          could you try this config:
          (click the View link)
          Code:
          receiver="beast-tcp"
          fr24key="XXXXXXXXXXXXXXX"
          host="127.0.0.1:30005"
          bs="no"
          raw="no"
          logmode="1"
          logpath="/var/log/fr24feed"
          mlat="yes"
          mlat-without-gps="yes"
          use-http=yes
          http-timeout=20
          after changing the config just do a reboot:
          sudo reboot

          If that doesn't help maybe take a look at the log file:

          tail -n60 /var/log/fr24feed/fr24feed.log

          Comment


          • #6
            I tried but the same mistake.

            Seems that the card has a defect because i cant make any updates and i cant edit the config too. I only get error messages. So I will format and re-play it.

            Thanks again for your help.

            Greetings
            Stefan

            Comment


            • #7
              Originally posted by Nopileos View Post
              I tried but the same mistake.

              Seems that the card has a defect because i cant make any updates and i cant edit the config too. I only get error messages.
              The Pi24 image has "read-only file system". That is why it cannot be updated or edited, and gives error messages when attempted to edit/upgrade.

              You can change read-only file system temporarily to read & write system
              Code:
              sudo mount -o remount,rw /      
              
              sudo chmod a+rw /etc/fr24feed.ini
              Now you will be able to make updates and edit config file.

              NOTE: The above command makes file system read-write temporarily only. When Pi is rebooted, it will again become default read-only. To edit or update after reboot, you will have to issue above command again.
              .
              Last edited by abcd567; 2019-03-01, 07:15.

              Comment


              • #8
                Actually a segfault usually implies a very rare error case. (Unless the application is very buggy, but i haven't seen a ton of segfaults on this forum)

                If you are running a Pi24 image then the readonly described by abcd567 might be the problem, but it seems unlikely you wouldn't know about the readonly fact after install other feeders.

                If you are running another sd-card image (Raspbian or piaware) then it is quite likely depending on the error that the sd-card itself is faulty.
                But reformatting is worth a try.

                Just be prepared that you might need a new sd-card.

                Comment


                • #9
                  I have completely rebuilt the system and everything works fine.

                  An update has probably shot something and my repair attempts had only made it worse.

                  Thanks again for the patience und help.

                  Comment

                  Working...
                  X