Dump1090 mutability 1-15 on Mint linux

[Space Pilot]

I blacklisted Ubuntu's support for RTL-SDR DBV stick and re-booted. Now dump1090 seems to be running. I can see about 35 flights on terminal console. But still no planes on map.

Problem fetching data from dump1090.
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date.

May be wrong port number(s)?

[abcd567]

First try this:
Clear Browser Cache (Ctrl+Shift+Delete) and Reload Browser (Ctrl+F5)

If you still get the warning "maybe dump1090in no longr running", then try this:

# List all the running instances of dump1090-mutability
pgrep -l dump1090

# Stop all instances of dump1090-mutability
sudo killall dump1090-mutability
sudo killall dump1090

# Restart single instance of dump1090-mutability
sudo systemctl restart dump1090-mutability

Open browser and point to
localhost/dump1090/gmap.html

Clear Browser Cache (Ctrl+Shift+Delete) and Reload Browser (Ctrl+F5)

[wiedehopf]

Yeah when you stop the service and run it on the console in interactive mode it won't provide the data for the webinterface.

[abcd567]

Did you execute BUG FIX in step (7) of following thread?
How to Install dump1090-mutability_1.15~dev on RPi

[Space Pilot]

I tried everything, including the bug fix.

When I start sudo systemctl restart dump1090-mutability apparently nothing happens.

pgrep -l dump1090 returns nothing

The only thing that starts is dump1090-mutability --interactive which produces a text console output but no graphics.

pgrep -l dump1090 sez:

7974 dump1090-mutabi

[wiedehopf]

Then check the log:

cat /var/log/dump1090-mutability.log

Most likely your configuration is bad because starting it from the command line works.
Maybe run this to configure it:

sudo dpkg-reconfigure dump1090-mutability

[Oblivian]

If you quit the interaction view, and pgrep still reports it as above. You need to kill it.

Not exiting correct - It should show nothing on pgrep.

When you try restarting it will be stuck with the err -6.

Before starting service you need NO pgrep (running copy) responce.

Sent from my EML-L09 using Tapatalk

[Space Pilot]

Log is empty.

Reconfigured:

root@T510:~# sudo dpkg-reconfigure dump1090-mutability
Enabling lighttpd integration..
already enabled
Run "service lighttpd force-reload" to enable changes
Restarting lighttpd..
insserv: warning: script 'mobile-broadband-connect' missing LSB tags and overrides
root@T510:~#

please explain 'mobile-broadband-connect'

[Space Pilot]

If you quit the interaction view, and pgrep still reports it as above. You need to kill it.

Not exiting correct - It should show nothing on pgrep.

When you try restarting it will be stuck with the err -6.

Before starting service you need NO pgrep (running copy) responce.

Sent from my EML-L09 using Tapatalk

I wrote that systemctl restart dump1090-mutability does not start the process so it's ok that pgrep doesn't list it.

Only dump1090-mutability --interactive would start a process called dump1090-mutabi that could be found by pgrep as long it was active, i.e. until I stopped it by CTRL-C.

[wiedehopf]

No idea what that lighttpd message means, but it's just a warning.

When configuring which path did you specify for logging when configuring it?
Check that log.

You should also enable automatic starting.

Could it be that you are just using an ancient version of Linux Mint?
Can't you upgrade that?

If there is still nothing in the log then the init script is not working for whatever reason.
I suppose you could run it manually as root from the command line and specify the json directory:

/run/dump1090-mutability

Check dump1090-mutability --help on how to do that.
Then the map should work even if you start it manually.

[Oblivian]

You didn't stipulate you were running it in a second window while interactive was running.

Most users will run 1. As no GUI.

Sent from my EML-L09 using Tapatalk

[Space Pilot]

Did I define a logging path? At what step?

Automatic starting - that's for later with the Raspberry Pi. I'm using my home office laptop with dozens of open documents and tasks, I'm rebooting say, every couple of weeks.

This is my System: Host: T510 Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Cinnamon 3.8.9 Distro: Linux Mint 19 Tara

/run/dump1090-mutability
-su: /run/dump1090-mutability: File or directory not found

Thanks for the --help hint. I'll check that tomorrow.

[wiedehopf]

Do the dpkg-reconfigure again.
Activate the automatic start otherwise the service won't run at all.

Also defining a log path during that dpkg-reconfigure doesn't hurt when it asks for it.

Or is the dpkg-reconfigure not even working?
(sudo dpkg-reconfigure dump1090-mutability)

[Space Pilot]

ok, I'll define a log path and autostart. Tomorrow, need som sleep now.

Thanks a lot!

[abcd567]

On Intel PC / Oracle VM / Raspbian x86
Note:
Do not get confused by "pi@raspberry:~ $". The hardware is NOT Raspberry PI.
The Raspbian x86 uses same naming as its Raspberry Pi version uses

Dump1090-mutability installed by method given in this post:
How to Install dump1090-mutability_1.15~dev on RPi

pi@raspberry:~ $ sudo find / -name dump1090-mutability.service 

find: ‘/run/user/1000/gvfs’: Permission denied
/run/systemd/generator.late/dump1090-mutability.service
/run/systemd/generator.late/graphical.target.wants/dump1090-mutability.service
/run/systemd/generator.late/multi-user.target.wants/dump1090-mutability.service
/sys/fs/cgroup/devices/system.slice/dump1090-mutability.service
/sys/fs/cgroup/pids/system.slice/dump1090-mutability.service
/sys/fs/cgroup/systemd/system.slice/dump1090-mutability.service

pi@raspberry:~ $ cat /run/systemd/generator.late/dump1090-mutability.service

# Automatically generated by systemd-sysv-generator

[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/dump1090-mutability
Description=LSB: dump1090 daemon (mutability variant)
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=remote-fs.target
After=network-online.target
Wants=network-online.target

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/init.d/dump1090-mutability start
ExecStop=/etc/init.d/dump1090-mutability stop

NOTE:
(1) No service file is installed in /lib/systemd/system/ by the .deb package installer. Only init file is installed.
(2) The service file is generated by systemd-sysv-generator from dump1090-mutability's init file
(3) The init file is:
/etc/init.d/dump1090-mutability