Announcement

Collapse
No announcement yet.

dump1090-fa.service failing

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

  • dump1090-fa.service failing

    At midday my Pi stopped feeding FR24 (and FlightAware)
    restart dump1090-fa fails, even after rebooting.


    The contents of the recommended 'dumps' are copied below. Would someone help me interpret please?

    pi@raspberrypi:~ $ systemctl status dump1090-fa.service
    ● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
    Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/dump1090-fa.service.d
    └─bias-t.conf
    Active: activating (auto-restart) (Result: exit-code) since Thu 2020-04-09 18:45:37 BST; 6s ago
    Docs: https://flightaware.com/adsb/piaware/
    Process: 672 ExecStartPre=/home/pi/rtl_biast/build/src/rtl_biast -b 1 (code=exited, status=1/FAILURE)

    And

    journalctl -xe

    -- A start job for unit dump1090-fa.service has finished with a failure.
    --
    -- The job identifier is 1777 and the job result is failed.
    Apr 09 18:55:44 raspberrypi sudo[1093]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl restart dump1090-fa
    Apr 09 18:55:44 raspberrypi sudo[1093]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
    Apr 09 18:55:44 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
    -- Subject: A stop job for unit dump1090-fa.service has finished
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- A stop job for unit dump1090-fa.service has finished.
    --
    -- The job identifier is 1835 and the job result is done.
    Apr 09 18:55:44 raspberrypi systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)...
    -- Subject: A start job for unit dump1090-fa.service has begun execution
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- A start job for unit dump1090-fa.service has begun execution.
    --
    -- The job identifier is 1835.
    Apr 09 18:55:44 raspberrypi dump1090-fa[1100]: No supported devices found.
    Apr 09 18:55:44 raspberrypi systemd[1]: dump1090-fa.service: Control process exited, code=exited, status=1/FAILURE
    -- Subject: Unit process exited
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- An ExecStartPre= process belonging to unit dump1090-fa.service has exited.
    --
    -- The process' exit code is 'exited' and its exit status is 1.
    Apr 09 18:55:44 raspberrypi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
    -- Subject: Unit failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
    Apr 09 18:55:44 raspberrypi systemd[1]: Failed to start dump1090 ADS-B receiver (FlightAware customization).
    -- Subject: A start job for unit dump1090-fa.service has failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- A start job for unit dump1090-fa.service has finished with a failure.
    --
    -- The job identifier is 1835 and the job result is failed.
    Apr 09 18:55:44 raspberrypi sudo[1093]: pam_unix(sudo:session): session closed for user root

  • #2
    looks like this is failing: /home/pi/rtl_biast/build/src/rtl_biast -b 1
    Did you by chance delete that folder / binary?

    Otherwise, test the receiver: https://github.com/wiedehopf/adsb-wi...Debug-commands

    Comment


    • #3
      I haven't touched it for months. I'll take a look at the test link you posted.

      Thank you

      Comment


      • #4
        Can you show the output for this:

        pgrep -a dump1090

        Comment


        • #5
          I'm just off up into the loft (attic). Looks like its a hardware issue as ./rtl_biast -b 1 reports something to do with the hardware not being found.

          I am a little paranoid that the SD card will be the first thing to fail, and always want to suspect that, but doesn't seem to be implicated here - yet. I'll report back on findings soon.

          Comment


          • #6
            Seemed to be the short USB cable that connects the RTL dongle to the Pi. I've replaced it with another I have and all seems fine. No idea how that might have 'failed'. Must be some tarnish.

            Anyhow all good now.

            Thank you wiedehopf for taking the time.

            Comment

            Working...
            X