I can’t really pin-point why and looking through the logs don’t really show me anything as they don’t appear to be constant. It’s once in a while but nevertheless there is only one DUMP installed on my PI(s) as far as I’m aware and every few days it stops feeding but PIaware stays connected (although recently within the last few hours my other PI appears to have shut itself off completely).
To resolve this you have to restart the whole device as the commands on flightaware won’t suffice for dump1090-mutability.
Anyone got a clue? It’s definitely mutability related as my SD card flashed with default piaware/dump worked fine for months on end.
So what do the dump1090-mutability logs actually say when it stops? Based on the information you’ve given all I can say is it’s probably power-related because that’s the usual explanation for mysterious crashes.
The default configuration is to log stats hourly. You can configure it to be more frequent if you want.
As you can see the PI never stops running (shown by temp), the system stopped running around 4-5am puu.sh/iqmIo/39fea7dec0.png
dump1090 was running at 05:53BST. What was the next log output after 05:53?
Is there anything unusual in the output of the “dmesg” command? (Look for USB disconnects or “out of memory” reports)
(For comparison, I run three instances of dump1090-mutability and they run for weeks at a time with no problems; if yours are crashing multiple times a day it’s going to be something specific to your setup)
There wasn’t a one after that, it happened again 7 hours ago. at 05:34 was the last dump log made and then it never made it past that.
DMESG:
pi@raspberrypi /var/log $ dmesg
0.000000] Booting Linux on physical CPU 0x0
0.000000] Initializing cgroup subsys cpu
0.000000] Initializing cgroup subsys cpuacct
0.000000] Linux version 3.18.11+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #781 PREEMPT Tue Apr 21 18:02:18 BST 2015
0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
0.000000] Machine model: Raspberry Pi Model B Plus
0.000000] cma: Reserved 8 MiB at 0x1b800000
0.000000] Memory policy: Data cache writeback
0.000000] On node 0 totalpages: 114688
0.000000] free_area_init_node: node 0, pgdat c083d364, node_mem_map db474000
0.000000] Normal zone: 896 pages used for memmap
0.000000] Normal zone: 0 pages reserved
0.000000] Normal zone: 114688 pages, LIFO batch:31
0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
0.000000] pcpu-alloc: [0] 0
0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 113792
0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0x10 bcm2708.serial=0xdf943800 smsc95xx.macaddr=B8:27:EB:94:38:00 bcm2708_fb.fbswap=1 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
0.000000] Memory: 437276K/458752K available (5881K kernel code, 348K rwdata, 1868K rodata, 336K init, 733K bss, 21476K reserved)
0.000000] Virtual kernel memory layout:
0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
0.000000] vmalloc : 0xdc800000 - 0xff000000 ( 552 MB)
0.000000] lowmem : 0xc0000000 - 0xdc000000 ( 448 MB)
0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
0.000000] .text : 0xc0008000 - 0xc07997a0 (7750 kB)
0.000000] .init : 0xc079a000 - 0xc07ee000 ( 336 kB)
0.000000] .data : 0xc07ee000 - 0xc084513c ( 349 kB)
0.000000] .bss : 0xc084513c - 0xc08fc8a8 ( 734 kB)
0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
0.000000] Preemptible hierarchical RCU implementation.
0.000000] NR_IRQS:522
0.000024] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns
0.000072] Switching to timer-based delay loop, resolution 1000ns
0.000356] Console: colour dummy device 80x30
0.001435] console [tty1] enabled
0.001481] Calibrating delay loop (skipped), value calculated using timer frequency… 2.00 BogoMIPS (lpj=10000)
0.001555] pid_max: default: 32768 minimum: 301
0.001932] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
0.001997] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
0.003004] Initializing cgroup subsys memory
0.003097] Initializing cgroup subsys devices
0.003157] Initializing cgroup subsys freezer
0.003211] Initializing cgroup subsys net_cls
0.003263] Initializing cgroup subsys blkio
0.003381] CPU: Testing write buffer coherency: ok
0.003495] ftrace: allocating 19232 entries in 57 pages
0.108349] Setting up static identity map for 0x553398 - 0x5533d0
0.111188] devtmpfs: initialized
0.128717] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
0.131740] pinctrl core: initialized pinctrl subsystem
0.134424] NET: Registered protocol family 16
0.139931] DMA: preallocated 4096 KiB pool for atomic coherent allocations
0.141383] bcm2708.uart_clock = 3000000
0.144336] No ATAGs?
0.144404] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
0.144465] hw-breakpoint: maximum watchpoint size is 4 bytes.
0.144528] mailbox: Broadcom VideoCore Mailbox driver
0.144691] bcm2708_vcio: mailbox at f200b880
0.145142] bcm_power: Broadcom power driver
0.145199] bcm_power_open() → 0
0.145230] bcm_power_request(0, 8)
0.645939] bcm_mailbox_read → 00000080, 0
0.645985] bcm_power_request → 0
0.646187] Serial: AMBA PL011 UART driver
0.646422] dev:f1: ttyAMA0 at MMIO 0x20201000 (irq = 83, base_baud = 0) is a PL011 rev3
1.033220] console [ttyAMA0] enabled
1.096487] SCSI subsystem initialized
1.100620] usbcore: registered new interface driver usbfs
1.106408] usbcore: registered new interface driver hub
1.111911] usbcore: registered new device driver usb
1.119077] Switched to clocksource stc
1.151330] FS-Cache: Loaded
1.154650] CacheFiles: Loaded
1.173940] NET: Registered protocol family 2
1.179918] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
1.187098] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
1.193871] TCP: Hash tables configured (established 4096 bind 4096)
1.200391] TCP: reno registered
1.203659] UDP hash table entries: 256 (order: 0, 4096 bytes)
1.209586] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
1.216245] NET: Registered protocol family 1
1.221322] RPC: Registered named UNIX socket transport module.
1.227290] RPC: Registered udp transport module.
1.232126] RPC: Registered tcp transport module.
1.236857] RPC: Registered tcp NFSv4.1 backchannel transport module.
1.244477] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
1.252615] bcm2708_dma: DMA manager at f2007000
1.257476] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
1.267218] futex hash table entries: 256 (order: -1, 3072 bytes)
1.273716] audit: initializing netlink subsys (disabled)
1.279306] audit: type=2000 audit(1.040:1): initialized
1.299993] VFS: Disk quotas dquot_6.5.2
1.304337] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
1.313797] FS-Cache: Netfs ‘nfs’ registered for caching
1.320969] NFS: Registering the id_resolver key type
1.326149] Key type id_resolver registered
1.330496] Key type id_legacy registered
1.335900] msgmni has been set to 870
1.342311] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
1.350329] io scheduler noop registered
1.354312] io scheduler deadline registered (default)
1.360061] io scheduler cfq registered
1.366448] BCM2708FB: allocated DMA memory 5bc00000
1.371758] BCM2708FB: allocated DMA channel 0 @ f2007000
1.382373] Console: switching to colour frame buffer device 82x26
1.394162] bcm2708-dmaengine bcm2708-dmaengine: Load BCM2835 DMA engine driver
1.403816] uart-pl011 dev:f1: no DMA platform data
1.411262] vc-cma: Videocore CMA driver
1.416866] vc-cma: vc_cma_base = 0x00000000
1.423289] vc-cma: vc_cma_size = 0x00000000 (0 MiB)
1.430378] vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
1.450459] brd: module loaded
1.462043] loop: module loaded
1.467203] vchiq: vchiq_init_state: slot_zero = 0xdb800000, is_master = 0
1.476623] Loading iSCSI transport class v2.0-870.
1.484869] usbcore: registered new interface driver smsc95xx
1.492533] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
1.700376] Core Release: 2.80a
1.705109] Setting default values for core params
1.711515] Finished setting default values for core params
1.918775] Using Buffer DMA mode
1.923679] Periodic Transfer Interrupt Enhancement - disabled
1.931121] Multiprocessor Interrupt Enhancement - disabled
1.938269] OTG VER PARAM: 0, OTG VER FLAG: 0
1.944244] Dedicated Tx FIFOs mode
1.949718] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xdbc14000 dma = 0x5bc14000 len=9024
1.962776] FIQ FSM acceleration enabled for :
1.962776] Non-periodic Split Transactions
1.962776] Periodic Split Transactions
1.962776] High-Speed Isochronous Endpoints
1.985809] dwc_otg: Microframe scheduler enabled
1.985922] WARN::hcd_init_fiq:412: FIQ on core 0 at 0xc03fad3c
1.993520] WARN::hcd_init_fiq:413: FIQ ASM at 0xc03fb014 length 36
2.001445] WARN::hcd_init_fiq:438: MPHI regs_base at 0xdc806000
2.009156] dwc_otg bcm2708_usb: DWC OTG Controller
2.015694] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
2.024669] dwc_otg bcm2708_usb: irq 32, io mem 0x00000000
2.031856] Init: Port Power? op_state=1
2.037366] Init: Power Port (0)
2.042577] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
2.051070] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
2.059965] usb usb1: Product: DWC OTG Controller
2.066249] usb usb1: Manufacturer: Linux 3.18.11+ dwc_otg_hcd
2.073708] usb usb1: SerialNumber: bcm2708_usb
2.080893] hub 1-0:1.0: USB hub found
2.086372] hub 1-0:1.0: 1 port detected
2.092531] dwc_otg: FIQ enabled
2.092555] dwc_otg: NAK holdoff enabled
2.092567] dwc_otg: FIQ split-transaction FSM enabled
2.092637] Module dwc_common_port init
2.093256] usbcore: registered new interface driver usb-storage
2.101474] mousedev: PS/2 mouse device common for all mice
2.109582] bcm2835-cpufreq: min=700000 max=800000
2.116313] sdhci: Secure Digital Host Controller Interface driver
2.124226] sdhci: Copyright(c) Pierre Ossman
2.130553] DMA channels allocated for the MMC driver
2.169157] Load BCM2835 MMC driver
2.176254] sdhci-pltfm: SDHCI platform and OF driver helper
2.192338] ledtrig-cpu: registered to indicate activity on CPUs
2.200387] hidraw: raw HID events driver (C) Jiri Kosina
2.212055] usbcore: registered new interface driver usbhid
2.221433] usbhid: USB HID core driver
2.228460] TCP: cubic registered
2.234693] Initializing XFRM netlink socket
2.242864] NET: Registered protocol family 17
2.249367] Key type dns_resolver registered
2.256938] registered taskstats version 1
2.263002] vc-sm: Videocore shared memory driver
2.269464] [vc_sm_connected_init]: start
2.276322] [vc_sm_connected_init]: end - returning 0
2.284959] Waiting for root device /dev/mmcblk0p2…
2.292154] Indeed it is in host mode hprt0 = 00021501
2.304418] mmc0: host does not support reading read-only switch, assuming write-enable
2.331427] mmc0: new high speed SDHC card at address 0007
2.349213] mmcblk0: mmc0:0007 SD16G 14.4 GiB
2.360583] mmcblk0: p1 p2
2.425630] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
2.437313] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
2.447488] devtmpfs: mounted
2.453596] Freeing unused kernel memory: 336K (c079a000 - c07ee000)
2.509334] usb 1-1: new high-speed USB device number 2 using dwc_otg
2.517947] Indeed it is in host mode hprt0 = 00001101
2.729762] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
2.739880] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2.750959] hub 1-1:1.0: USB hub found
2.757599] hub 1-1:1.0: 5 ports detected
3.039438] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
3.159797] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
3.168759] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
3.188111] smsc95xx v1.0.4
3.268675] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:94:38:00
3.379509] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
3.491278] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=8176
3.500785] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
3.512233] usb 1-1.2: Product: 802.11n WLAN Adapter
3.519898] usb 1-1.2: Manufacturer: Realtek
3.527005] usb 1-1.2: SerialNumber: 00e04c000001
3.619403] usb 1-1.5: new high-speed USB device number 5 using dwc_otg
3.762098] usb 1-1.5: New USB device found, idVendor=0bda, idProduct=2838
3.779428] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
3.788653] usb 1-1.5: Product: RTL2838UHIDIR
3.809287] usb 1-1.5: Manufacturer: Realtek
3.815412] usb 1-1.5: SerialNumber: 00000001
4.299369] udevd[159]: starting version 175
7.448918] random: nonblocking pool is initialized
8.075623] usbcore: registered new interface driver rtl8192cu
10.977086] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
11.410119] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
12.506128] device-mapper: ioctl: 4.28.0-ioctl (2014-09-17) initialised: dm-devel@redhat.com
22.639353] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
29.949385] cfg80211: Calling CRDA to update world regulatory domain
46.278835] Adding 102396k swap on /var/swap. Priority:-1 extents:2 across:2134012k SSFS
The only other thing I can think of is FR24’s feeder settings having the DUMP line:
COM/DEV/PATH: my setting [/dev/ttyUSB0, COM8, /usr/bin/dump1090]
However I am pretty certain I left everything as suggested when reading through and I couldn’t go back and distinguish the exact path without knowing exactly where dump placed itself. But dump 1090 does seem to either crash/vanish as the weburl:8080 doesn’t work.
pi@raspberrypi /run/dump1090-mutability $ /etc/init.d/dump1090-mutability status
[FAIL] dump1090-mutability is not running … failed!
pi@raspberrypi /run/dump1090-mutability $ sudo /etc/init.d/dump1090-mutability start
pi@raspberrypi /run/dump1090-mutability $
pi@raspberrypi /run/dump1090-mutability $ /etc/init.d/dump1090-mutability status
ok ] dump1090-mutability is running.
Well - what are you expecting to manage dump1090 - init.d scripts, piaware, or the FR24 feeder? If you are giving a path to the FR24 feeder, I guess you are expecting the FR24 feeder to manage it? Maybe you should check those logs.
I have removed it from FR24 although I don’t remember instructing PIAWARE directly to manage DUMP.
FR logs show this at the time DUMP stopped;
2015-06-16 07:34:24 | [feed]sent 6 AC in 1 packet
2015-06-16 07:34:29 | [feed]sent 6 AC in 1 packet
2015-06-16 07:34:32 | [feed]removed 2 of 16 AC
2015-06-16 07:34:34 | [feed]sent 8 AC in 1 packet
2015-06-16 07:34:37 | [reader][0]Connection terminated
2015-06-16 07:34:42 | [reader][0]Connecting to Generic receiver via (avr-tcp://localhost:30002)
2015-06-16 07:34:42 | [reader][e][0]Could not connect to avr-tcp://localhost:30002
2015-06-16 07:34:47 | [reader][0]Connecting to Generic receiver via (avr-tcp://localhost:30002)
2015-06-16 07:34:47 | [reader][e][0]Could not connect to avr-tcp://localhost:30002
2015-06-16 07:34:52 | [reader][0]Connecting to Generic receiver via (avr-tcp://localhost:30002)
2015-06-16 07:34:52 | [reader][e][0]Could not connect to avr-tcp://localhost:30002
2015-06-16 07:34:57 | [reader][0]Connecting to Generic receiver via (avr-tcp://localhost:30002)
2015-06-16 07:34:57 | [reader][e][0]Could not connect to avr-tcp://localhost:30002
2015-06-16 07:35:02 | [reader][0]Connecting to Generic receiver via (avr-tcp://localhost:30002)
2015-06-16 07:35:02 | [reader][e][0]Could not connect to avr-tcp://localhost:30002
2015-06-16 07:35:04 | [feed][n]ping 1
2015-06-16 07:35:07 | [reader][0]Connecting to Generic receiver via (avr-tcp://localhost:30002)
2015-06-16 07:35:07 | [reader][e][0]Could not connect to avr-tcp://localhost:30002
2015-06-16 07:35:12 | [reader][0]Connecting to Generic receiver via (avr-tcp://localhost:30002)
2015-06-16 07:35:12 | [reader][e][0]Could not connect to avr-tcp://localhost:30002
Piaware
[quote]06/16/2015 06:20:52 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.6kB/s UDP to server
06/16/2015 06:20:52 mlat: Aircraft: 19 known, 12 requested by server
06/16/2015 06:21:05 12693 msgs recv’d from dump1090-mutab (279 in last 5m); 12692 msgs sent to FlightAware
06/16/2015 06:26:05 12909 msgs recv’d from dump1090-mutab (216 in last 5m); 12908 msgs sent to FlightAware
06/16/2015 06:31:05 13096 msgs recv’d from dump1090-mutab (187 in last 5m); 13095 msgs sent to FlightAware
06/16/2015 06:34:37 lost connection to faup1090, reconnecting…
06/16/2015 06:34:37 mlat: Lost connection to localhost:30005
06/16/2015 06:34:37 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:34:37 no ADS-B data program is serving on port 30005, next check in 60s
06/16/2015 06:35:08 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:35:08 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:35:35 no ADS-B producer program seen for 300 seconds (or since piaware started), will attempt to start it next check after 360 seconds…
06/16/2015 06:35:35 no ADS-B producer (dump1090, modesmixer, etc) appears to be running or is not listening for connections on port 30005, next check in 5m
06/16/2015 06:35:37 no ADS-B data program is serving on port 30005, next check in 60s
06/16/2015 06:35:38 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:35:38 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:35:53 mlat: Receiver connection: disconnected
06/16/2015 06:35:53 mlat: Server connection: ready
06/16/2015 06:35:53 mlat: Receiver: 62.3 msg/s received 1.1kB/s from receiver
06/16/2015 06:35:53 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
06/16/2015 06:35:53 mlat: Aircraft: 0 known, 10 requested by server
06/16/2015 06:36:05 13234 msgs recv’d from dump1090-mutab (138 in last 5m); 13233 msgs sent to FlightAware
06/16/2015 06:36:08 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:36:08 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:36:37 no ADS-B data program is serving on port 30005, next check in 60s
06/16/2015 06:36:38 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:36:38 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:37:08 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:37:08 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:37:37 no ADS-B data program is serving on port 30005, next check in 60s
06/16/2015 06:37:38 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:37:38 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:38:08 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:38:08 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:38:37 no ADS-B data program is serving on port 30005, next check in 60s
06/16/2015 06:38:38 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:38:38 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:39:08 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:39:08 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:39:38 no ADS-B data program is serving on port 30005, next check in 60s
06/16/2015 06:39:38 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:39:38 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:40:08 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:40:08 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:40:35 seconds since last message or startup (360) less than threshold for action (3600), waiting…
06/16/2015 06:40:35 no ADS-B producer program seen for 600 seconds, trying to start it…
06/16/2015 06:40:35 can’t start dump1090, no dump1090 script in /etc/init.d
06/16/2015 06:40:38 no ADS-B data program is serving on port 30005, next check in 60s
06/16/2015 06:40:38 mlat: Connection to localhost:30005 lost: [Errno 111] Connection refused
06/16/2015 06:40:38 mlat: Reconnecting in 30.0 seconds
06/16/2015 06:41:05 13234 msgs recv’d from dump1090-mutab (0 in last 5m); 13233 msgs sent to FlightAware
looks like faup is trying to start??? or something[/quote]
Unfortunately it’s nothing obvious then. You will probably need to run dump1090 by hand in a screen session with core dumps enabled and wait for it to happen again. How frequently does it crash?
Seems to be once a day around 5am but I don’t get the notification until about 1pm that it’s off however sometimes it runs fine past that point and carries on for a few days.
Seems as soon as I put a new SD-Card flashed with Dump-Mutability that it’s had issues as the previous card wasn’t an issue on normal DUMP.
I’m not too sure what I can do as I can’t leave a screen running for hours when I’m not awake as it’d disconnect SSH
“screen” is a utility that solves exactly that problem.
If it is crashing regularly at 5am then I would suggest investigating what is happening at 5am.
If you are swapping SD cards you are effectively swapping the entire operating system and everything installed so it’s not really a useful way to narrow down the problem - it’s equally likely it’s a setup problem specific to one image.
“[2015-06-20 07:40 BST] no ADS-B data program is serving on port 30005, next check in 60s
[2015-06-20 07:41 BST] no new messages received in 19310 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart dump1090, possibly restart faup1090 and definitely reconnect, just in case…
[2015-06-20 07:41 BST] can’t restart dump1090, no dump1090 script in /etc/init.d
[2015-06-20 07:41 BST] stop_faup1090: no need to stop faup1090, it’s not running
[2015-06-20 07:41 BST] close_faup1090_socket called with no socket argument and no faup1090 global socket
[2015-06-20 07:41 BST] will attempt to connect to faup1090 in 60s…
[2015-06-20 07:41 BST] 87226 msgs recv’d from dump1090-mutab (0 in last 5m); 87103 msgs sent to FlightAware”
How it got 87226 msg’s from Dump1090-mutab I’ll never know but it doesn’t see “dump” in the init.d file although there is dump1090-mutability.
You need to explain what you’re doing more clearly.
Those logs tell me that (a) dump1090-mutability is running and listening on port 30005 and (b) piaware is not receiving messages
But you have not given enough context about whether this is before or after you restarted things, what the corresponding dump1090-mutability logs say at the time, and what the previous context of the piaware logs is.
If you want to sort out remote ssh access to your Pi it might be simplest if I ssh in and have a poke around rather than trying to guess at the problem from incomplete/garbled information.
This is just piaware trying to be clever and failing, FWIW; it only looks for scripts that look like the Flightaware dump1090 initscript.
(More recent piaware versions are a little smarter about this)
