API tools faq
paste
Advertisement
Guest User

Untitled

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