API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Feb 4th, 2019
225
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 106.67 KB | None | 0 0
raw download clone embed print report
  1. -- Logs begin at Mon 2019-02-04 18:34:43 UTC, end at Mon 2019-02-04 18:40:17 UTC
  2. Feb 04 18:34:43 adsbx-custom kernel: Booting Linux on physical CPU 0x0
  3. Feb 04 18:34:43 adsbx-custom kernel: Linux version 4.14.52-v7+ (dc4@dc4-XPS13-93
  4. Feb 04 18:34:43 adsbx-custom kernel: CPU: ARMv7 Processor [410fd034] revision 4
  5. Feb 04 18:34:43 adsbx-custom kernel: CPU: div instructions available: patching d
  6. Feb 04 18:34:43 adsbx-custom kernel: CPU: PIPT / VIPT nonaliasing data cache, VI
  7. Feb 04 18:34:43 adsbx-custom kernel: OF: fdt: Machine model: Raspberry Pi 3 Mode
  8. Feb 04 18:34:43 adsbx-custom kernel: Memory policy: Data cache writealloc
  9. Feb 04 18:34:43 adsbx-custom kernel: cma: Reserved 8 MiB at 0x3ac00000
  10. Feb 04 18:34:43 adsbx-custom kernel: On node 0 totalpages: 242688
  11. Feb 04 18:34:43 adsbx-custom kernel: free_area_init_node: node 0, pgdat 80c85000
  12. Feb 04 18:34:43 adsbx-custom kernel: Normal zone: 2133 pages used for memmap
  13. Feb 04 18:34:43 adsbx-custom kernel: Normal zone: 0 pages reserved
  14. Feb 04 18:34:43 adsbx-custom kernel: Normal zone: 242688 pages, LIFO batch:31
  15. Feb 04 18:34:43 adsbx-custom kernel: percpu: Embedded 17 pages/cpu @ba34a000 s38
  16. Feb 04 18:34:43 adsbx-custom kernel: pcpu-alloc: s38720 r8192 d22720 u69632 allo
  17. Feb 04 18:34:43 adsbx-custom kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
  18. Feb 04 18:34:43 adsbx-custom kernel: Built 1 zonelists, mobility grouping on. T
  19. Feb 04 18:34:43 adsbx-custom kernel: Kernel command line: 8250.nr_uarts=0 bcm270
  20. Feb 04 18:34:43 adsbx-custom kernel: PID hash table entries: 4096 (order: 2, 163
  21. Feb 04 18:34:43 adsbx-custom kernel: Dentry cache hash table entries: 131072 (or
  22. Feb 04 18:34:43 adsbx-custom kernel: Inode-cache hash table entries: 65536 (orde
  23. Feb 04 18:34:43 adsbx-custom kernel: Memory: 940236K/970752K available (7168K ke
  24. Feb 04 18:34:43 adsbx-custom kernel: Virtual kernel memory layout:
  25. vector : 0xffff0000 - 0xffff1000 (
  26. fixmap : 0xffc00000 - 0xfff00000 (30
  27. vmalloc : 0xbb800000 - 0xff800000 (10
  28. lowmem : 0x80000000 - 0xbb400000 ( 9
  29. modules : 0x7f000000 - 0x80000000 (
  30. .text : 0x80008000 - 0x80800000 (81
  31. .init : 0x80b00000 - 0x80c00000 (10
  32. .data : 0x80c00000 - 0x80c8fef4 ( 5
  33. .bss : 0x80c96f40 - 0x80d47874 ( 7
  34. Feb 04 18:34:43 adsbx-custom kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0,
  35. Feb 04 18:34:43 adsbx-custom kernel: ftrace: allocating 25258 entries in 75 page
  36. Feb 04 18:34:43 adsbx-custom kernel: Hierarchical RCU implementation.
  37. Feb 04 18:34:43 adsbx-custom kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs
  38. Feb 04 18:34:43 adsbx-custom kernel: arch_timer: cp15 timer(s) running at 19.20M
  39. Feb 04 18:34:43 adsbx-custom kernel: clocksource: arch_sys_counter: mask: 0xffff
  40. Feb 04 18:34:43 adsbx-custom kernel: sched_clock: 56 bits at 19MHz, resolution 5
  41. Feb 04 18:34:43 adsbx-custom kernel: Switching to timer-based delay loop, resolu
  42. Feb 04 18:34:43 adsbx-custom kernel: Console: colour dummy device 80x30
  43. Feb 04 18:34:43 adsbx-custom kernel: console [tty1] enabled
  44. Feb 04 18:34:43 adsbx-custom kernel: Calibrating delay loop (skipped), value cal
  45. Feb 04 18:34:43 adsbx-custom kernel: pid_max: default: 32768 minimum: 301
  46. Feb 04 18:34:43 adsbx-custom kernel: Mount-cache hash table entries: 2048 (order
  47. Feb 04 18:34:43 adsbx-custom kernel: Mountpoint-cache hash table entries: 2048 (
  48. Feb 04 18:34:43 adsbx-custom kernel: Disabling memory control group subsystem
  49. Feb 04 18:34:43 adsbx-custom kernel: CPU: Testing write buffer coherency: ok
  50. Feb 04 18:34:43 adsbx-custom kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 800
  51. Feb 04 18:34:43 adsbx-custom kernel: Setting up static identity map for 0x100000
  52. Feb 04 18:34:43 adsbx-custom kernel: Hierarchical SRCU implementation.
  53. Feb 04 18:34:43 adsbx-custom kernel: smp: Bringing up secondary CPUs ...
  54. Feb 04 18:34:43 adsbx-custom kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 800
  55. Feb 04 18:34:43 adsbx-custom kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 800
  56. Feb 04 18:34:43 adsbx-custom kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 800
  57. Feb 04 18:34:43 adsbx-custom kernel: smp: Brought up 1 node, 4 CPUs
  58. Feb 04 18:34:43 adsbx-custom kernel: SMP: Total of 4 processors activated (153.6
  59. Feb 04 18:34:43 adsbx-custom kernel: CPU: All CPU(s) started in HYP mode.
  60. Feb 04 18:34:43 adsbx-custom kernel: CPU: Virtualization extensions available.
  61. Feb 04 18:34:43 adsbx-custom kernel: devtmpfs: initialized
  62. Feb 04 18:34:43 adsbx-custom kernel: random: get_random_u32 called from bucket_t
  63. Feb 04 18:34:43 adsbx-custom kernel: VFP support v0.3: implementor 41 architectu
  64. Feb 04 18:34:43 adsbx-custom kernel: clocksource: jiffies: mask: 0xffffffff max_
  65. Feb 04 18:34:43 adsbx-custom kernel: futex hash table entries: 1024 (order: 4, 6
  66. Feb 04 18:34:43 adsbx-custom kernel: pinctrl core: initialized pinctrl subsystem
  67. Feb 04 18:34:43 adsbx-custom kernel: NET: Registered protocol family 16
  68. Feb 04 18:34:43 adsbx-custom kernel: DMA: preallocated 1024 KiB pool for atomic
  69. Feb 04 18:34:43 adsbx-custom kernel: hw-breakpoint: found 5 (+1 reserved) breakp
  70. Feb 04 18:34:43 adsbx-custom kernel: hw-breakpoint: maximum watchpoint size is 8
  71. Feb 04 18:34:43 adsbx-custom kernel: Serial: AMBA PL011 UART driver
  72. Feb 04 18:34:43 adsbx-custom kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enab
  73. Feb 04 18:34:43 adsbx-custom kernel: uart-pl011 3f201000.serial: could not find
  74. Feb 04 18:34:43 adsbx-custom kernel: bcm2835-dma 3f007000.dma: DMA legacy API ma
  75. Feb 04 18:34:43 adsbx-custom kernel: SCSI subsystem initialized
  76. Feb 04 18:34:43 adsbx-custom kernel: usbcore: registered new interface driver us
  77. Feb 04 18:34:43 adsbx-custom kernel: usbcore: registered new interface driver hu
  78. Feb 04 18:34:43 adsbx-custom kernel: usbcore: registered new device driver usb
  79. Feb 04 18:34:43 adsbx-custom kernel: raspberrypi-firmware soc:firmware: Attached
  80. Feb 04 18:34:43 adsbx-custom kernel: clocksource: Switched to clocksource arch_s
  81. Feb 04 18:34:43 adsbx-custom kernel: VFS: Disk quotas dquot_6.6.0
  82. Feb 04 18:34:43 adsbx-custom kernel: VFS: Dquot-cache hash table entries: 1024 (
  83. Feb 04 18:34:43 adsbx-custom kernel: FS-Cache: Loaded
  84. Feb 04 18:34:43 adsbx-custom kernel: CacheFiles: Loaded
  85. Feb 04 18:34:43 adsbx-custom kernel: NET: Registered protocol family 2
  86. Feb 04 18:34:43 adsbx-custom kernel: TCP established hash table entries: 8192 (o
  87. Feb 04 18:34:43 adsbx-custom kernel: TCP bind hash table entries: 8192 (order: 4
  88. Feb 04 18:34:43 adsbx-custom kernel: TCP: Hash tables configured (established 81
  89. Feb 04 18:34:43 adsbx-custom kernel: UDP hash table entries: 512 (order: 2, 1638
  90. Feb 04 18:34:43 adsbx-custom kernel: UDP-Lite hash table entries: 512 (order: 2,
  91. Feb 04 18:34:43 adsbx-custom kernel: NET: Registered protocol family 1
  92. Feb 04 18:34:43 adsbx-custom kernel: RPC: Registered named UNIX socket transport
  93. Feb 04 18:34:43 adsbx-custom kernel: RPC: Registered udp transport module.
  94. Feb 04 18:34:43 adsbx-custom kernel: RPC: Registered tcp transport module.
  95. Feb 04 18:34:43 adsbx-custom kernel: RPC: Registered tcp NFSv4.1 backchannel tra
  96. Feb 04 18:34:43 adsbx-custom kernel: hw perfevents: enabled with armv7_cortex_a7
  97. Feb 04 18:34:43 adsbx-custom kernel: workingset: timestamp_bits=14 max_order=18
  98. Feb 04 18:34:43 adsbx-custom kernel: FS-Cache: Netfs 'nfs' registered for cachin
  99. Feb 04 18:34:43 adsbx-custom kernel: NFS: Registering the id_resolver key type
  100. Feb 04 18:34:43 adsbx-custom kernel: Key type id_resolver registered
  101. Feb 04 18:34:43 adsbx-custom kernel: Key type id_legacy registered
  102. Feb 04 18:34:43 adsbx-custom kernel: nfs4filelayout_init: NFSv4 File Layout Driv
  103. Feb 04 18:34:43 adsbx-custom kernel: Block layer SCSI generic (bsg) driver versi
  104. Feb 04 18:34:43 adsbx-custom kernel: io scheduler noop registered
  105. Feb 04 18:34:43 adsbx-custom kernel: io scheduler deadline registered (default)
  106. Feb 04 18:34:43 adsbx-custom kernel: io scheduler cfq registered
  107. Feb 04 18:34:43 adsbx-custom kernel: io scheduler mq-deadline registered
  108. Feb 04 18:34:43 adsbx-custom kernel: io scheduler kyber registered
  109. Feb 04 18:34:43 adsbx-custom kernel: BCM2708FB: allocated DMA memory fad10000
  110. Feb 04 18:34:43 adsbx-custom kernel: BCM2708FB: allocated DMA channel 0 @ bb8130
  111. Feb 04 18:34:43 adsbx-custom kernel: Console: switching to colour frame buffer d
  112. Feb 04 18:34:43 adsbx-custom kernel: bcm2835-rng 3f104000.rng: hwrng registered
  113. Feb 04 18:34:43 adsbx-custom kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3ec
  114. Feb 04 18:34:43 adsbx-custom kernel: vc-sm: Videocore shared memory driver
  115. Feb 04 18:34:43 adsbx-custom kernel: gpiomem-bcm2835 3f200000.gpiomem: Initialis
  116. Feb 04 18:34:43 adsbx-custom kernel: brd: module loaded
  117. Feb 04 18:34:43 adsbx-custom kernel: loop: module loaded
  118. Feb 04 18:34:43 adsbx-custom kernel: Loading iSCSI transport class v2.0-870.
  119. Feb 04 18:34:43 adsbx-custom kernel: libphy: Fixed MDIO Bus: probed
  120. Feb 04 18:34:43 adsbx-custom kernel: usbcore: registered new interface driver la
  121. Feb 04 18:34:43 adsbx-custom kernel: usbcore: registered new interface driver sm
  122. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg: version 3.00a 10-AUG-2012 (platfor
  123. Feb 04 18:34:43 adsbx-custom kernel: Core Release: 2.80a
  124. Feb 04 18:34:43 adsbx-custom kernel: Setting default values for core params
  125. Feb 04 18:34:43 adsbx-custom kernel: Finished setting default values for core pa
  126. Feb 04 18:34:43 adsbx-custom kernel: Using Buffer DMA mode
  127. Feb 04 18:34:43 adsbx-custom kernel: Periodic Transfer Interrupt Enhancement - d
  128. Feb 04 18:34:43 adsbx-custom kernel: Multiprocessor Interrupt Enhancement - disa
  129. Feb 04 18:34:43 adsbx-custom kernel: OTG VER PARAM: 0, OTG VER FLAG: 0
  130. Feb 04 18:34:43 adsbx-custom kernel: Dedicated Tx FIFOs mode
  131. Feb 04 18:34:43 adsbx-custom kernel: WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce
  132. Feb 04 18:34:43 adsbx-custom kernel: FIQ FSM acceleration enabled for :
  133. Non-periodic Split Transactions
  134. Periodic Split Transactions
  135. High-Speed Isochronous Endpoints
  136. Interrupt/Control Split Transaction hack en
  137. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg: Microframe scheduler enabled
  138. Feb 04 18:34:43 adsbx-custom kernel: WARN::hcd_init_fiq:459: FIQ on core 1 at 0x
  139. Feb 04 18:34:43 adsbx-custom kernel: WARN::hcd_init_fiq:460: FIQ ASM at 0x805e83
  140. Feb 04 18:34:43 adsbx-custom kernel: WARN::hcd_init_fiq:486: MPHI regs_base at 0
  141. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg 3f980000.usb: DWC OTG Controller
  142. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg 3f980000.usb: new USB bus registere
  143. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg 3f980000.usb: irq 62, io mem 0x0000
  144. Feb 04 18:34:43 adsbx-custom kernel: Init: Port Power? op_state=1
  145. Feb 04 18:34:43 adsbx-custom kernel: Init: Power Port (0)
  146. Feb 04 18:34:43 adsbx-custom kernel: usb usb1: New USB device found, idVendor=1d
  147. Feb 04 18:34:43 adsbx-custom kernel: usb usb1: New USB device strings: Mfr=3, Pr
  148. Feb 04 18:34:43 adsbx-custom kernel: usb usb1: Product: DWC OTG Controller
  149. Feb 04 18:34:43 adsbx-custom kernel: usb usb1: Manufacturer: Linux 4.14.52-v7+ d
  150. Feb 04 18:34:43 adsbx-custom kernel: usb usb1: SerialNumber: 3f980000.usb
  151. Feb 04 18:34:43 adsbx-custom kernel: hub 1-0:1.0: USB hub found
  152. Feb 04 18:34:43 adsbx-custom kernel: hub 1-0:1.0: 1 port detected
  153. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg: FIQ enabled
  154. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg: NAK holdoff enabled
  155. Feb 04 18:34:43 adsbx-custom kernel: dwc_otg: FIQ split-transaction FSM enabled
  156. Feb 04 18:34:43 adsbx-custom kernel: Module dwc_common_port init
  157. Feb 04 18:34:43 adsbx-custom kernel: usbcore: registered new interface driver us
  158. Feb 04 18:34:43 adsbx-custom kernel: mousedev: PS/2 mouse device common for all
  159. Feb 04 18:34:43 adsbx-custom kernel: IR NEC protocol handler initialized
  160. Feb 04 18:34:43 adsbx-custom kernel: IR RC5(x/sz) protocol handler initialized
  161. Feb 04 18:34:43 adsbx-custom kernel: IR RC6 protocol handler initialized
  162. Feb 04 18:34:43 adsbx-custom kernel: IR JVC protocol handler initialized
  163. Feb 04 18:34:43 adsbx-custom kernel: IR Sony protocol handler initialized
  164. Feb 04 18:34:43 adsbx-custom kernel: IR SANYO protocol handler initialized
  165. Feb 04 18:34:43 adsbx-custom kernel: IR Sharp protocol handler initialized
  166. Feb 04 18:34:43 adsbx-custom kernel: IR MCE Keyboard/mouse protocol handler init
  167. Feb 04 18:34:43 adsbx-custom kernel: IR XMP protocol handler initialized
  168. Feb 04 18:34:43 adsbx-custom kernel: bcm2835-wdt 3f100000.watchdog: Broadcom BCM
  169. Feb 04 18:34:43 adsbx-custom kernel: bcm2835-cpufreq: min=600000 max=1200000
  170. Feb 04 18:34:43 adsbx-custom kernel: sdhci: Secure Digital Host Controller Inter
  171. Feb 04 18:34:43 adsbx-custom kernel: sdhci: Copyright(c) Pierre Ossman
  172. Feb 04 18:34:43 adsbx-custom kernel: mmc-bcm2835 3f300000.mmc: could not get clk
  173. Feb 04 18:34:43 adsbx-custom kernel: sdhost-bcm2835 3f202000.mmc: could not get
  174. Feb 04 18:34:43 adsbx-custom kernel: sdhci-pltfm: SDHCI platform and OF driver h
  175. Feb 04 18:34:43 adsbx-custom kernel: ledtrig-cpu: registered to indicate activit
  176. Feb 04 18:34:43 adsbx-custom kernel: hidraw: raw HID events driver (C) Jiri Kosi
  177. Feb 04 18:34:43 adsbx-custom kernel: usbcore: registered new interface driver us
  178. Feb 04 18:34:43 adsbx-custom kernel: usbhid: USB HID core driver
  179. Feb 04 18:34:43 adsbx-custom kernel: vchiq: vchiq_init_state: slot_zero = bad800
  180. Feb 04 18:34:43 adsbx-custom kernel: [vc_sm_connected_init]: start
  181. Feb 04 18:34:43 adsbx-custom kernel: [vc_sm_connected_init]: end - returning 0
  182. Feb 04 18:34:43 adsbx-custom kernel: Initializing XFRM netlink socket
  183. Feb 04 18:34:43 adsbx-custom kernel: NET: Registered protocol family 17
  184. Feb 04 18:34:43 adsbx-custom kernel: Key type dns_resolver registered
  185. Feb 04 18:34:43 adsbx-custom kernel: Registering SWP/SWPB emulation handler
  186. Feb 04 18:34:43 adsbx-custom kernel: registered taskstats version 1
  187. Feb 04 18:34:43 adsbx-custom kernel: uart-pl011 3f201000.serial: cts_event_worka
  188. Feb 04 18:34:43 adsbx-custom kernel: 3f201000.serial: ttyAMA0 at MMIO 0x3f201000
  189. Feb 04 18:34:43 adsbx-custom kernel: mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_d
  190. Feb 04 18:34:43 adsbx-custom kernel: mmc-bcm2835 3f300000.mmc: DMA channel alloc
  191. Feb 04 18:34:43 adsbx-custom kernel: sdhost: log_buf @ bad07000 (fad07000)
  192. Feb 04 18:34:43 adsbx-custom kernel: mmc1: queuing unknown CIS tuple 0x80 (2 byt
  193. Feb 04 18:34:43 adsbx-custom kernel: mmc1: queuing unknown CIS tuple 0x80 (3 byt
  194. Feb 04 18:34:43 adsbx-custom kernel: mmc1: queuing unknown CIS tuple 0x80 (3 byt
  195. Feb 04 18:34:43 adsbx-custom kernel: mmc1: queuing unknown CIS tuple 0x80 (7 byt
  196. Feb 04 18:34:43 adsbx-custom kernel: Indeed it is in host mode hprt0 = 00021501
  197. Feb 04 18:34:43 adsbx-custom kernel: random: fast init done
  198. Feb 04 18:34:43 adsbx-custom kernel: mmc0: sdhost-bcm2835 loaded - DMA enabled (
  199. Feb 04 18:34:43 adsbx-custom kernel: of_cfs_init
  200. Feb 04 18:34:43 adsbx-custom kernel: of_cfs_init: OK
  201. Feb 04 18:34:43 adsbx-custom kernel: Waiting for root device PARTUUID=49bb75c5-0
  202. Feb 04 18:34:43 adsbx-custom kernel: mmc0: host does not support reading read-on
  203. Feb 04 18:34:43 adsbx-custom kernel: mmc0: new high speed SDHC card at address 0
  204. Feb 04 18:34:43 adsbx-custom kernel: mmcblk0: mmc0:0007 Y016B 14.9 GiB
  205. Feb 04 18:34:43 adsbx-custom kernel: mmcblk0: p1 p2
  206. Feb 04 18:34:43 adsbx-custom kernel: mmc1: new high speed SDIO card at address 0
  207. Feb 04 18:34:43 adsbx-custom kernel: EXT4-fs (mmcblk0p2): mounted filesystem wit
  208. Feb 04 18:34:43 adsbx-custom kernel: VFS: Mounted root (ext4 filesystem) readonl
  209. Feb 04 18:34:43 adsbx-custom kernel: devtmpfs: mounted
  210. Feb 04 18:34:43 adsbx-custom kernel: Freeing unused kernel memory: 1024K
  211. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1: new high-speed USB device number 2
  212. Feb 04 18:34:43 adsbx-custom kernel: Indeed it is in host mode hprt0 = 00001101
  213. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1: New USB device found, idVendor=042
  214. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1: New USB device strings: Mfr=0, Pro
  215. Feb 04 18:34:43 adsbx-custom kernel: hub 1-1:1.0: USB hub found
  216. Feb 04 18:34:43 adsbx-custom kernel: hub 1-1:1.0: 5 ports detected
  217. Feb 04 18:34:43 adsbx-custom systemd[1]: System time before build time, advancin
  218. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.1: new high-speed USB device number
  219. Feb 04 18:34:43 adsbx-custom kernel: NET: Registered protocol family 10
  220. Feb 04 18:34:43 adsbx-custom kernel: Segment Routing with IPv6
  221. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.1: New USB device found, idVendor=0
  222. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.1: New USB device strings: Mfr=0, P
  223. Feb 04 18:34:43 adsbx-custom kernel: ip_tables: (C) 2000-2006 Netfilter Core Tea
  224. Feb 04 18:34:43 adsbx-custom kernel: smsc95xx v1.0.6
  225. Feb 04 18:34:43 adsbx-custom kernel: random: systemd: uninitialized urandom read
  226. Feb 04 18:34:43 adsbx-custom systemd[1]: systemd 232 running in system mode. (+P
  227. Feb 04 18:34:43 adsbx-custom systemd[1]: Detected architecture arm.
  228. Feb 04 18:34:43 adsbx-custom systemd[1]: Set hostname to <adsbx-custom>.
  229. Feb 04 18:34:43 adsbx-custom kernel: random: systemd: uninitialized urandom read
  230. Feb 04 18:34:43 adsbx-custom kernel: smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx
  231. Feb 04 18:34:43 adsbx-custom kernel: random: systemd-cryptse: uninitialized uran
  232. Feb 04 18:34:43 adsbx-custom kernel: Under-voltage detected! (0x00050005)
  233. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.3: new high-speed USB device number
  234. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.3: New USB device found, idVendor=0
  235. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.3: New USB device strings: Mfr=1, P
  236. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.3: Product: RTL2838UHIDIR
  237. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.3: Manufacturer: Realtek
  238. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.3: SerialNumber: 00000001
  239. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.5: new high-speed USB device number
  240. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.5: New USB device found, idVendor=0
  241. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.5: New USB device strings: Mfr=1, P
  242. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.5: Product: RTL2838UHIDIR
  243. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.5: Manufacturer: Realtek
  244. Feb 04 18:34:43 adsbx-custom kernel: usb 1-1.5: SerialNumber: 00000001
  245. Feb 04 18:34:43 adsbx-custom systemd[1]: lm-sensors.service: Cannot add dependen
  246. Feb 04 18:34:43 adsbx-custom systemd[1]: Listening on Journal Socket.
  247. Feb 04 18:34:43 adsbx-custom systemd[1]: Listening on udev Kernel Socket.
  248. Feb 04 18:34:43 adsbx-custom systemd[1]: Listening on /dev/initctl Compatibility
  249. Feb 04 18:34:43 adsbx-custom systemd[1]: Created slice System Slice.
  250. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting Restore / save the current clo
  251. Feb 04 18:34:43 adsbx-custom systemd[1]: Created slice system-getty.slice.
  252. Feb 04 18:34:43 adsbx-custom systemd-journald[107]: Journal started
  253. -- Subject: The journal has been started
  254. -- Defined-By: systemd
  255. -- Support: https://www.debian.org/support
  256. --
  257. -- The system journal process has started up, opened the journal
  258. -- files for writing and is now ready to process requests.
  259. Feb 04 18:34:43 adsbx-custom systemd-journald[107]: Runtime journal (/run/log/jo
  260. -- Subject: Disk space used by the journal
  261. -- Defined-By: systemd
  262. -- Support: https://www.debian.org/support
  263. --
  264. -- Runtime journal (/run/log/journal/a70a6c77c57b4aceaedbe1115705864a) is curren
  265. -- Maximum allowed usage is set to 46.3M.
  266. -- Leaving at least 69.5M free (of currently available 457.7M of disk space).
  267. -- Enforced usage limit is thus 46.3M, of which 40.5M are still available.
  268. --
  269. -- The limits controlling how much disk space is used by the journal may
  270. -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
  271. -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
  272. -- /etc/systemd/journald.conf. See journald.conf(5) for details.
  273. Feb 04 18:34:43 adsbx-custom fake-hwclock[82]: Mon Feb 4 18:34:43 UTC 2019
  274. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Apply Kernel Variables.
  275. -- Subject: Unit systemd-sysctl.service has finished start-up
  276. -- Defined-By: systemd
  277. -- Support: https://www.debian.org/support
  278. --
  279. -- Unit systemd-sysctl.service has finished starting up.
  280. --
  281. -- The start-up result is done.
  282. Feb 04 18:34:43 adsbx-custom systemd-fsck[114]: e2fsck 1.43.4 (31-Jan-2017)
  283. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Create Static Device Nodes in /
  284. -- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
  285. -- Defined-By: systemd
  286. -- Support: https://www.debian.org/support
  287. --
  288. -- Unit systemd-tmpfiles-setup-dev.service has finished starting up.
  289. --
  290. -- The start-up result is done.
  291. Feb 04 18:34:43 adsbx-custom systemd-fsck[114]: rootfs: clean, 68690/948480 file
  292. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting udev Kernel Device Manager...
  293. -- Subject: Unit systemd-udevd.service has begun start-up
  294. -- Defined-By: systemd
  295. -- Support: https://www.debian.org/support
  296. --
  297. -- Unit systemd-udevd.service has begun starting up.
  298. Feb 04 18:34:43 adsbx-custom systemd[1]: Started File System Check on Root Devic
  299. -- Subject: Unit systemd-fsck-root.service has finished start-up
  300. -- Defined-By: systemd
  301. -- Support: https://www.debian.org/support
  302. --
  303. -- Unit systemd-fsck-root.service has finished starting up.
  304. --
  305. -- The start-up result is done.
  306. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting Remount Root and Kernel File S
  307. -- Subject: Unit systemd-remount-fs.service has begun start-up
  308. -- Defined-By: systemd
  309. -- Support: https://www.debian.org/support
  310. --
  311. -- Unit systemd-remount-fs.service has begun starting up.
  312. Feb 04 18:34:43 adsbx-custom kernel: EXT4-fs (mmcblk0p2): re-mounted. Opts: (nul
  313. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Remount Root and Kernel File Sy
  314. -- Subject: Unit systemd-remount-fs.service has finished start-up
  315. -- Defined-By: systemd
  316. -- Support: https://www.debian.org/support
  317. --
  318. -- Unit systemd-remount-fs.service has finished starting up.
  319. --
  320. -- The start-up result is done.
  321. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting Load/Save Random Seed...
  322. -- Subject: Unit systemd-random-seed.service has begun start-up
  323. -- Defined-By: systemd
  324. -- Support: https://www.debian.org/support
  325. --
  326. -- Unit systemd-random-seed.service has begun starting up.
  327. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting udev Coldplug all Devices...
  328. -- Subject: Unit systemd-udev-trigger.service has begun start-up
  329. -- Defined-By: systemd
  330. -- Support: https://www.debian.org/support
  331. --
  332. -- Unit systemd-udev-trigger.service has begun starting up.
  333. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting Flush Journal to Persistent St
  334. -- Subject: Unit systemd-journal-flush.service has begun start-up
  335. -- Defined-By: systemd
  336. -- Support: https://www.debian.org/support
  337. --
  338. -- Unit systemd-journal-flush.service has begun starting up.
  339. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Load/Save Random Seed.
  340. -- Subject: Unit systemd-random-seed.service has finished start-up
  341. -- Defined-By: systemd
  342. -- Support: https://www.debian.org/support
  343. --
  344. -- Unit systemd-random-seed.service has finished starting up.
  345. --
  346. lines 323-345
  347. -- Defined-By: systemd
  348. -- Support: https://www.debian.org/support
  349. --
  350. -- Unit systemd-random-seed.service has begun starting up.
  351. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting udev Coldplug all Devices...
  352. -- Subject: Unit systemd-udev-trigger.service has begun start-up
  353. -- Defined-By: systemd
  354. -- Support: https://www.debian.org/support
  355. --
  356. -- Unit systemd-udev-trigger.service has begun starting up.
  357. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting Flush Journal to Persistent Storage...
  358. -- Subject: Unit systemd-journal-flush.service has begun start-up
  359. -- Defined-By: systemd
  360. -- Support: https://www.debian.org/support
  361. --
  362. -- Unit systemd-journal-flush.service has begun starting up.
  363. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Load/Save Random Seed.
  364. -- Subject: Unit systemd-random-seed.service has finished start-up
  365. -- Defined-By: systemd
  366. -- Support: https://www.debian.org/support
  367. --
  368. -- Unit systemd-random-seed.service has finished starting up.
  369. --
  370. -- The start-up result is done.
  371. Feb 04 18:34:43 adsbx-custom systemd[1]: Started udev Kernel Device Manager.
  372. -- Subject: Unit systemd-udevd.service has finished start-up
  373. -- Defined-By: systemd
  374. -- Support: https://www.debian.org/support
  375. --
  376. -- Unit systemd-udevd.service has finished starting up.
  377. --
  378. -- The start-up result is done.
  379. Feb 04 18:34:43 adsbx-custom systemd-journald[107]: Runtime journal (/run/log/journal/a70a6c77c57b4aceaedbe1115705864a) is 5.7M, max 46.3M, 40.5M free.
  380. -- Subject: Disk space used by the journal
  381. -- Defined-By: systemd
  382. -- Support: https://www.debian.org/support
  383. --
  384. -- Runtime journal (/run/log/journal/a70a6c77c57b4aceaedbe1115705864a) is currently using 5.7M.
  385. -- Maximum allowed usage is set to 46.3M.
  386. -- Leaving at least 69.5M free (of currently available 457.7M of disk space).
  387. -- Enforced usage limit is thus 46.3M, of which 40.5M are still available.
  388. --
  389. -- The limits controlling how much disk space is used by the journal may
  390. -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
  391. -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
  392. -- /etc/systemd/journald.conf. See journald.conf(5) for details.
  393. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Set the console keyboard layout.
  394. -- Subject: Unit keyboard-setup.service has finished start-up
  395. -- Defined-By: systemd
  396. -- Support: https://www.debian.org/support
  397. --
  398. -- Unit keyboard-setup.service has finished starting up.
  399. --
  400. -- The start-up result is done.
  401. Feb 04 18:34:43 adsbx-custom systemd[1]: Reached target Local File Systems (Pre).
  402. -- Subject: Unit local-fs-pre.target has finished start-up
  403. -- Defined-By: systemd
  404. -- Support: https://www.debian.org/support
  405. --
  406. -- Unit local-fs-pre.target has finished starting up.
  407. --
  408. -- The start-up result is done.
  409. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Flush Journal to Persistent Storage.
  410. -- Subject: Unit systemd-journal-flush.service has finished start-up
  411. -- Defined-By: systemd
  412. -- Support: https://www.debian.org/support
  413. --
  414. -- Unit systemd-journal-flush.service has finished starting up.
  415. --
  416. -- The start-up result is done.
  417. Feb 04 18:34:43 adsbx-custom systemd[1]: Started udev Coldplug all Devices.
  418. -- Subject: Unit systemd-udev-trigger.service has finished start-up
  419. -- Defined-By: systemd
  420. -- Support: https://www.debian.org/support
  421. --
  422. -- Unit systemd-udev-trigger.service has finished starting up.
  423. --
  424. -- The start-up result is done.
  425. Feb 04 18:34:43 adsbx-custom systemd[1]: Starting Show Plymouth Boot Screen...
  426. -- Subject: Unit plymouth-start.service has begun start-up
  427. -- Defined-By: systemd
  428. -- Support: https://www.debian.org/support
  429. --
  430. -- Unit plymouth-start.service has begun starting up.
  431. Feb 04 18:34:43 adsbx-custom systemd[1]: Received SIGRTMIN+20 from PID 182 (plymouthd).
  432. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Show Plymouth Boot Screen.
  433. -- Subject: Unit plymouth-start.service has finished start-up
  434. -- Defined-By: systemd
  435. -- Support: https://www.debian.org/support
  436. --
  437. -- Unit plymouth-start.service has finished starting up.
  438. --
  439. -- The start-up result is done.
  440. Feb 04 18:34:43 adsbx-custom systemd[1]: Reached target Encrypted Volumes.
  441. -- Subject: Unit cryptsetup.target has finished start-up
  442. -- Defined-By: systemd
  443. -- Support: https://www.debian.org/support
  444. --
  445. -- Unit cryptsetup.target has finished starting up.
  446. --
  447. -- The start-up result is done.
  448. Feb 04 18:34:43 adsbx-custom systemd[1]: Reached target Paths.
  449. -- Subject: Unit paths.target has finished start-up
  450. -- Defined-By: systemd
  451. -- Support: https://www.debian.org/support
  452. --
  453. -- Unit paths.target has finished starting up.
  454. --
  455. -- The start-up result is done.
  456. Feb 04 18:34:43 adsbx-custom systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
  457. -- Subject: Unit systemd-ask-password-plymouth.path has finished start-up
  458. -- Defined-By: systemd
  459. -- Support: https://www.debian.org/support
  460. --
  461. -- Unit systemd-ask-password-plymouth.path has finished starting up.
  462. --
  463. -- The start-up result is done.
  464. Feb 04 18:34:43 adsbx-custom systemd[1]: Found device /dev/serial1.
  465. -- Subject: Unit dev-serial1.device has finished start-up
  466. -- Defined-By: systemd
  467. -- Support: https://www.debian.org/support
  468. --
  469. -- Unit dev-serial1.device has finished starting up.
  470. --
  471. -- The start-up result is done.
  472. Feb 04 18:34:44 adsbx-custom kernel: snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
  473. Feb 04 18:34:44 adsbx-custom kernel: bcm2835_alsa bcm2835_alsa: card created with 8 channels
  474. Feb 04 18:34:44 adsbx-custom systemd[1]: Found device /dev/disk/by-partuuid/49bb75c5-01.
  475. -- Subject: Unit dev-disk-by\x2dpartuuid-49bb75c5\x2d01.device has finished start-up
  476. -- Defined-By: systemd
  477. -- Support: https://www.debian.org/support
  478. --
  479. -- Unit dev-disk-by\x2dpartuuid-49bb75c5\x2d01.device has finished starting up.
  480. --
  481. -- The start-up result is done.
  482. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting File System Check on /dev/disk/by-partuuid/49bb75c5-01...
  483. -- Subject: Unit systemd-fsck@dev-disk-by\x2dpartuuid-49bb75c5\x2d01.service has begun start-up
  484. -- Defined-By: systemd
  485. -- Support: https://www.debian.org/support
  486. --
  487. -- Unit systemd-fsck@dev-disk-by\x2dpartuuid-49bb75c5\x2d01.service has begun starting up.
  488. Feb 04 18:34:44 adsbx-custom mtp-probe[212]: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1"
  489. Feb 04 18:34:44 adsbx-custom mtp-probe[214]: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
  490. Feb 04 18:34:44 adsbx-custom mtp-probe[214]: bus: 1, device: 4 was not an MTP device
  491. Feb 04 18:34:44 adsbx-custom mtp-probe[218]: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5"
  492. Feb 04 18:34:44 adsbx-custom mtp-probe[212]: bus: 1, device: 3 was not an MTP device
  493. Feb 04 18:34:44 adsbx-custom mtp-probe[218]: bus: 1, device: 5 was not an MTP device
  494. Feb 04 18:34:44 adsbx-custom kernel: brcmfmac: F1 signature read @0x18000000=0x1541a9a6
  495. Feb 04 18:34:44 adsbx-custom kernel: brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
  496. Feb 04 18:34:44 adsbx-custom kernel: usbcore: registered new interface driver brcmfmac
  497. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target Sound Card.
  498. -- Subject: Unit sound.target has finished start-up
  499. -- Defined-By: systemd
  500. -- Support: https://www.debian.org/support
  501. --
  502. -- Unit sound.target has finished starting up.
  503. --
  504. -- The start-up result is done.
  505. Feb 04 18:34:44 adsbx-custom systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
  506. -- Subject: Unit systemd-rfkill.socket has finished start-up
  507. -- Defined-By: systemd
  508. -- Support: https://www.debian.org/support
  509. --
  510. -- Unit systemd-rfkill.socket has finished starting up.
  511. --
  512. -- The start-up result is done.
  513. Feb 04 18:34:44 adsbx-custom kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
  514. Feb 04 18:34:44 adsbx-custom kernel: brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.3
  515. Feb 04 18:34:44 adsbx-custom systemd-fsck[215]: fsck.fat 4.1 (2017-01-24)
  516. Feb 04 18:34:44 adsbx-custom systemd-fsck[215]: /dev/mmcblk0p1: 176 files, 44870/83705 clusters
  517. Feb 04 18:34:44 adsbx-custom systemd[1]: Started File System Check on /dev/disk/by-partuuid/49bb75c5-01.
  518. -- Subject: Unit systemd-fsck@dev-disk-by\x2dpartuuid-49bb75c5\x2d01.service has finished start-up
  519. -- Defined-By: systemd
  520. -- Support: https://www.debian.org/support
  521. --
  522. -- Unit systemd-fsck@dev-disk-by\x2dpartuuid-49bb75c5\x2d01.service has finished starting up.
  523. --
  524. -- The start-up result is done.
  525. Feb 04 18:34:44 adsbx-custom systemd[1]: Mounting /boot...
  526. -- Subject: Unit boot.mount has begun start-up
  527. -- Defined-By: systemd
  528. -- Support: https://www.debian.org/support
  529. --
  530. -- Unit boot.mount has begun starting up.
  531. Feb 04 18:34:44 adsbx-custom systemd[1]: Mounted /boot.
  532. -- Subject: Unit boot.mount has finished start-up
  533. -- Defined-By: systemd
  534. -- Support: https://www.debian.org/support
  535. --
  536. -- Unit boot.mount has finished starting up.
  537. --
  538. -- The start-up result is done.
  539. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target Local File Systems.
  540. -- Subject: Unit local-fs.target has finished start-up
  541. -- Defined-By: systemd
  542. -- Support: https://www.debian.org/support
  543. --
  544. -- Unit local-fs.target has finished starting up.
  545. --
  546. -- The start-up result is done.
  547. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
  548. -- Subject: Unit plymouth-read-write.service has begun start-up
  549. -- Defined-By: systemd
  550. -- Support: https://www.debian.org/support
  551. --
  552. -- Unit plymouth-read-write.service has begun starting up.
  553. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting Preprocess NFS configuration...
  554. -- Subject: Unit nfs-config.service has begun start-up
  555. -- Defined-By: systemd
  556. -- Support: https://www.debian.org/support
  557. --
  558. -- Unit nfs-config.service has begun starting up.
  559. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting Create Volatile Files and Directories...
  560. -- Subject: Unit systemd-tmpfiles-setup.service has begun start-up
  561. -- Defined-By: systemd
  562. -- Support: https://www.debian.org/support
  563. --
  564. -- Unit systemd-tmpfiles-setup.service has begun starting up.
  565. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting Set console font and keymap...
  566. -- Subject: Unit console-setup.service has begun start-up
  567. -- Defined-By: systemd
  568. -- Support: https://www.debian.org/support
  569. --
  570. -- Unit console-setup.service has begun starting up.
  571. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting Raise network interfaces...
  572. -- Subject: Unit networking.service has begun start-up
  573. -- Defined-By: systemd
  574. -- Support: https://www.debian.org/support
  575. --
  576. -- Unit networking.service has begun starting up.
  577. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
  578. -- Subject: Unit plymouth-read-write.service has finished start-up
  579. -- Defined-By: systemd
  580. -- Support: https://www.debian.org/support
  581. --
  582. -- Unit plymouth-read-write.service has finished starting up.
  583. --
  584. -- The start-up result is done.
  585. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Preprocess NFS configuration.
  586. -- Subject: Unit nfs-config.service has finished start-up
  587. -- Defined-By: systemd
  588. -- Support: https://www.debian.org/support
  589. --
  590. -- Unit nfs-config.service has finished starting up.
  591. --
  592. -- The start-up result is done.
  593. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Set console font and keymap.
  594. -- Subject: Unit console-setup.service has finished start-up
  595. -- Defined-By: systemd
  596. -- Support: https://www.debian.org/support
  597. --
  598. -- Unit console-setup.service has finished starting up.
  599. --
  600. -- The start-up result is done.
  601. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target NFS client services.
  602. -- Subject: Unit nfs-client.target has finished start-up
  603. -- Defined-By: systemd
  604. -- Support: https://www.debian.org/support
  605. --
  606. -- Unit nfs-client.target has finished starting up.
  607. --
  608. -- The start-up result is done.
  609. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target Remote File Systems (Pre).
  610. -- Subject: Unit remote-fs-pre.target has finished start-up
  611. -- Defined-By: systemd
  612. -- Support: https://www.debian.org/support
  613. --
  614. -- Unit remote-fs-pre.target has finished starting up.
  615. --
  616. -- The start-up result is done.
  617. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target Remote File Systems.
  618. -- Subject: Unit remote-fs.target has finished start-up
  619. -- Defined-By: systemd
  620. -- Support: https://www.debian.org/support
  621. --
  622. -- Unit remote-fs.target has finished starting up.
  623. --
  624. -- The start-up result is done.
  625. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Create Volatile Files and Directories.
  626. -- Subject: Unit systemd-tmpfiles-setup.service has finished start-up
  627. -- Defined-By: systemd
  628. -- Support: https://www.debian.org/support
  629. --
  630. -- Unit systemd-tmpfiles-setup.service has finished starting up.
  631. --
  632. -- The start-up result is done.
  633. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting Update UTMP about System Boot/Shutdown...
  634. -- Subject: Unit systemd-update-utmp.service has begun start-up
  635. -- Defined-By: systemd
  636. -- Support: https://www.debian.org/support
  637. --
  638. -- Unit systemd-update-utmp.service has begun starting up.
  639. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target System Time Synchronized.
  640. -- Subject: Unit time-sync.target has finished start-up
  641. -- Defined-By: systemd
  642. -- Support: https://www.debian.org/support
  643. --
  644. -- Unit time-sync.target has finished starting up.
  645. --
  646. -- The start-up result is done.
  647. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Update UTMP about System Boot/Shutdown.
  648. -- Subject: Unit systemd-update-utmp.service has finished start-up
  649. -- Defined-By: systemd
  650. -- Support: https://www.debian.org/support
  651. --
  652. -- Unit systemd-update-utmp.service has finished starting up.
  653. --
  654. -- The start-up result is done.
  655. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target System Initialization.
  656. -- Subject: Unit sysinit.target has finished start-up
  657. -- Defined-By: systemd
  658. -- Support: https://www.debian.org/support
  659. --
  660. -- Unit sysinit.target has finished starting up.
  661. --
  662. -- The start-up result is done.
  663. Feb 04 18:34:44 adsbx-custom systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
  664. -- Subject: Unit avahi-daemon.socket has finished start-up
  665. -- Defined-By: systemd
  666. -- Support: https://www.debian.org/support
  667. --
  668. -- Unit avahi-daemon.socket has finished starting up.
  669. --
  670. -- The start-up result is done.
  671. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Daily Cleanup of Temporary Directories.
  672. -- Subject: Unit systemd-tmpfiles-clean.timer has finished start-up
  673. -- Defined-By: systemd
  674. -- Support: https://www.debian.org/support
  675. --
  676. -- Unit systemd-tmpfiles-clean.timer has finished starting up.
  677. --
  678. -- The start-up result is done.
  679. Feb 04 18:34:44 adsbx-custom systemd[1]: Listening on GPS (Global Positioning System) Daemon Sockets.
  680. -- Subject: Unit gpsd.socket has finished start-up
  681. -- Defined-By: systemd
  682. -- Support: https://www.debian.org/support
  683. --
  684. -- Unit gpsd.socket has finished starting up.
  685. --
  686. -- The start-up result is done.
  687. Feb 04 18:34:44 adsbx-custom systemd[1]: Listening on triggerhappy.socket.
  688. -- Subject: Unit triggerhappy.socket has finished start-up
  689. -- Defined-By: systemd
  690. -- Support: https://www.debian.org/support
  691. --
  692. -- Unit triggerhappy.socket has finished starting up.
  693. --
  694. -- The start-up result is done.
  695. Feb 04 18:34:44 adsbx-custom systemd[1]: Listening on D-Bus System Message Bus Socket.
  696. -- Subject: Unit dbus.socket has finished start-up
  697. -- Defined-By: systemd
  698. -- Support: https://www.debian.org/support
  699. --
  700. -- Unit dbus.socket has finished starting up.
  701. --
  702. -- The start-up result is done.
  703. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target Sockets.
  704. -- Subject: Unit sockets.target has finished start-up
  705. -- Defined-By: systemd
  706. -- Support: https://www.debian.org/support
  707. --
  708. -- Unit sockets.target has finished starting up.
  709. --
  710. -- The start-up result is done.
  711. Feb 04 18:34:44 adsbx-custom systemd[1]: apt-daily.timer: Adding 2h 50min 2.936589s random time.
  712. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Daily apt download activities.
  713. -- Subject: Unit apt-daily.timer has finished start-up
  714. -- Defined-By: systemd
  715. -- Support: https://www.debian.org/support
  716. --
  717. -- Unit apt-daily.timer has finished starting up.
  718. --
  719. -- The start-up result is done.
  720. Feb 04 18:34:44 adsbx-custom systemd[1]: apt-daily-upgrade.timer: Adding 8min 53.822270s random time.
  721. Feb 04 18:34:44 adsbx-custom systemd[1]: Started Daily apt upgrade and clean activities.
  722. -- Subject: Unit apt-daily-upgrade.timer has finished start-up
  723. -- Defined-By: systemd
  724. -- Support: https://www.debian.org/support
  725. --
  726. -- Unit apt-daily-upgrade.timer has finished starting up.
  727. --
  728. -- The start-up result is done.
  729. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target Timers.
  730. -- Subject: Unit timers.target has finished start-up
  731. -- Defined-By: systemd
  732. -- Support: https://www.debian.org/support
  733. --
  734. -- Unit timers.target has finished starting up.
  735. --
  736. -- The start-up result is done.
  737. Feb 04 18:34:44 adsbx-custom systemd[1]: Reached target Basic System.
  738. -- Subject: Unit basic.target has finished start-up
  739. -- Defined-By: systemd
  740. -- Support: https://www.debian.org/support
  741. --
  742. -- Unit basic.target has finished starting up.
  743. --
  744. -- The start-up result is done.
  745. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting LSB: Autogenerate and use a swap file...
  746. -- Subject: Unit dphys-swapfile.service has begun start-up
  747. -- Defined-By: systemd
  748. -- Support: https://www.debian.org/support
  749. --
  750. -- Unit dphys-swapfile.service has begun starting up.
  751. Feb 04 18:34:44 adsbx-custom systemd[1]: Starting System Logging Service...
  752. -- Subject: Unit rsyslog.service has begun start-up
  753. -- Defined-By: systemd
  754. -- Support: https://www.debian.org/support
  755. --
  756. -- Unit rsyslog.service has begun starting up.
  757. Feb 04 18:34:44 adsbx-custom systemd[1]: Started D-Bus System Message Bus.
  758. -- Subject: Unit dbus.service has finished start-up
  759. -- Defined-By: systemd
  760. -- Support: https://www.debian.org/support
  761. --
  762. -- Unit dbus.service has finished starting up.
  763. --
  764. -- The start-up result is done.
  765. Feb 04 18:34:45 adsbx-custom liblogging-stdlog[283]: [origin software="rsyslogd" swVersion="8.24.0" x-pid="283" x-info="http://www.rsyslog.com"] start
  766. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting WPA supplicant...
  767. -- Subject: Unit wpa_supplicant.service has begun start-up
  768. -- Defined-By: systemd
  769. -- Support: https://www.debian.org/support
  770. --
  771. -- Unit wpa_supplicant.service has begun starting up.
  772. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting triggerhappy global hotkey daemon...
  773. -- Subject: Unit triggerhappy.service has begun start-up
  774. -- Defined-By: systemd
  775. -- Support: https://www.debian.org/support
  776. --
  777. -- Unit triggerhappy.service has begun starting up.
  778. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting Save/Restore Sound Card State...
  779. -- Subject: Unit alsa-restore.service has begun start-up
  780. -- Defined-By: systemd
  781. -- Support: https://www.debian.org/support
  782. --
  783. -- Unit alsa-restore.service has begun starting up.
  784. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
  785. -- Subject: Unit raspi-config.service has begun start-up
  786. -- Defined-By: systemd
  787. -- Support: https://www.debian.org/support
  788. --
  789. -- Unit raspi-config.service has begun starting up.
  790. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting Disable WiFi if country not set...
  791. -- Subject: Unit wifi-country.service has begun start-up
  792. -- Defined-By: systemd
  793. -- Support: https://www.debian.org/support
  794. --
  795. -- Unit wifi-country.service has begun starting up.
  796. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting Configure Bluetooth Modems connected by UART...
  797. -- Subject: Unit hciuart.service has begun start-up
  798. -- Defined-By: systemd
  799. -- Support: https://www.debian.org/support
  800. --
  801. -- Unit hciuart.service has begun starting up.
  802. Feb 04 18:34:45 adsbx-custom thd[306]: Found socket passed from systemd
  803. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting dhcpcd on all interfaces...
  804. -- Subject: Unit dhcpcd.service has begun start-up
  805. -- Defined-By: systemd
  806. -- Support: https://www.debian.org/support
  807. --
  808. -- Unit dhcpcd.service has begun starting up.
  809. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Regular background program processing daemon.
  810. -- Subject: Unit cron.service has finished start-up
  811. -- Defined-By: systemd
  812. -- Support: https://www.debian.org/support
  813. --
  814. -- Unit cron.service has finished starting up.
  815. --
  816. -- The start-up result is done.
  817. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
  818. -- Subject: Unit avahi-daemon.service has begun start-up
  819. -- Defined-By: systemd
  820. -- Support: https://www.debian.org/support
  821. --
  822. -- Unit avahi-daemon.service has begun starting up.
  823. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
  824. -- Subject: Unit pppd-dns.service has begun start-up
  825. -- Defined-By: systemd
  826. -- Support: https://www.debian.org/support
  827. --
  828. -- Unit pppd-dns.service has begun starting up.
  829. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting Login Service...
  830. -- Subject: Unit systemd-logind.service has begun start-up
  831. -- Defined-By: systemd
  832. -- Support: https://www.debian.org/support
  833. --
  834. -- Unit systemd-logind.service has begun starting up.
  835. Feb 04 18:34:45 adsbx-custom cron[315]: (CRON) INFO (pidfile fd = 3)
  836. Feb 04 18:34:45 adsbx-custom systemd[1]: Started System Logging Service.
  837. -- Subject: Unit rsyslog.service has finished start-up
  838. -- Defined-By: systemd
  839. -- Support: https://www.debian.org/support
  840. --
  841. -- Unit rsyslog.service has finished starting up.
  842. --
  843. -- The start-up result is done.
  844. Feb 04 18:34:45 adsbx-custom systemd[1]: Started triggerhappy global hotkey daemon.
  845. -- Subject: Unit triggerhappy.service has finished start-up
  846. -- Defined-By: systemd
  847. -- Support: https://www.debian.org/support
  848. --
  849. -- Unit triggerhappy.service has finished starting up.
  850. --
  851. -- The start-up result is done.
  852. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Save/Restore Sound Card State.
  853. -- Subject: Unit alsa-restore.service has finished start-up
  854. -- Defined-By: systemd
  855. -- Support: https://www.debian.org/support
  856. --
  857. -- Unit alsa-restore.service has finished starting up.
  858. --
  859. -- The start-up result is done.
  860. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Disable WiFi if country not set.
  861. -- Subject: Unit wifi-country.service has finished start-up
  862. -- Defined-By: systemd
  863. -- Support: https://www.debian.org/support
  864. --
  865. -- Unit wifi-country.service has finished starting up.
  866. --
  867. -- The start-up result is done.
  868. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
  869. -- Subject: Unit pppd-dns.service has finished start-up
  870. -- Defined-By: systemd
  871. -- Support: https://www.debian.org/support
  872. --
  873. -- Unit pppd-dns.service has finished starting up.
  874. --
  875. -- The start-up result is done.
  876. Feb 04 18:34:45 adsbx-custom dhcpcd[312]: dev: loaded udev
  877. Feb 04 18:34:45 adsbx-custom cron[315]: (CRON) INFO (Running @reboot jobs)
  878. Feb 04 18:34:45 adsbx-custom kernel: uart-pl011 3f201000.serial: no DMA platform data
  879. Feb 04 18:34:45 adsbx-custom wpa_supplicant[305]: Successfully initialized wpa_supplicant
  880. Feb 04 18:34:45 adsbx-custom systemd[1]: Started WPA supplicant.
  881. -- Subject: Unit wpa_supplicant.service has finished start-up
  882. -- Defined-By: systemd
  883. -- Support: https://www.debian.org/support
  884. --
  885. -- Unit wpa_supplicant.service has finished starting up.
  886. --
  887. -- The start-up result is done.
  888. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: Found user 'avahi' (UID 108) and group 'avahi' (GID 112).
  889. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: Successfully dropped root privileges.
  890. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: avahi-daemon 0.6.32 starting up.
  891. Feb 04 18:34:45 adsbx-custom systemd-logind[321]: New seat seat0.
  892. -- Subject: A new seat seat0 is now available
  893. -- Defined-By: systemd
  894. -- Support: https://www.debian.org/support
  895. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  896. --
  897. -- A new seat seat0 has been configured and is now available.
  898. Feb 04 18:34:45 adsbx-custom dphys-swapfile[282]: Starting dphys-swapfile swapfile setup ...
  899. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Login Service.
  900. -- Subject: Unit systemd-logind.service has finished start-up
  901. -- Defined-By: systemd
  902. -- Support: https://www.debian.org/support
  903. --
  904. -- Unit systemd-logind.service has finished starting up.
  905. --
  906. -- The start-up result is done.
  907. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: Successfully called chroot().
  908. Feb 04 18:34:45 adsbx-custom systemd[1]: Starting Load/Save RF Kill Switch Status...
  909. -- Subject: Unit systemd-rfkill.service has begun start-up
  910. -- Defined-By: systemd
  911. -- Support: https://www.debian.org/support
  912. --
  913. -- Unit systemd-rfkill.service has begun starting up.
  914. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: Successfully dropped remaining capabilities.
  915. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Avahi mDNS/DNS-SD Stack.
  916. -- Subject: Unit avahi-daemon.service has finished start-up
  917. -- Defined-By: systemd
  918. -- Support: https://www.debian.org/support
  919. --
  920. -- Unit avahi-daemon.service has finished starting up.
  921. --
  922. -- The start-up result is done.
  923. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: No service file found in /etc/avahi/services.
  924. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: Network interface enumeration completed.
  925. Feb 04 18:34:45 adsbx-custom raspi-config[308]: Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory
  926. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Load/Save RF Kill Switch Status.
  927. -- Subject: Unit systemd-rfkill.service has finished start-up
  928. -- Defined-By: systemd
  929. -- Support: https://www.debian.org/support
  930. --
  931. -- Unit systemd-rfkill.service has finished starting up.
  932. --
  933. -- The start-up result is done.
  934. Feb 04 18:34:45 adsbx-custom avahi-daemon[317]: Server startup complete. Host name is adsbx-custom.local. Local service cookie is 668626117.
  935. Feb 04 18:34:45 adsbx-custom raspi-config[308]: No. Switching to ondemand scaling governor.
  936. Feb 04 18:34:45 adsbx-custom systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
  937. -- Subject: Unit raspi-config.service has finished start-up
  938. -- Defined-By: systemd
  939. -- Support: https://www.debian.org/support
  940. --
  941. -- Unit raspi-config.service has finished starting up.
  942. --
  943. -- The start-up result is done.
  944. Feb 04 18:34:45 adsbx-custom dphys-swapfile[282]: want /var/swap=100MByte, checking existing: keeping it
  945. Feb 04 18:34:45 adsbx-custom dhcpcd[312]: wlan0: starting wpa_supplicant
  946. Feb 04 18:34:45 adsbx-custom systemd[1]: Started Raise network interfaces.
  947. -- Subject: Unit networking.service has finished start-up
  948. -- Defined-By: systemd
  949. -- Support: https://www.debian.org/support
  950. --
  951. -- Unit networking.service has finished starting up.
  952. --
  953. -- The start-up result is done.
  954. Feb 04 18:34:45 adsbx-custom dhcpcd-run-hooks[396]: wlan0: starting wpa_supplicant
  955. Feb 04 18:34:45 adsbx-custom kernel: Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
  956. Feb 04 18:34:45 adsbx-custom dphys-swapfile[282]: done.
  957. Feb 04 18:34:45 adsbx-custom systemd[1]: Started LSB: Autogenerate and use a swap file.
  958. -- Subject: Unit dphys-swapfile.service has finished start-up
  959. -- Defined-By: systemd
  960. -- Support: https://www.debian.org/support
  961. --
  962. -- Unit dphys-swapfile.service has finished starting up.
  963. --
  964. -- The start-up result is done.
  965. Feb 04 18:34:48 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  966. Feb 04 18:34:48 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  967. Feb 04 18:34:50 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  968. Feb 04 18:34:50 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  969. Feb 04 18:34:50 adsbx-custom kernel: brcmfmac: brcmf_dongle_scantime: Scan assoc time error (-110)
  970. Feb 04 18:34:53 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  971. Feb 04 18:34:53 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  972. Feb 04 18:34:53 adsbx-custom kernel: brcmfmac: brcmf_netdev_open: failed to bring up cfg80211
  973. Feb 04 18:34:55 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  974. Feb 04 18:34:55 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  975. Feb 04 18:34:55 adsbx-custom kernel: brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)
  976. Feb 04 18:34:58 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  977. Feb 04 18:34:58 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  978. Feb 04 18:34:58 adsbx-custom kernel: brcmfmac: brcmf_cfg80211_get_tx_power: error (-110)
  979. Feb 04 18:35:01 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  980. Feb 04 18:35:01 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  981. Feb 04 18:35:03 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  982. Feb 04 18:35:03 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  983. Feb 04 18:35:06 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  984. Feb 04 18:35:06 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  985. Feb 04 18:35:06 adsbx-custom kernel: brcmfmac: brcmf_dongle_scantime: Scan assoc time error (-110)
  986. Feb 04 18:35:08 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  987. Feb 04 18:35:08 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  988. Feb 04 18:35:08 adsbx-custom kernel: brcmfmac: brcmf_netdev_open: failed to bring up cfg80211
  989. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: wlan0: failed to start wpa_supplicant
  990. Feb 04 18:35:08 adsbx-custom dhcpcd-run-hooks[401]: wlan0: failed to start wpa_supplicant
  991. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: wlan0: Successfully initialized wpa_supplicant
  992. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: Could not set interface wlan0 flags (UP): Input/output error
  993. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: nl80211: Could not set interface 'wlan0' UP
  994. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
  995. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: Could not set interface wlan0 flags (UP): Input/output error
  996. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: WEXT: Could not set interface 'wlan0' UP
  997. Feb 04 18:35:08 adsbx-custom dhcpcd[312]: wlan0: Failed to initialize driver interface
  998. Feb 04 18:35:08 adsbx-custom dhcpcd-run-hooks[402]: wlan0: Successfully initialized wpa_supplicant
  999. Could not set interface wlan0 flags (UP): Input/output error
  1000. nl80211: Could not set interface 'wlan0' UP
  1001. nl80211: deinit ifname=wlan0 disabled_11b_rates=0
  1002. Could not set interface wlan0 flags (UP): Input/output error
  1003. WEXT: Could not set interface 'wlan0' UP
  1004. wlan0: Failed to initialize driver interface
  1005. Feb 04 18:35:11 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  1006. Feb 04 18:35:11 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  1007. Feb 04 18:35:13 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  1008. Feb 04 18:35:13 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  1009. Feb 04 18:35:15 adsbx-custom btuart[311]: Initialization timed out.
  1010. Feb 04 18:35:15 adsbx-custom btuart[311]: bcm43xx_init
  1011. Feb 04 18:35:15 adsbx-custom systemd[1]: hciuart.service: Control process exited, code=exited status=1
  1012. Feb 04 18:35:15 adsbx-custom systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
  1013. -- Subject: Unit hciuart.service has failed
  1014. -- Defined-By: systemd
  1015. -- Support: https://www.debian.org/support
  1016. --
  1017. -- Unit hciuart.service has failed.
  1018. --
  1019. -- The result is failed.
  1020. Feb 04 18:35:15 adsbx-custom systemd[1]: hciuart.service: Unit entered failed state.
  1021. Feb 04 18:35:15 adsbx-custom systemd[1]: hciuart.service: Failed with result 'exit-code'.
  1022. Feb 04 18:35:16 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  1023. Feb 04 18:35:16 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  1024. Feb 04 18:35:16 adsbx-custom kernel: brcmfmac: brcmf_dongle_scantime: Scan assoc time error (-110)
  1025. Feb 04 18:35:19 adsbx-custom dhcpcd[312]: wlan0: if_up: Input/output error
  1026. Feb 04 18:35:19 adsbx-custom dhcpcd[312]: wlan0: waiting for carrier
  1027. Feb 04 18:35:19 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  1028. Feb 04 18:35:19 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  1029. Feb 04 18:35:19 adsbx-custom kernel: brcmfmac: brcmf_netdev_open: failed to bring up cfg80211
  1030. Feb 04 18:35:19 adsbx-custom dhcpcd[312]: eth0: waiting for carrier
  1031. Feb 04 18:35:19 adsbx-custom dhcpcd[312]: eth0: carrier acquired
  1032. Feb 04 18:35:19 adsbx-custom kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
  1033. Feb 04 18:35:20 adsbx-custom dhcpcd[312]: DUID 00:01:00:01:21:b0:d9:d3:b8:27:eb:ac:01:92
  1034. Feb 04 18:35:20 adsbx-custom dhcpcd[312]: eth0: IAID eb:18:dd:e4
  1035. Feb 04 18:35:20 adsbx-custom kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
  1036. Feb 04 18:35:20 adsbx-custom dhcpcd[312]: eth0: adding address fe80::7ce1:f14f:44cd:890b
  1037. Feb 04 18:35:20 adsbx-custom dhcpcd[312]: eth0: carrier lost
  1038. Feb 04 18:35:21 adsbx-custom dhcpcd[312]: eth0: deleting address fe80::7ce1:f14f:44cd:890b
  1039. Feb 04 18:35:21 adsbx-custom dhcpcd[312]: eth0: carrier acquired
  1040. Feb 04 18:35:21 adsbx-custom dhcpcd[312]: eth0: IAID eb:18:dd:e4
  1041. Feb 04 18:35:21 adsbx-custom dhcpcd[312]: eth0: adding address fe80::7ce1:f14f:44cd:890b
  1042. Feb 04 18:35:21 adsbx-custom dhcpcd[312]: eth0: rebinding lease of 192.168.1.143
  1043. Feb 04 18:35:21 adsbx-custom dhcpcd[312]: eth0: probing address 192.168.1.143/24
  1044. Feb 04 18:35:21 adsbx-custom dhcpcd[312]: eth0: soliciting an IPv6 router
  1045. Feb 04 18:35:22 adsbx-custom avahi-daemon[317]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7ce1:f14f:44cd:890b.
  1046. Feb 04 18:35:22 adsbx-custom avahi-daemon[317]: New relevant interface eth0.IPv6 for mDNS.
  1047. Feb 04 18:35:22 adsbx-custom avahi-daemon[317]: Registering new address record for fe80::7ce1:f14f:44cd:890b on eth0.*.
  1048. Feb 04 18:35:22 adsbx-custom dhcpcd[312]: eth0: Router Advertisement from fe80::26f5:a2ff:fe57:e14a
  1049. Feb 04 18:35:22 adsbx-custom dhcpcd[312]: eth0: adding address 2601:40e:8101:2f98:b344:a374:bca4:888c/64
  1050. Feb 04 18:35:22 adsbx-custom dhcpcd[312]: eth0: adding route to 2601:40e:8101:2f98::/64
  1051. Feb 04 18:35:22 adsbx-custom dhcpcd[312]: eth0: adding default route via fe80::26f5:a2ff:fe57:e14a
  1052. Feb 04 18:35:22 adsbx-custom dhcpcd[312]: eth0: requesting DHCPv6 information
  1053. Feb 04 18:35:23 adsbx-custom dhcpcd[312]: Too few arguments.
  1054. Feb 04 18:35:23 adsbx-custom dhcpcd[312]: Too few arguments.
  1055. Feb 04 18:35:23 adsbx-custom avahi-daemon[317]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::7ce1:f14f:44cd:890b.
  1056. Feb 04 18:35:23 adsbx-custom avahi-daemon[317]: Joining mDNS multicast group on interface eth0.IPv6 with address 2601:40e:8101:2f98:b344:a374:bca4:888c.
  1057. Feb 04 18:35:23 adsbx-custom avahi-daemon[317]: Registering new address record for 2601:40e:8101:2f98:b344:a374:bca4:888c on eth0.*.
  1058. Feb 04 18:35:23 adsbx-custom avahi-daemon[317]: Withdrawing address record for fe80::7ce1:f14f:44cd:890b on eth0.
  1059. Feb 04 18:35:24 adsbx-custom dhcpcd[312]: forked to background, child pid 519
  1060. Feb 04 18:35:24 adsbx-custom systemd[1]: Started dhcpcd on all interfaces.
  1061. -- Subject: Unit dhcpcd.service has finished start-up
  1062. -- Defined-By: systemd
  1063. -- Support: https://www.debian.org/support
  1064. --
  1065. -- Unit dhcpcd.service has finished starting up.
  1066. --
  1067. -- The start-up result is done.
  1068. Feb 04 18:35:24 adsbx-custom systemd[1]: Reached target Network.
  1069. -- Subject: Unit network.target has finished start-up
  1070. -- Defined-By: systemd
  1071. -- Support: https://www.debian.org/support
  1072. --
  1073. -- Unit network.target has finished starting up.
  1074. --
  1075. -- The start-up result is done.
  1076. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting Permit User Sessions...
  1077. -- Subject: Unit systemd-user-sessions.service has begun start-up
  1078. -- Defined-By: systemd
  1079. -- Support: https://www.debian.org/support
  1080. --
  1081. -- Unit systemd-user-sessions.service has begun starting up.
  1082. Feb 04 18:35:24 adsbx-custom systemd[1]: Reached target Network is Online.
  1083. -- Subject: Unit network-online.target has finished start-up
  1084. -- Defined-By: systemd
  1085. -- Support: https://www.debian.org/support
  1086. --
  1087. -- Unit network-online.target has finished starting up.
  1088. --
  1089. -- The start-up result is done.
  1090. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting /etc/rc.local Compatibility...
  1091. -- Subject: Unit rc-local.service has begun start-up
  1092. -- Defined-By: systemd
  1093. -- Support: https://www.debian.org/support
  1094. --
  1095. -- Unit rc-local.service has begun starting up.
  1096. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
  1097. -- Subject: Unit dump1090-mutability.service has begun start-up
  1098. -- Defined-By: systemd
  1099. -- Support: https://www.debian.org/support
  1100. --
  1101. -- Unit dump1090-mutability.service has begun starting up.
  1102. Feb 04 18:35:24 adsbx-custom systemd[1]: Started Grafana instance.
  1103. -- Subject: Unit grafana-server.service has finished start-up
  1104. -- Defined-By: systemd
  1105. -- Support: https://www.debian.org/support
  1106. --
  1107. -- Unit grafana-server.service has finished starting up.
  1108. --
  1109. -- The start-up result is done.
  1110. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting LSB: Shell In A Box Daemon...
  1111. -- Subject: Unit shellinabox.service has begun start-up
  1112. -- Defined-By: systemd
  1113. -- Support: https://www.debian.org/support
  1114. --
  1115. -- Unit shellinabox.service has begun starting up.
  1116. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting LSB: Start NTP daemon...
  1117. -- Subject: Unit ntp.service has begun start-up
  1118. -- Defined-By: systemd
  1119. -- Support: https://www.debian.org/support
  1120. --
  1121. -- Unit ntp.service has begun starting up.
  1122. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting Flightradar24 Decoder & Feeder...
  1123. -- Subject: Unit fr24feed.service has begun start-up
  1124. -- Defined-By: systemd
  1125. -- Support: https://www.debian.org/support
  1126. --
  1127. -- Unit fr24feed.service has begun starting up.
  1128. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting Lighttpd Daemon...
  1129. -- Subject: Unit lighttpd.service has begun start-up
  1130. -- Defined-By: systemd
  1131. -- Support: https://www.debian.org/support
  1132. --
  1133. -- Unit lighttpd.service has begun starting up.
  1134. Feb 04 18:35:24 adsbx-custom systemd[1]: Starting OpenBSD Secure Shell server...
  1135. -- Subject: Unit ssh.service has begun start-up
  1136. -- Defined-By: systemd
  1137. -- Support: https://www.debian.org/support
  1138. --
  1139. -- Unit ssh.service has begun starting up.
  1140. Feb 04 18:35:24 adsbx-custom systemd[1]: Started ZeroTier One.
  1141. -- Subject: Unit zerotier-one.service has finished start-up
  1142. -- Defined-By: systemd
  1143. -- Support: https://www.debian.org/support
  1144. --
  1145. -- Unit zerotier-one.service has finished starting up.
  1146. --
  1147. -- The start-up result is done.
  1148. Feb 04 18:35:24 adsbx-custom systemd[1]: Started Permit User Sessions.
  1149. -- Subject: Unit systemd-user-sessions.service has finished start-up
  1150. -- Defined-By: systemd
  1151. -- Support: https://www.debian.org/support
  1152. --
  1153. -- Unit systemd-user-sessions.service has finished starting up.
  1154. --
  1155. -- The start-up result is done.
  1156. Feb 04 18:35:24 adsbx-custom dump1090-mutability[522]: Not starting dump1090-mutability daemon, disabled via /etc/default/dump1090-mutability ... (warning).
  1157. Feb 04 18:35:24 adsbx-custom systemd[1]: Started LSB: dump1090 daemon (mutability variant).
  1158. -- Subject: Unit dump1090-mutability.service has finished start-up
  1159. -- Defined-By: systemd
  1160. -- Support: https://www.debian.org/support
  1161. --
  1162. -- Unit dump1090-mutability.service has finished starting up.
  1163. --
  1164. -- The start-up result is done.
  1165. Feb 04 18:35:24 adsbx-custom systemd[1]: Started Flightradar24 Decoder & Feeder.
  1166. -- Subject: Unit fr24feed.service has finished start-up
  1167. -- Defined-By: systemd
  1168. -- Support: https://www.debian.org/support
  1169. --
  1170. -- Unit fr24feed.service has finished starting up.
  1171. --
  1172. -- The start-up result is done.
  1173. Feb 04 18:35:24 adsbx-custom ntpd[565]: ntpd 4.2.8p10@1.3728-o Sat Mar 10 18:03:33 UTC 2018 (1): Starting
  1174. Feb 04 18:35:24 adsbx-custom ntpd[565]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 114:115
  1175. Feb 04 18:35:24 adsbx-custom ntp[528]: Starting NTP server: ntpd.
  1176. Feb 04 18:35:24 adsbx-custom systemd[1]: Started LSB: Start NTP daemon.
  1177. -- Subject: Unit ntp.service has finished start-up
  1178. -- Defined-By: systemd
  1179. -- Support: https://www.debian.org/support
  1180. --
  1181. -- Unit ntp.service has finished starting up.
  1182. --
  1183. -- The start-up result is done.
  1184. Feb 04 18:35:25 adsbx-custom shellinabox[525]: [config] Duplicate --port option!
  1185. Feb 04 18:35:25 adsbx-custom shellinaboxd[584]: [config] Duplicate --port option!
  1186. Feb 04 18:35:25 adsbx-custom kernel: capability: warning: `zerotier-one' uses 32-bit capabilities (legacy support in use)
  1187. Feb 04 18:35:25 adsbx-custom shellinaboxd[584]: [server] Aborting...
  1188. Feb 04 18:35:25 adsbx-custom systemd[1]: Started LSB: Shell In A Box Daemon.
  1189. -- Subject: Unit shellinabox.service has finished start-up
  1190. -- Defined-By: systemd
  1191. -- Support: https://www.debian.org/support
  1192. --
  1193. -- Unit shellinabox.service has finished starting up.
  1194. --
  1195. -- The start-up result is done.
  1196. Feb 04 18:35:25 adsbx-custom ntpd[597]: proto: precision = 1.458 usec (-19)
  1197. Feb 04 18:35:25 adsbx-custom ntpd[597]: Listen and drop on 0 v6wildcard [::]:123
  1198. Feb 04 18:35:25 adsbx-custom ntpd[597]: Listen and drop on 1 v4wildcard 0.0.0.0:123
  1199. Feb 04 18:35:25 adsbx-custom ntpd[597]: Listen normally on 2 lo 127.0.0.1:123
  1200. Feb 04 18:35:25 adsbx-custom ntpd[597]: Listen normally on 3 lo [::1]:123
  1201. Feb 04 18:35:25 adsbx-custom ntpd[597]: Listen normally on 4 eth0 [2601:40e:8101:2f98:b344:a374:bca4:888c]:123
  1202. Feb 04 18:35:25 adsbx-custom ntpd[597]: Listen normally on 5 eth0 [fe80::7ce1:f14f:44cd:890b%2]:123
  1203. Feb 04 18:35:25 adsbx-custom ntpd[597]: Listening on routing socket on fd #22 for interface updates
  1204. Feb 04 18:35:25 adsbx-custom zerotier-one[539]: sendto: Network unreachable
  1205. Feb 04 18:35:25 adsbx-custom kernel: tun: Universal TUN/TAP device driver, 1.6
  1206. Feb 04 18:35:25 adsbx-custom dhcpcd[519]: zt1: IAID bc:36:1d:0f
  1207. Feb 04 18:35:26 adsbx-custom ntpd[597]: Soliciting pool server 104.171.118.254
  1208. Feb 04 18:35:26 adsbx-custom dhcpcd[519]: zt1: soliciting a DHCP lease
  1209. Feb 04 18:35:26 adsbx-custom dhcpcd[519]: eth0: leased 192.168.1.143 for 86400 seconds
  1210. Feb 04 18:35:26 adsbx-custom avahi-daemon[317]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.143.
  1211. Feb 04 18:35:26 adsbx-custom dhcpcd[519]: eth0: adding route to 192.168.1.0/24
  1212. Feb 04 18:35:26 adsbx-custom dhcpcd[519]: eth0: adding default route via 192.168.1.1
  1213. Feb 04 18:35:26 adsbx-custom avahi-daemon[317]: New relevant interface eth0.IPv4 for mDNS.
  1214. Feb 04 18:35:26 adsbx-custom avahi-daemon[317]: Registering new address record for 192.168.1.143 on eth0.IPv4.
  1215. Feb 04 18:35:26 adsbx-custom systemd[1]: Started OpenBSD Secure Shell server.
  1216. -- Subject: Unit ssh.service has finished start-up
  1217. -- Defined-By: systemd
  1218. -- Support: https://www.debian.org/support
  1219. --
  1220. -- Unit ssh.service has finished starting up.
  1221. --
  1222. -- The start-up result is done.
  1223. Feb 04 18:35:26 adsbx-custom sshd[625]: Server listening on 0.0.0.0 port 3226.
  1224. Feb 04 18:35:26 adsbx-custom sshd[625]: Server listening on :: port 3226.
  1225. Feb 04 18:35:26 adsbx-custom dhcpcd[519]: zt1: soliciting an IPv6 router
  1226. Feb 04 18:35:26 adsbx-custom lighttpd[532]: 2019-02-04 18:35:24: (plugin.c.187) Cannot load plugin mod_proxy more than once, please fix your config (lighttpd may not accept such configs in
  1227. Feb 04 18:35:26 adsbx-custom systemd[1]: Started Lighttpd Daemon.
  1228. -- Subject: Unit lighttpd.service has finished start-up
  1229. -- Defined-By: systemd
  1230. -- Support: https://www.debian.org/support
  1231. --
  1232. -- Unit lighttpd.service has finished starting up.
  1233. --
  1234. -- The start-up result is done.
  1235. Feb 04 18:35:26 adsbx-custom lighttpd[696]: 2019-02-04 18:35:26: (plugin.c.187) Cannot load plugin mod_proxy more than once, please fix your config (lighttpd may not accept such configs in
  1236. Feb 04 18:35:27 adsbx-custom ntpd[597]: Soliciting pool server 138.197.114.122
  1237. Feb 04 18:35:27 adsbx-custom avahi-daemon[317]: Joining mDNS multicast group on interface zt1.IPv6 with address fe80::cab:bcff:fe36:1d0f.
  1238. Feb 04 18:35:27 adsbx-custom avahi-daemon[317]: New relevant interface zt1.IPv6 for mDNS.
  1239. Feb 04 18:35:27 adsbx-custom avahi-daemon[317]: Registering new address record for fe80::cab:bcff:fe36:1d0f on zt1.*.
  1240. Feb 04 18:35:28 adsbx-custom ntpd[597]: Soliciting pool server 2600:3c01::f03c:91ff:fe93:a60c
  1241. Feb 04 18:35:28 adsbx-custom ntpd[597]: Soliciting pool server 2600:1f16:7a3:8a22:a922:8e9c:be3:992a
  1242. Feb 04 18:35:28 adsbx-custom ntpd[597]: Listen normally on 6 eth0 192.168.1.143:123
  1243. Feb 04 18:35:28 adsbx-custom ntpd[597]: Listen normally on 7 zt1 [fe80::cab:bcff:fe36:1d0f%4]:123
  1244. Feb 04 18:35:29 adsbx-custom ntpd[597]: Soliciting pool server 204.9.54.119
  1245. Feb 04 18:35:29 adsbx-custom ntpd[597]: Soliciting pool server 207.244.103.95
  1246. Feb 04 18:35:29 adsbx-custom ntpd[597]: Soliciting pool server 2600:3c01::f03c:91ff:fed5:8c30
  1247. Feb 04 18:35:30 adsbx-custom ntpd[597]: Soliciting pool server 155.94.238.29
  1248. Feb 04 18:35:30 adsbx-custom ntpd[597]: Soliciting pool server 2001:4998:58:183a::1001
  1249. Feb 04 18:35:31 adsbx-custom dhcpcd[519]: zt1: probing for an IPv4LL address
  1250. Feb 04 18:35:31 adsbx-custom ntpd[597]: Soliciting pool server 204.2.134.164
  1251. Feb 04 18:35:31 adsbx-custom ntpd[597]: Soliciting pool server 107.181.191.189
  1252. Feb 04 18:35:33 adsbx-custom ntpd[597]: Soliciting pool server 103.105.51.156
  1253. Feb 04 18:35:34 adsbx-custom ntpd[597]: Soliciting pool server 71.92.69.98
  1254. Feb 04 18:35:34 adsbx-custom systemd[1]: Reloading.
  1255. Feb 04 18:35:34 adsbx-custom systemd[1]: apt-daily.timer: Adding 40min 2.245944s random time.
  1256. Feb 04 18:35:34 adsbx-custom systemd[1]: apt-daily-upgrade.timer: Adding 44min 48.021026s random time.
  1257. Feb 04 18:35:34 adsbx-custom systemd[1]: Reloading.
  1258. Feb 04 18:35:35 adsbx-custom ntpd[597]: Soliciting pool server 52.53.178.201
  1259. Feb 04 18:35:43 adsbx-custom systemd[1]: apt-daily-upgrade.timer: Adding 7min 12.065704s random time.
  1260. Feb 04 18:35:43 adsbx-custom systemd[1]: apt-daily.timer: Adding 58.527166s random time.
  1261. Feb 04 18:35:43 adsbx-custom systemd[1]: Time has been changed
  1262. -- Subject: Time change
  1263. -- Defined-By: systemd
  1264. -- Support: https://www.debian.org/support
  1265. --
  1266. -- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
  1267. Feb 04 18:35:43 adsbx-custom systemd[1]: apt-daily-upgrade.timer: Adding 25min 15.251566s random time.
  1268. Feb 04 18:35:43 adsbx-custom systemd[1]: Starting Daily apt download activities...
  1269. -- Subject: Unit apt-daily.service has begun start-up
  1270. -- Defined-By: systemd
  1271. -- Support: https://www.debian.org/support
  1272. --
  1273. -- Unit apt-daily.service has begun starting up.
  1274. Feb 04 18:35:43 adsbx-custom systemd[1]: Stopping OpenBSD Secure Shell server...
  1275. -- Subject: Unit ssh.service has begun shutting down
  1276. -- Defined-By: systemd
  1277. -- Support: https://www.debian.org/support
  1278. --
  1279. -- Unit ssh.service has begun shutting down.
  1280. Feb 04 18:35:43 adsbx-custom sshd[625]: Received signal 15; terminating.
  1281. Feb 04 18:35:43 adsbx-custom systemd[1]: Stopped OpenBSD Secure Shell server.
  1282. -- Subject: Unit ssh.service has finished shutting down
  1283. -- Defined-By: systemd
  1284. -- Support: https://www.debian.org/support
  1285. --
  1286. -- Unit ssh.service has finished shutting down.
  1287. Feb 04 18:35:43 adsbx-custom systemd[1]: Starting OpenBSD Secure Shell server...
  1288. -- Subject: Unit ssh.service has begun start-up
  1289. -- Defined-By: systemd
  1290. -- Support: https://www.debian.org/support
  1291. --
  1292. -- Unit ssh.service has begun starting up.
  1293. Feb 04 18:35:43 adsbx-custom sshd[1003]: Server listening on 0.0.0.0 port 3226.
  1294. Feb 04 18:35:43 adsbx-custom sshd[1003]: Server listening on :: port 3226.
  1295. Feb 04 18:35:43 adsbx-custom systemd[1]: Started OpenBSD Secure Shell server.
  1296. -- Subject: Unit ssh.service has finished start-up
  1297. -- Defined-By: systemd
  1298. -- Support: https://www.debian.org/support
  1299. --
  1300. -- Unit ssh.service has finished starting up.
  1301. --
  1302. -- The start-up result is done.
  1303. Feb 04 18:35:43 adsbx-custom dhcpcd[519]: zt1: using IPv4LL address 169.254.165.13
  1304. Feb 04 18:35:43 adsbx-custom avahi-daemon[317]: Joining mDNS multicast group on interface zt1.IPv4 with address 169.254.165.13.
  1305. Feb 04 18:35:43 adsbx-custom avahi-daemon[317]: New relevant interface zt1.IPv4 for mDNS.
  1306. Feb 04 18:35:43 adsbx-custom dhcpcd[519]: zt1: adding route to 169.254.0.0/16
  1307. Feb 04 18:35:43 adsbx-custom avahi-daemon[317]: Registering new address record for 169.254.165.13 on zt1.IPv4.
  1308. Feb 04 18:35:45 adsbx-custom ntpd[597]: Listen normally on 8 zt1 169.254.165.13:123
  1309. Feb 04 18:35:47 adsbx-custom dhcpcd[519]: zt1: no IPv6 Routers available
  1310. Feb 04 18:35:48 adsbx-custom systemd[1]: Started Daily apt download activities.
  1311. -- Subject: Unit apt-daily.service has finished start-up
  1312. -- Defined-By: systemd
  1313. -- Support: https://www.debian.org/support
  1314. --
  1315. -- Unit apt-daily.service has finished starting up.
  1316. --
  1317. -- The start-up result is done.
  1318. Feb 04 18:35:48 adsbx-custom systemd[1]: apt-daily.timer: Adding 7h 38min 57.347745s random time.
  1319. Feb 04 18:35:48 adsbx-custom systemd[1]: apt-daily.timer: Adding 9h 19min 17.536543s random time.
  1320. Feb 04 18:35:49 adsbx-custom rc.local[521]: rm: cannot remove '/tmp/adsbx-params': No such file or directory
  1321. Feb 04 18:35:51 adsbx-custom rc.local[521]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory
  1322. Feb 04 18:35:54 adsbx-custom sshd[1221]: Accepted password for pi from 192.168.1.146 port 51297 ssh2
  1323. Feb 04 18:35:54 adsbx-custom sshd[1221]: pam_unix(sshd:session): session opened for user pi by (uid=0)
  1324. Feb 04 18:35:54 adsbx-custom systemd[1]: Created slice User Slice of pi.
  1325. -- Subject: Unit user-1000.slice has finished start-up
  1326. -- Defined-By: systemd
  1327. -- Support: https://www.debian.org/support
  1328. --
  1329. -- Unit user-1000.slice has finished starting up.
  1330. --
  1331. -- The start-up result is done.
  1332. Feb 04 18:35:54 adsbx-custom systemd-logind[321]: New session c1 of user pi.
  1333. -- Subject: A new session c1 has been created for user pi
  1334. -- Defined-By: systemd
  1335. -- Support: https://www.debian.org/support
  1336. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1337. --
  1338. -- A new session with the ID c1 has been created for the user pi.
  1339. --
  1340. -- The leading process of the session is 1221.
  1341. Feb 04 18:35:54 adsbx-custom systemd[1]: Started Session c1 of user pi.
  1342. -- Subject: Unit session-c1.scope has finished start-up
  1343. -- Defined-By: systemd
  1344. -- Support: https://www.debian.org/support
  1345. --
  1346. -- Unit session-c1.scope has finished starting up.
  1347. --
  1348. -- The start-up result is done.
  1349. Feb 04 18:35:54 adsbx-custom systemd[1]: Starting User Manager for UID 1000...
  1350. -- Subject: Unit user@1000.service has begun start-up
  1351. -- Defined-By: systemd
  1352. -- Support: https://www.debian.org/support
  1353. --
  1354. -- Unit user@1000.service has begun starting up.
  1355. Feb 04 18:35:54 adsbx-custom systemd[1537]: pam_unix(systemd-user:session): session opened for user pi by (uid=0)
  1356. Feb 04 18:35:54 adsbx-custom systemd[1537]: Listening on GnuPG network certificate management daemon.
  1357. -- Subject: Unit UNIT has finished start-up
  1358. -- Defined-By: systemd
  1359. -- Support: https://www.debian.org/support
  1360. --
  1361. -- Unit UNIT has finished starting up.
  1362. --
  1363. -- The start-up result is done.
  1364. Feb 04 18:35:54 adsbx-custom systemd[1537]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
  1365. -- Subject: Unit UNIT has finished start-up
  1366. -- Defined-By: systemd
  1367. -- Support: https://www.debian.org/support
  1368. --
  1369. -- Unit UNIT has finished starting up.
  1370. --
  1371. -- The start-up result is done.
  1372. Feb 04 18:35:54 adsbx-custom systemd[1537]: Listening on GnuPG cryptographic agent (access for web browsers).
  1373. -- Subject: Unit UNIT has finished start-up
  1374. -- Defined-By: systemd
  1375. -- Support: https://www.debian.org/support
  1376. --
  1377. -- Unit UNIT has finished starting up.
  1378. --
  1379. -- The start-up result is done.
  1380. Feb 04 18:35:54 adsbx-custom systemd[1537]: Reached target Timers.
  1381. -- Subject: Unit UNIT has finished start-up
  1382. -- Defined-By: systemd
  1383. -- Support: https://www.debian.org/support
  1384. --
  1385. -- Unit UNIT has finished starting up.
  1386. --
  1387. -- The start-up result is done.
  1388. Feb 04 18:35:54 adsbx-custom systemd[1537]: Listening on GnuPG cryptographic agent and passphrase cache.
  1389. -- Subject: Unit UNIT has finished start-up
  1390. -- Defined-By: systemd
  1391. -- Support: https://www.debian.org/support
  1392. --
  1393. -- Unit UNIT has finished starting up.
  1394. --
  1395. -- The start-up result is done.
  1396. Feb 04 18:35:54 adsbx-custom systemd[1537]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
  1397. -- Subject: Unit UNIT has finished start-up
  1398. -- Defined-By: systemd
  1399. -- Support: https://www.debian.org/support
  1400. --
  1401. -- Unit UNIT has finished starting up.
  1402. --
  1403. -- The start-up result is done.
  1404. Feb 04 18:35:54 adsbx-custom systemd[1537]: Reached target Sockets.
  1405. -- Subject: Unit UNIT has finished start-up
  1406. -- Defined-By: systemd
  1407. -- Support: https://www.debian.org/support
  1408. --
  1409. -- Unit UNIT has finished starting up.
  1410. --
  1411. -- The start-up result is done.
  1412. Feb 04 18:35:54 adsbx-custom systemd[1537]: Reached target Paths.
  1413. -- Subject: Unit UNIT has finished start-up
  1414. -- Defined-By: systemd
  1415. -- Support: https://www.debian.org/support
  1416. --
  1417. -- Unit UNIT has finished starting up.
  1418. --
  1419. -- The start-up result is done.
  1420. Feb 04 18:35:54 adsbx-custom systemd[1537]: Reached target Basic System.
  1421. -- Subject: Unit UNIT has finished start-up
  1422. -- Defined-By: systemd
  1423. -- Support: https://www.debian.org/support
  1424. --
  1425. -- Unit UNIT has finished starting up.
  1426. --
  1427. -- The start-up result is done.
  1428. Feb 04 18:35:54 adsbx-custom systemd[1537]: Reached target Default.
  1429. -- Subject: Unit UNIT has finished start-up
  1430. -- Defined-By: systemd
  1431. -- Support: https://www.debian.org/support
  1432. --
  1433. -- Unit UNIT has finished starting up.
  1434. --
  1435. -- The start-up result is done.
  1436. Feb 04 18:35:54 adsbx-custom systemd[1537]: Startup finished in 91ms.
  1437. -- Subject: System start-up is now complete
  1438. -- Defined-By: systemd
  1439. -- Support: https://www.debian.org/support
  1440. --
  1441. -- All system services necessary queued for starting at boot have been
  1442. -- successfully started. Note that this does not mean that the machine is
  1443. -- now idle as services might still be busy with completing start-up.
  1444. --
  1445. -- Kernel start-up required KERNEL_USEC microseconds.
  1446. --
  1447. -- Initial RAM disk start-up required INITRD_USEC microseconds.
  1448. --
  1449. -- Userspace start-up required 91952 microseconds.
  1450. Feb 04 18:35:54 adsbx-custom systemd[1]: Started User Manager for UID 1000.
  1451. -- Subject: Unit user@1000.service has finished start-up
  1452. -- Defined-By: systemd
  1453. -- Support: https://www.debian.org/support
  1454. --
  1455. -- Unit user@1000.service has finished starting up.
  1456. --
  1457. -- The start-up result is done.
  1458. Feb 04 18:36:00 adsbx-custom sudo[1590]: pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/raspi-config
  1459. Feb 04 18:36:01 adsbx-custom sudo[1590]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
  1460. Feb 04 18:36:03 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  1461. Feb 04 18:36:03 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  1462. Feb 04 18:36:06 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  1463. Feb 04 18:36:06 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  1464. Feb 04 18:36:09 adsbx-custom kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
  1465. Feb 04 18:36:09 adsbx-custom kernel: brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
  1466. Feb 04 18:36:09 adsbx-custom kernel: brcmfmac: brcmf_dongle_scantime: Scan assoc time error (-110)
  1467. Feb 04 18:36:11 adsbx-custom rc.local[521]: RTNETLINK answers: Input/output error
  1468. Feb 04 18:36:11 adsbx-custom kernel: brcmfmac: brcmf_netdev_open: failed to bring up cfg80211
  1469. Feb 04 18:36:16 adsbx-custom kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
  1470. Feb 04 18:36:21 adsbx-custom kernel: brcmfmac: brcmf_dongle_scantime: Scan assoc time error (-110)
  1471. Feb 04 18:36:23 adsbx-custom kernel: brcmfmac: brcmf_netdev_open: failed to bring up cfg80211
  1472. Feb 04 18:36:29 adsbx-custom systemd[1]: Stopping LSB: Start NTP daemon...
  1473. -- Subject: Unit ntp.service has begun shutting down
  1474. -- Defined-By: systemd
  1475. -- Support: https://www.debian.org/support
  1476. --
  1477. -- Unit ntp.service has begun shutting down.
  1478. Feb 04 18:36:29 adsbx-custom ntpd[597]: ntpd exiting on signal 15 (Terminated)
  1479. Feb 04 18:36:29 adsbx-custom ntpd[597]: 2600:3c01::f03c:91ff:fe93:a60c local addr 2601:40e:8101:2f98:b344:a374:bca4:888c -> <null>
  1480. Feb 04 18:36:29 adsbx-custom ntpd[597]: 2600:1f16:7a3:8a22:a922:8e9c:be3:992a local addr 2601:40e:8101:2f98:b344:a374:bca4:888c -> <null>
  1481. Feb 04 18:36:29 adsbx-custom ntpd[597]: 204.9.54.119 local addr 192.168.1.143 -> <null>
  1482. Feb 04 18:36:29 adsbx-custom ntpd[597]: 207.244.103.95 local addr 192.168.1.143 -> <null>
  1483. Feb 04 18:36:29 adsbx-custom ntpd[597]: 2600:3c01::f03c:91ff:fed5:8c30 local addr 2601:40e:8101:2f98:b344:a374:bca4:888c -> <null>
  1484. Feb 04 18:36:29 adsbx-custom ntpd[597]: 2001:4998:58:183a::1001 local addr 2601:40e:8101:2f98:b344:a374:bca4:888c -> <null>
  1485. Feb 04 18:36:29 adsbx-custom ntpd[597]: 155.94.238.29 local addr 192.168.1.143 -> <null>
  1486. Feb 04 18:36:29 adsbx-custom ntpd[597]: 107.181.191.189 local addr 192.168.1.143 -> <null>
  1487. Feb 04 18:36:29 adsbx-custom ntpd[597]: 204.2.134.164 local addr 192.168.1.143 -> <null>
  1488. Feb 04 18:36:29 adsbx-custom ntpd[597]: 103.105.51.156 local addr 192.168.1.143 -> <null>
  1489. Feb 04 18:36:29 adsbx-custom ntpd[597]: 71.92.69.98 local addr 192.168.1.143 -> <null>
  1490. Feb 04 18:36:29 adsbx-custom ntp[1649]: Stopping NTP server: ntpd.
  1491. Feb 04 18:36:29 adsbx-custom systemd[1]: Stopped LSB: Start NTP daemon.
  1492. -- Subject: Unit ntp.service has finished shutting down
  1493. -- Defined-By: systemd
  1494. -- Support: https://www.debian.org/support
  1495. --
  1496. -- Unit ntp.service has finished shutting down.
  1497. Feb 04 18:36:29 adsbx-custom ntpd[1662]: ntpd 4.2.8p10@1.3728-o Sat Mar 10 18:03:33 UTC 2018 (1): Starting
  1498. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Command line: ntpd -q -g
  1499. Feb 04 18:36:29 adsbx-custom ntpd[1662]: proto: precision = 1.458 usec (-19)
  1500. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen and drop on 0 v6wildcard [::]:123
  1501. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen and drop on 1 v4wildcard 0.0.0.0:123
  1502. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen normally on 2 lo 127.0.0.1:123
  1503. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen normally on 3 eth0 192.168.1.143:123
  1504. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen normally on 4 zt1 169.254.165.13:123
  1505. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen normally on 5 lo [::1]:123
  1506. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen normally on 6 eth0 [2601:40e:8101:2f98:b344:a374:bca4:888c]:123
  1507. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen normally on 7 eth0 [fe80::7ce1:f14f:44cd:890b%2]:123
  1508. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listen normally on 8 zt1 [fe80::cab:bcff:fe36:1d0f%4]:123
  1509. Feb 04 18:36:29 adsbx-custom ntpd[1662]: Listening on routing socket on fd #25 for interface updates
  1510. Feb 04 18:36:30 adsbx-custom ntpd[1662]: Soliciting pool server 64.62.142.222
  1511. Feb 04 18:36:31 adsbx-custom ntpd[1662]: Soliciting pool server 173.230.144.109
  1512. Feb 04 18:36:31 adsbx-custom ntpd[1662]: Soliciting pool server 96.244.96.25
  1513. Feb 04 18:36:32 adsbx-custom ntpd[1662]: Soliciting pool server 108.61.73.244
  1514. Feb 04 18:36:32 adsbx-custom ntpd[1662]: Soliciting pool server 206.55.191.142
  1515. Feb 04 18:36:32 adsbx-custom ntpd[1662]: Soliciting pool server 2600:3c01::f03c:91ff:fed5:8c30
  1516. Feb 04 18:36:33 adsbx-custom ntpd[1662]: Soliciting pool server 2600:1f16:7a3:8a22:a922:8e9c:be3:992a
  1517. Feb 04 18:36:33 adsbx-custom ntpd[1662]: Soliciting pool server 204.2.134.164
  1518. Feb 04 18:36:33 adsbx-custom ntpd[1662]: Soliciting pool server 104.171.118.254
  1519. Feb 04 18:36:33 adsbx-custom ntpd[1662]: Soliciting pool server 204.9.54.119
  1520. Feb 04 18:36:34 adsbx-custom ntpd[1662]: Soliciting pool server 155.94.238.29
  1521. Feb 04 18:36:34 adsbx-custom ntpd[1662]: Soliciting pool server 2600:3c01::f03c:91ff:fe93:a60c
  1522. Feb 04 18:36:34 adsbx-custom ntpd[1662]: Soliciting pool server 138.197.114.122
  1523. Feb 04 18:36:35 adsbx-custom ntpd[1662]: Soliciting pool server 207.244.103.95
  1524. Feb 04 18:36:35 adsbx-custom ntpd[1662]: Soliciting pool server 2001:4998:58:183a::1001
  1525. Feb 04 18:36:36 adsbx-custom ntpd[1662]: Soliciting pool server 52.53.178.201
  1526. Feb 04 18:36:37 adsbx-custom ntpd[1662]: Soliciting pool server 71.92.69.98
  1527. Feb 04 18:36:38 adsbx-custom ntpd[1662]: ntpd: time slew +0.000406 s
  1528. Feb 04 18:36:38 adsbx-custom systemd[1]: Starting LSB: Start NTP daemon...
  1529. -- Subject: Unit ntp.service has begun start-up
  1530. -- Defined-By: systemd
  1531. -- Support: https://www.debian.org/support
  1532. --
  1533. -- Unit ntp.service has begun starting up.
  1534. Feb 04 18:36:38 adsbx-custom ntpd[1880]: ntpd 4.2.8p10@1.3728-o Sat Mar 10 18:03:33 UTC 2018 (1): Starting
  1535. Feb 04 18:36:38 adsbx-custom ntpd[1880]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 114:115
  1536. Feb 04 18:36:38 adsbx-custom ntp[1871]: Starting NTP server: ntpd.
  1537. Feb 04 18:36:38 adsbx-custom systemd[1]: Started LSB: Start NTP daemon.
  1538. -- Subject: Unit ntp.service has finished start-up
  1539. -- Defined-By: systemd
  1540. -- Support: https://www.debian.org/support
  1541. --
  1542. -- Unit ntp.service has finished starting up.
  1543. --
  1544. -- The start-up result is done.
  1545. Feb 04 18:36:38 adsbx-custom ntpd[1883]: proto: precision = 1.459 usec (-19)
  1546. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen and drop on 0 v6wildcard [::]:123
  1547. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen and drop on 1 v4wildcard 0.0.0.0:123
  1548. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen normally on 2 lo 127.0.0.1:123
  1549. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen normally on 3 eth0 192.168.1.143:123
  1550. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen normally on 4 zt1 169.254.165.13:123
  1551. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen normally on 5 lo [::1]:123
  1552. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen normally on 6 eth0 [2601:40e:8101:2f98:b344:a374:bca4:888c]:123
  1553. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen normally on 7 eth0 [fe80::7ce1:f14f:44cd:890b%2]:123
  1554. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listen normally on 8 zt1 [fe80::cab:bcff:fe36:1d0f%4]:123
  1555. Feb 04 18:36:38 adsbx-custom ntpd[1883]: Listening on routing socket on fd #25 for interface updates
  1556. Feb 04 18:36:39 adsbx-custom su[1889]: Successful su for pi by root
  1557. Feb 04 18:36:39 adsbx-custom su[1889]: + ??? root:pi
  1558. Feb 04 18:36:39 adsbx-custom su[1889]: pam_unix(su:session): session opened for user pi by (uid=0)
  1559. Feb 04 18:36:39 adsbx-custom su[1894]: Successful su for pi by root
  1560. Feb 04 18:36:39 adsbx-custom su[1894]: + ??? root:pi
  1561. Feb 04 18:36:39 adsbx-custom systemd-logind[321]: New session c2 of user pi.
  1562. -- Subject: A new session c2 has been created for user pi
  1563. -- Defined-By: systemd
  1564. -- Support: https://www.debian.org/support
  1565. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1566. --
  1567. -- A new session with the ID c2 has been created for the user pi.
  1568. --
  1569. -- The leading process of the session is 1889.
  1570. Feb 04 18:36:39 adsbx-custom systemd[1]: Started Session c2 of user pi.
  1571. -- Subject: Unit session-c2.scope has finished start-up
  1572. -- Defined-By: systemd
  1573. -- Support: https://www.debian.org/support
  1574. --
  1575. -- Unit session-c2.scope has finished starting up.
  1576. --
  1577. -- The start-up result is done.
  1578. Feb 04 18:36:39 adsbx-custom su[1894]: pam_unix(su:session): session opened for user pi by (uid=0)
  1579. Feb 04 18:36:39 adsbx-custom systemd[1]: Started Session c3 of user pi.
  1580. -- Subject: Unit session-c3.scope has finished start-up
  1581. -- Defined-By: systemd
  1582. -- Support: https://www.debian.org/support
  1583. --
  1584. -- Unit session-c3.scope has finished starting up.
  1585. --
  1586. -- The start-up result is done.
  1587. Feb 04 18:36:39 adsbx-custom systemd-logind[321]: New session c3 of user pi.
  1588. -- Subject: A new session c3 has been created for user pi
  1589. -- Defined-By: systemd
  1590. -- Support: https://www.debian.org/support
  1591. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1592. --
  1593. -- A new session with the ID c3 has been created for the user pi.
  1594. --
  1595. -- The leading process of the session is 1894.
  1596. Feb 04 18:36:39 adsbx-custom su[1889]: pam_unix(su:session): session closed for user pi
  1597. Feb 04 18:36:39 adsbx-custom rc.local[521]: Mon Feb 4 18:36:39 2019 UTC dump1090-mutability v1.15~dev starting up.
  1598. Feb 04 18:36:39 adsbx-custom rc.local[521]: Using sample converter: UC8, float path
  1599. Feb 04 18:36:39 adsbx-custom rc.local[521]: Found 2 device(s):
  1600. Feb 04 18:36:39 adsbx-custom rc.local[521]: 0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
  1601. Feb 04 18:36:39 adsbx-custom rc.local[521]: 1: Realtek, RTL2838UHIDIR, SN: 00000001
  1602. Feb 04 18:36:39 adsbx-custom rc.local[521]: Found Rafael Micro R820T tuner
  1603. Feb 04 18:36:39 adsbx-custom rc.local[521]: Max available gain is: 49.60 dB
  1604. Feb 04 18:36:39 adsbx-custom rc.local[521]: Setting gain to: 49.60 dB
  1605. Feb 04 18:36:39 adsbx-custom ntpd[1883]: Soliciting pool server 206.55.191.142
  1606. Feb 04 18:36:39 adsbx-custom rc.local[521]: Gain reported by device: 49.60 dB
  1607. Feb 04 18:36:40 adsbx-custom rc.local[521]: Mon Feb 4 18:36:40 2019 mlat-client 0.2.6 starting up
  1608. Feb 04 18:36:40 adsbx-custom kernel: random: crng init done
  1609. Feb 04 18:36:40 adsbx-custom kernel: random: 7 urandom warning(s) missed due to ratelimiting
  1610. Feb 04 18:36:40 adsbx-custom rc.local[521]: Mon Feb 4 18:36:40 2019 Beast-format results connection with 127.0.0.1:30104: connection established
  1611. Feb 04 18:36:40 adsbx-custom ntpd[1883]: Soliciting pool server 104.171.118.254
  1612. Feb 04 18:36:40 adsbx-custom ntpd[1883]: Soliciting pool server 204.2.134.164
  1613. Feb 04 18:36:41 adsbx-custom ntpd[1883]: Soliciting pool server 138.197.114.122
  1614. Feb 04 18:36:41 adsbx-custom ntpd[1883]: Soliciting pool server 64.62.142.222
  1615. Feb 04 18:36:41 adsbx-custom ntpd[1883]: Soliciting pool server 2600:3c01::f03c:91ff:fe93:a60c
  1616. Feb 04 18:36:42 adsbx-custom ntpd[1883]: Soliciting pool server 2600:3c01::f03c:91ff:fed5:8c30
  1617. Feb 04 18:36:42 adsbx-custom ntpd[1883]: Soliciting pool server 96.244.96.25
  1618. Feb 04 18:36:42 adsbx-custom ntpd[1883]: Soliciting pool server 173.230.144.109
  1619. Feb 04 18:36:42 adsbx-custom ntpd[1883]: Soliciting pool server 155.94.238.29
  1620. Feb 04 18:36:43 adsbx-custom ntpd[1883]: Soliciting pool server 207.244.103.95
  1621. Feb 04 18:36:43 adsbx-custom ntpd[1883]: Soliciting pool server 2600:1f16:7a3:8a22:a922:8e9c:be3:992a
  1622. Feb 04 18:36:43 adsbx-custom ntpd[1883]: Soliciting pool server 108.61.73.244
  1623. Feb 04 18:36:44 adsbx-custom su[1972]: Successful su for pi by root
  1624. Feb 04 18:36:44 adsbx-custom su[1972]: + ??? root:pi
  1625. Feb 04 18:36:44 adsbx-custom su[1972]: pam_unix(su:session): session opened for user pi by (uid=0)
  1626. Feb 04 18:36:44 adsbx-custom systemd[1]: Started Session c4 of user pi.
  1627. -- Subject: Unit session-c4.scope has finished start-up
  1628. -- Defined-By: systemd
  1629. -- Support: https://www.debian.org/support
  1630. --
  1631. -- Unit session-c4.scope has finished starting up.
  1632. --
  1633. -- The start-up result is done.
  1634. Feb 04 18:36:44 adsbx-custom systemd-logind[321]: New session c4 of user pi.
  1635. -- Subject: A new session c4 has been created for user pi
  1636. -- Defined-By: systemd
  1637. -- Support: https://www.debian.org/support
  1638. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1639. --
  1640. -- A new session with the ID c4 has been created for the user pi.
  1641. --
  1642. -- The leading process of the session is 1972.
  1643. Feb 04 18:36:44 adsbx-custom su[1972]: pam_unix(su:session): session closed for user pi
  1644. Feb 04 18:36:44 adsbx-custom ntpd[1883]: Soliciting pool server 204.9.54.119
  1645. Feb 04 18:36:44 adsbx-custom ntpd[1883]: Soliciting pool server 2001:4998:58:183a::1001
  1646. Feb 04 18:36:45 adsbx-custom ntpd[1883]: Soliciting pool server 107.181.191.189
  1647. Feb 04 18:36:46 adsbx-custom ntpd[1883]: Soliciting pool server 52.53.178.201
  1648. Feb 04 18:36:49 adsbx-custom su[2112]: Successful su for pi by root
  1649. Feb 04 18:36:49 adsbx-custom su[2112]: + ??? root:pi
  1650. Feb 04 18:36:49 adsbx-custom su[2112]: pam_unix(su:session): session opened for user pi by (uid=0)
  1651. Feb 04 18:36:49 adsbx-custom systemd-logind[321]: New session c5 of user pi.
  1652. -- Subject: A new session c5 has been created for user pi
  1653. -- Defined-By: systemd
  1654. -- Support: https://www.debian.org/support
  1655. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1656. --
  1657. -- A new session with the ID c5 has been created for the user pi.
  1658. --
  1659. -- The leading process of the session is 2112.
  1660. Feb 04 18:36:49 adsbx-custom systemd[1]: Started Session c5 of user pi.
  1661. -- Subject: Unit session-c5.scope has finished start-up
  1662. -- Defined-By: systemd
  1663. -- Support: https://www.debian.org/support
  1664. --
  1665. -- Unit session-c5.scope has finished starting up.
  1666. --
  1667. -- The start-up result is done.
  1668. Feb 04 18:36:49 adsbx-custom su[2112]: pam_unix(su:session): session closed for user pi
  1669. Feb 04 18:36:49 adsbx-custom su[2126]: Successful su for pi by root
  1670. Feb 04 18:36:49 adsbx-custom su[2126]: + ??? root:pi
  1671. Feb 04 18:36:49 adsbx-custom su[2126]: pam_unix(su:session): session opened for user pi by (uid=0)
  1672. Feb 04 18:36:49 adsbx-custom systemd[1]: Started Session c6 of user pi.
  1673. -- Subject: Unit session-c6.scope has finished start-up
  1674. -- Defined-By: systemd
  1675. -- Support: https://www.debian.org/support
  1676. --
  1677. -- Unit session-c6.scope has finished starting up.
  1678. --
  1679. -- The start-up result is done.
  1680. Feb 04 18:36:49 adsbx-custom systemd-logind[321]: New session c6 of user pi.
  1681. -- Subject: A new session c6 has been created for user pi
  1682. -- Defined-By: systemd
  1683. -- Support: https://www.debian.org/support
  1684. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1685. --
  1686. -- A new session with the ID c6 has been created for the user pi.
  1687. --
  1688. -- The leading process of the session is 2126.
  1689. Feb 04 18:36:49 adsbx-custom su[2126]: pam_unix(su:session): session closed for user pi
  1690. Feb 04 18:36:49 adsbx-custom su[2185]: Successful su for pi by root
  1691. Feb 04 18:36:49 adsbx-custom su[2185]: + ??? root:pi
  1692. Feb 04 18:36:49 adsbx-custom su[2185]: pam_unix(su:session): session opened for user pi by (uid=0)
  1693. Feb 04 18:36:49 adsbx-custom systemd-logind[321]: New session c7 of user pi.
  1694. -- Subject: A new session c7 has been created for user pi
  1695. -- Defined-By: systemd
  1696. -- Support: https://www.debian.org/support
  1697. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1698. --
  1699. -- A new session with the ID c7 has been created for the user pi.
  1700. --
  1701. -- The leading process of the session is 2185.
  1702. Feb 04 18:36:49 adsbx-custom systemd[1]: Started Session c7 of user pi.
  1703. -- Subject: Unit session-c7.scope has finished start-up
  1704. -- Defined-By: systemd
  1705. -- Support: https://www.debian.org/support
  1706. --
  1707. -- Unit session-c7.scope has finished starting up.
  1708. --
  1709. -- The start-up result is done.
  1710. Feb 04 18:36:50 adsbx-custom rc.local[521]: flag provided but not defined: -collector.hwmon
  1711. Feb 04 18:36:50 adsbx-custom rc.local[521]: Usage of /usr/local/bin/node_exporter:
  1712. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.diskstats.ignored-devices string
  1713. Feb 04 18:36:50 adsbx-custom rc.local[521]: Regexp of devices to ignore for diskstats. (default "^(ram|loop|fd|(h|s|v|xv)d[a-z]|nvme\\d+n\\d+p)\\d+$")
  1714. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.filesystem.ignored-fs-types string
  1715. Feb 04 18:36:50 adsbx-custom rc.local[521]: Regexp of filesystem types to ignore for filesystem collector. (default "^(sys|proc|auto)fs$")
  1716. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.filesystem.ignored-mount-points string
  1717. Feb 04 18:36:50 adsbx-custom rc.local[521]: Regexp of mount points to ignore for filesystem collector. (default "^/(sys|proc|dev)($|/)")
  1718. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.megacli.command string
  1719. Feb 04 18:36:50 adsbx-custom rc.local[521]: Command to run megacli. (default "megacli")
  1720. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.netdev.ignored-devices string
  1721. Feb 04 18:36:50 adsbx-custom rc.local[521]: Regexp of net devices to ignore for netdev collector. (default "^$")
  1722. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.ntp.protocol-version int
  1723. Feb 04 18:36:50 adsbx-custom rc.local[521]: NTP protocol version (default 4)
  1724. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.ntp.server string
  1725. Feb 04 18:36:50 adsbx-custom rc.local[521]: NTP server to use for ntp collector.
  1726. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.procfs string
  1727. Feb 04 18:36:50 adsbx-custom rc.local[521]: procfs mountpoint. (default "/proc")
  1728. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.runit.servicedir string
  1729. Feb 04 18:36:50 adsbx-custom rc.local[521]: Path to runit service directory. (default "/etc/service")
  1730. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.supervisord.url string
  1731. Feb 04 18:36:50 adsbx-custom rc.local[521]: XML RPC endpoint (default "http://localhost:9001/RPC2")
  1732. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.sysfs string
  1733. Feb 04 18:36:50 adsbx-custom rc.local[521]: sysfs mountpoint. (default "/sys")
  1734. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.systemd.private
  1735. Feb 04 18:36:50 adsbx-custom rc.local[521]: Establish a private, direct connection to systemd without dbus.
  1736. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.systemd.unit-blacklist string
  1737. Feb 04 18:36:50 adsbx-custom rc.local[521]: Regexp of systemd units to blacklist. Units must both match whitelist and not match blacklist to be included.
  1738. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.systemd.unit-whitelist string
  1739. Feb 04 18:36:50 adsbx-custom rc.local[521]: Regexp of systemd units to whitelist. Units must both match whitelist and not match blacklist to be included. (default ".+")
  1740. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.textfile.directory string
  1741. Feb 04 18:36:50 adsbx-custom rc.local[521]: Directory to read text files with metrics from.
  1742. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collector.wifi string
  1743. Feb 04 18:36:50 adsbx-custom rc.local[521]: test fixtures to use for wifi collector metrics
  1744. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collectors.enabled string
  1745. Feb 04 18:36:50 adsbx-custom rc.local[521]: Comma-separated list of collectors to use. (default "conntrack,diskstats,entropy,edac,filefd,filesystem,hwmon,infiniband,loadavg,mdad
  1746. Feb 04 18:36:50 adsbx-custom rc.local[521]: -collectors.print
  1747. Feb 04 18:36:50 adsbx-custom rc.local[521]: If true, print available collectors and exit.
  1748. Feb 04 18:36:50 adsbx-custom rc.local[521]: -log.format value
  1749. Feb 04 18:36:50 adsbx-custom rc.local[521]: Set the log target and format. Example: "logger:syslog?appname=bob&local=7" or "logger:stdout?json=true" (default "logger:stderr")
  1750. Feb 04 18:36:50 adsbx-custom rc.local[521]: -log.level value
  1751. Feb 04 18:36:50 adsbx-custom rc.local[521]: Only log messages with the given severity or above. Valid levels: [debug, info, warn, error, fatal] (default "info")
  1752. Feb 04 18:36:50 adsbx-custom rc.local[521]: -version
  1753. Feb 04 18:36:50 adsbx-custom rc.local[521]: Print version information.
  1754. Feb 04 18:36:50 adsbx-custom rc.local[521]: -web.listen-address string
  1755. Feb 04 18:36:50 adsbx-custom rc.local[521]: Address on which to expose metrics and web interface. (default ":9100")
  1756. Feb 04 18:36:50 adsbx-custom rc.local[521]: -web.telemetry-path string
  1757. Feb 04 18:36:50 adsbx-custom systemd-logind[321]: Removed session c6.
  1758. -- Subject: Session c6 has been terminated
  1759. -- Defined-By: systemd
  1760. -- Support: https://www.debian.org/support
  1761. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1762. --
  1763. -- A session with the ID c6 has been terminated.
  1764. Feb 04 18:36:50 adsbx-custom rc.local[521]: Path under which to expose metrics. (default "/metrics")
  1765. Feb 04 18:36:54 adsbx-custom su[2240]: Successful su for pi by root
  1766. Feb 04 18:36:54 adsbx-custom su[2240]: + ??? root:pi
  1767. Feb 04 18:36:54 adsbx-custom su[2240]: pam_unix(su:session): session opened for user pi by (uid=0)
  1768. Feb 04 18:36:54 adsbx-custom systemd[1]: Started Session c8 of user pi.
  1769. -- Subject: Unit session-c8.scope has finished start-up
  1770. -- Defined-By: systemd
  1771. -- Support: https://www.debian.org/support
  1772. --
  1773. -- Unit session-c8.scope has finished starting up.
  1774. --
  1775. -- The start-up result is done.
  1776. Feb 04 18:36:54 adsbx-custom systemd-logind[321]: New session c8 of user pi.
  1777. -- Subject: A new session c8 has been created for user pi
  1778. -- Defined-By: systemd
  1779. -- Support: https://www.debian.org/support
  1780. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  1781. --
  1782. -- A new session with the ID c8 has been created for the user pi.
  1783. --
  1784. -- The leading process of the session is 2240.
  1785. Feb 04 18:36:54 adsbx-custom su[2240]: pam_unix(su:session): session closed for user pi
  1786. Feb 04 18:36:55 adsbx-custom rc.local[521]: Mon Feb 4 18:36:55 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking
  1787. Feb 04 18:36:56 adsbx-custom su[2270]: Successful su for pi by root
  1788. Feb 04 18:36:56 adsbx-custom su[2270]: + /dev/pts/1 root:pi
  1789. Feb 04 18:36:56 adsbx-custom su[2270]: pam_unix(su:session): session opened for user pi by pi(uid=0)
  1790. Feb 04 18:36:57 adsbx-custom su[2270]: pam_systemd(su:session): Cannot create session: Already running in a session
  1791. Feb 04 18:36:57 adsbx-custom su[2270]: pam_unix(su:session): session closed for user pi
  1792. Feb 04 18:36:57 adsbx-custom su[2284]: Successful su for pi by root
  1793. Feb 04 18:36:57 adsbx-custom su[2284]: + /dev/pts/1 root:pi
  1794. Feb 04 18:36:57 adsbx-custom su[2284]: pam_unix(su:session): session opened for user pi by pi(uid=0)
  1795. Feb 04 18:36:57 adsbx-custom su[2284]: pam_systemd(su:session): Cannot create session: Already running in a session
  1796. Feb 04 18:36:57 adsbx-custom su[2284]: pam_unix(su:session): session closed for user pi
  1797. Feb 04 18:37:09 adsbx-custom systemd[1]: Started /etc/rc.local Compatibility.
  1798. -- Subject: Unit rc-local.service has finished start-up
  1799. -- Defined-By: systemd
  1800. -- Support: https://www.debian.org/support
  1801. --
  1802. -- Unit rc-local.service has finished starting up.
  1803. --
  1804. -- The start-up result is done.
  1805. Feb 04 18:37:09 adsbx-custom systemd[1]: Starting Terminate Plymouth Boot Screen...
  1806. -- Subject: Unit plymouth-quit.service has begun start-up
  1807. -- Defined-By: systemd
  1808. -- Support: https://www.debian.org/support
  1809. --
  1810. -- Unit plymouth-quit.service has begun starting up.
  1811. Feb 04 18:37:09 adsbx-custom systemd[1]: Starting Hold until boot process finishes up...
  1812. -- Subject: Unit plymouth-quit-wait.service has begun start-up
  1813. -- Defined-By: systemd
  1814. -- Support: https://www.debian.org/support
  1815. --
  1816. -- Unit plymouth-quit-wait.service has begun starting up.
  1817. Feb 04 18:37:09 adsbx-custom systemd[1]: Received SIGRTMIN+21 from PID 182 (plymouthd).
  1818. Feb 04 18:37:09 adsbx-custom systemd[1]: Started Terminate Plymouth Boot Screen.
  1819. -- Subject: Unit plymouth-quit.service has finished start-up
  1820. -- Defined-By: systemd
  1821. -- Support: https://www.debian.org/support
  1822. --
  1823. -- Unit plymouth-quit.service has finished starting up.
  1824. --
  1825. -- The start-up result is done.
  1826. Feb 04 18:37:09 adsbx-custom systemd[1]: Started Hold until boot process finishes up.
  1827. -- Subject: Unit plymouth-quit-wait.service has finished start-up
  1828. -- Defined-By: systemd
  1829. -- Support: https://www.debian.org/support
  1830. --
  1831. -- Unit plymouth-quit-wait.service has finished starting up.
  1832. --
  1833. -- The start-up result is done.
  1834. Feb 04 18:37:09 adsbx-custom systemd[1]: Started Getty on tty1.
  1835. -- Subject: Unit getty@tty1.service has finished start-up
  1836. -- Defined-By: systemd
  1837. -- Support: https://www.debian.org/support
  1838. --
  1839. -- Unit getty@tty1.service has finished starting up.
  1840. --
  1841. -- The start-up result is done.
  1842. Feb 04 18:37:09 adsbx-custom systemd[1]: Reached target Login Prompts.
  1843. -- Subject: Unit getty.target has finished start-up
  1844. -- Defined-By: systemd
  1845. -- Support: https://www.debian.org/support
  1846. --
  1847. -- Unit getty.target has finished starting up.
  1848. --
  1849. -- The start-up result is done.
  1850. Feb 04 18:37:09 adsbx-custom systemd[1]: Reached target Multi-User System.
  1851. -- Subject: Unit multi-user.target has finished start-up
  1852. -- Defined-By: systemd
  1853. -- Support: https://www.debian.org/support
  1854. --
  1855. -- Unit multi-user.target has finished starting up.
  1856. --
  1857. -- The start-up result is done.
  1858. Feb 04 18:37:09 adsbx-custom systemd[1]: Starting Update UTMP about System Runlevel Changes...
  1859. -- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up
  1860. -- Defined-By: systemd
  1861. -- Support: https://www.debian.org/support
  1862. --
  1863. -- Unit systemd-update-utmp-runlevel.service has begun starting up.
  1864. Feb 04 18:37:09 adsbx-custom systemd[1]: Started Update UTMP about System Runlevel Changes.
  1865. -- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
  1866. -- Defined-By: systemd
  1867. -- Support: https://www.debian.org/support
  1868. --
  1869. -- Unit systemd-update-utmp-runlevel.service has finished starting up.
  1870. --
  1871. -- The start-up result is done.
  1872. Feb 04 18:37:09 adsbx-custom systemd[1]: Startup finished in 1.691s (kernel) + 2min 19.700s (userspace) = 2min 21.391s.
  1873. -- Subject: System start-up is now complete
  1874. -- Defined-By: systemd
  1875. -- Support: https://www.debian.org/support
  1876. --
  1877. -- All system services necessary queued for starting at boot have been
  1878. -- successfully started. Note that this does not mean that the machine is
  1879. -- now idle as services might still be busy with completing start-up.
  1880. --
  1881. -- Kernel start-up required 1691712 microseconds.
  1882. --
  1883. -- Initial RAM disk start-up required INITRD_USEC microseconds.
  1884. --
  1885. -- Userspace start-up required 139700215 microseconds.
  1886. Feb 04 18:37:27 adsbx-custom rc.local[521]: Problem extracting local item 'noise' from: {'samples_processed': 0, 'bad': 0, 'unknown_icao': 0, 'samples_dropped': 0, 'strong_signals': 0, 'mod
  1887. Feb 04 18:37:38 adsbx-custom systemd[1]: Reloading.
  1888. Feb 04 18:37:39 adsbx-custom systemd[1]: apt-daily.timer: Adding 7h 54min 4.975027s random time.
  1889. Feb 04 18:37:39 adsbx-custom systemd[1]: apt-daily-upgrade.timer: Adding 7min 895.068ms random time.
  1890. Feb 04 18:37:40 adsbx-custom systemd[1]: Reloading.
  1891. Feb 04 18:37:41 adsbx-custom systemd[1]: apt-daily-upgrade.timer: Adding 29min 49.601416s random time.
  1892. Feb 04 18:37:41 adsbx-custom systemd[1]: apt-daily.timer: Adding 2h 34min 58.849091s random time.
  1893. Feb 04 18:37:41 adsbx-custom systemd[1]: Reloading.
  1894. Feb 04 18:37:42 adsbx-custom systemd[1]: apt-daily.timer: Adding 9h 28min 59.840330s random time.
  1895. Feb 04 18:37:42 adsbx-custom systemd[1]: apt-daily-upgrade.timer: Adding 9min 57.738051s random time.
  1896. Feb 04 18:37:55 adsbx-custom rc.local[521]: Mon Feb 4 18:37:55 2019 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds
  1897. Feb 04 18:38:01 adsbx-custom rc.local[521]: No binary formatter available, falling back to text format
  1898. Feb 04 18:38:02 adsbx-custom rc.local[521]: Mon Feb 4 18:38:02 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking
  1899. Feb 04 18:39:01 adsbx-custom rc.local[521]: No binary formatter available, falling back to text format
  1900. Feb 04 18:39:03 adsbx-custom rc.local[521]: Mon Feb 4 18:39:03 2019 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds
  1901. Feb 04 18:39:35 adsbx-custom rc.local[521]: Mon Feb 4 18:39:35 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking
  1902. Feb 04 18:40:01 adsbx-custom rc.local[521]: No binary formatter available, falling back to text format
  1903. Feb 04 18:40:08 adsbx-custom rc.local[521]: Mon Feb 4 18:40:08 2019 Lost connection to feed.adsbexchange.com:31090
  1904. Feb 04 18:40:08 adsbx-custom rc.local[521]: Mon Feb 4 18:40:08 2019 Reconnecting in 30.0 seconds
  1905. Feb 04 18:40:09 adsbx-custom sudo[1590]: pam_unix(sudo:session): session closed for user root
  1906. Feb 04 18:40:17 adsbx-custom sudo[3193]: pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -x
  1907. Feb 04 18:40:17 adsbx-custom sudo[3193]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
  1908. lines 1835-1883/1883 (END)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!