My 192.168.0.97:8080 dump stopped working


#1

For about the last 2 weeks my dump from my unit has not worked, although I am still live with my feeds to FA. I have been having some IP address issues on my local net and did replace by modem, but that is not a current problem. All else is working fine on my system. Any thoughts would be appreciated. (I have, of course, rebooted my unit several times).

Steve Cantrill


#2

Your stats page (flightaware.com/adsb/stats/user/scantrill) reports a different local IP for your piaware, not .97. Probably the modem change has caused a different local IP to be assigned to your piaware, so you’re just looking at the wrong address. Try following the “view live data” link on the stats page.


#3

Great. Thanks!


#4

Hi.
I have this issue also. My local page 192.168.0.5:8080, dont work.
The IP is correct.
Thanks

Jefferson


#5

Couple of suggestions:

  1. Call the dump from your ADS-B stats page… then you know the IP is correct.
  2. Reboot your piaware and then re-check your IP. If there are doubly assigned IPs, that could cause a problem.
    Good luck.

#6

Hi.

The IP is correct.
It looks like lighttpd does not go up.
Thanks.

1 ?        00:00:21 systemd
2 ?        00:00:00 kthreadd
3 ?        00:00:05 ksoftirqd/0
6 ?        00:00:00 migration/0
7 ?        00:00:03 watchdog/0
8 ?        00:00:00 migration/1
9 ?        00:01:07 kworker/1:0

10 ? 00:00:02 ksoftirqd/1
11 ? 00:00:03 watchdog/1
12 ? 00:00:00 migration/2
14 ? 00:00:04 ksoftirqd/2
15 ? 00:00:03 watchdog/2
16 ? 00:00:00 migration/3
17 ? 00:00:00 kworker/3:0
18 ? 00:00:01 ksoftirqd/3
19 ? 00:00:03 watchdog/3
20 ? 00:00:00 cpuset
21 ? 00:00:00 khelper
22 ? 00:00:00 kdevtmpfs
23 ? 00:00:00 netns
24 ? 00:00:00 kworker/0:1
26 ? 00:03:21 kworker/2:1
27 ? 00:00:32 kworker/3:1
28 ? 00:00:01 sync_supers
29 ? 00:00:00 bdi-default
30 ? 00:00:00 kintegrityd
31 ? 00:00:00 crypto
32 ? 00:00:00 kblockd
33 ? 00:00:00 sytem
34 ? 00:00:00 khubd
35 ? 00:00:00 cfg80211
36 ? 00:00:00 rpciod
37 ? 00:00:00 khungtaskd
38 ? 00:00:01 kswapd0
39 ? 00:00:00 vmstat
40 ? 00:00:00 fsnotify_mark
41 ? 00:00:00 nfsiod
42 ? 00:00:00 cifsiod
57 ? 00:00:00 SunxiDisCommit
58 ? 00:00:00 kapmd
59 ? 00:00:00 spi.0
67 ? 00:03:12 cfinteractive
68 ? 00:00:01 kworker/u:2
69 ? 00:00:00 kworker/u:3
71 ? 00:13:31 kworker/0:2
72 ? 00:00:13 mmcqd/0
73 ? 00:00:56 hdmi proc
74 ? 00:00:00 deferwq
75 ? 00:00:00 thermal_wq
77 ? 00:00:00 devfreq_wq
115 ? 00:00:00 kworker/1:2
136 ? 00:00:00 jbd2/mmcblk0p1-
137 ? 00:00:00 ext4-dio-unwrit
173 ? 00:00:00 mali-pmm-wq
179 ? 00:00:00 kauditd
207 ? 00:00:01 systemd-udevd
235 ? 00:01:34 haveged
285 ? 00:04:30 systemd-journal
491 ? 00:01:03 accounts-daemon
492 ? 00:00:00 avahi-daemon
496 ? 00:00:00 avahi-daemon
497 ? 00:00:01 systemd-logind
540 ? 00:00:01 cron
547 ? 00:01:05 rsyslogd
563 ? 00:00:05 dbus-daemon
614 ? 00:03:50 NetworkManager
640 ? 00:00:00 nodm
648 tty7 00:00:06 Xorg
691 ? 00:00:00 dhclient
731 ? 00:00:16 sshd
743 ? 00:00:03 polkitd
779 ? 00:00:00 nodm
806 ? 00:00:00 systemd
830 ? 00:00:00 (sd-pam)
872 ? 00:00:00 dnsmasq
927 ? 00:00:45 ntpd
947 ? 00:00:00 sh
948 tty1 00:00:00 agetty
951 ? 00:00:00 sh
962 ttyS0 00:00:00 agetty
1008 ? 00:00:02 ssh-agent
1011 ? 00:00:00 dbus-launch
1012 ? 00:00:01 dbus-daemon
1030 ? 00:00:00 xfce4-session
1051 ? 00:00:00 xfconfd
1055 ? 00:00:02 xfwm4
1059 ? 00:00:16 xfce4-panel
1061 ? 00:00:00 Thunar
1063 ? 00:00:13 xfdesktop
1064 ? 00:00:01 pasystray
1068 ? 00:00:00 xfsettingsd
1069 ? 00:00:02 blueman-applet
1073 ? 00:00:00 polkit-gnome-au
1080 ? 00:00:00 pulseaudio
1082 ? 00:00:00 gvfsd
1087 ? 00:00:00 gvfsd-fuse
1111 ? 00:00:00 gvfs-udisks2-vo
1118 ? 00:00:01 udisksd
1156 ? 00:00:00 gvfs-gphoto2-vo
1160 ? 00:00:00 panel-6-systray
1164 ? 00:00:00 panel-2-actions
1166 ? 00:00:00 gvfs-mtp-volume
1172 ? 00:00:00 gvfs-goa-volume
1177 ? 00:00:00 gvfs-afc-volume
1188 ? 00:00:00 gvfsd-trash
1221 ? 00:00:00 gvfsd-metadata
1258 ? 00:00:00 gconf-helper
1260 ? 00:00:00 gconfd-2
1465 ? 00:00:00 obexd
1493 ? 17:07:02 dump1090-fa
12050 ? 00:00:09 faup1090
13120 ? 00:00:00 gnome-keyring-d
13906 ? 00:00:00 sshd
13908 ? 00:00:00 systemd
13909 ? 00:00:00 (sd-pam)
13987 pts/0 00:00:01 bash
14072 pts/0 00:00:00 ps
20412 ? 00:00:00 dhclient
26533 ? 00:02:32 piaware
26548 ? 00:09:02 fa-mlat-client
29117 ? 00:00:00 kworker/2:0

eth0 Link encap:Ethernet HWaddr xx-xx-xx-xx-xx-xx
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::b447:d8ff:feec:7d4f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:227107 errors:0 dropped:0 overruns:0 frame:0
TX packets:158398 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:88616624 (88.6 MB) TX bytes:25693796 (25.6 MB)
Interrupt:114


#7

I was having this same issue.

I’m running apache and not lighttpd. I reconfigured lighttpd to use port 81 (since apache is on 80) and the live stats showed up as another site served by lighttpd on port 8080.


#8

dump1090-fa does nothing to listen on port 8080. You must arrange for a webserver to serve the map there if you want it. The package provides a lighttpd configuration fragment that does this, but if you are using another webserver such as apache you need to configure that yourself.