root@Pi-Hole4:~# journalctl -xb -- Logs begin at Mon 2023-04-10 13:28:49 CDT, end at Mon 2023-04-10 13:41:30 CDT. -- Apr 10 13:28:49 Pi-Hole4 kernel: Booting Linux on physical CPU 0x0 Apr 10 13:28:49 Pi-Hole4 kernel: Linux version 5.10.103-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:24:00 GMT 2022 Apr 10 13:28:49 Pi-Hole4 kernel: CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d Apr 10 13:28:49 Pi-Hole4 kernel: CPU: div instructions available: patching division code Apr 10 13:28:49 Pi-Hole4 kernel: CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Apr 10 13:28:49 Pi-Hole4 kernel: OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1 Apr 10 13:28:49 Pi-Hole4 kernel: random: fast init done Apr 10 13:28:49 Pi-Hole4 kernel: Memory policy: Data cache writealloc Apr 10 13:28:49 Pi-Hole4 kernel: Reserved memory: created CMA memory pool at 0x000000002ac00000, size 64 MiB Apr 10 13:28:49 Pi-Hole4 kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool Apr 10 13:28:49 Pi-Hole4 kernel: Zone ranges: Apr 10 13:28:49 Pi-Hole4 kernel: DMA [mem 0x0000000000000000-0x000000002fffffff] Apr 10 13:28:49 Pi-Hole4 kernel: Normal empty Apr 10 13:28:49 Pi-Hole4 kernel: HighMem [mem 0x0000000030000000-0x000000007fffffff] Apr 10 13:28:49 Pi-Hole4 kernel: Movable zone start for each node Apr 10 13:28:49 Pi-Hole4 kernel: Early memory node ranges Apr 10 13:28:49 Pi-Hole4 kernel: node 0: [mem 0x0000000000000000-0x000000003e5fffff] Apr 10 13:28:49 Pi-Hole4 kernel: node 0: [mem 0x0000000040000000-0x000000007fffffff] Apr 10 13:28:49 Pi-Hole4 kernel: Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff] Apr 10 13:28:49 Pi-Hole4 kernel: On node 0 totalpages: 517632 Apr 10 13:28:49 Pi-Hole4 kernel: DMA zone: 1728 pages used for memmap Apr 10 13:28:49 Pi-Hole4 kernel: DMA zone: 0 pages reserved Apr 10 13:28:49 Pi-Hole4 kernel: DMA zone: 196608 pages, LIFO batch:63 Apr 10 13:28:49 Pi-Hole4 kernel: HighMem zone: 321024 pages, LIFO batch:63 Apr 10 13:28:49 Pi-Hole4 kernel: percpu: Embedded 20 pages/cpu s50828 r8192 d22900 u81920 Apr 10 13:28:49 Pi-Hole4 kernel: pcpu-alloc: s50828 r8192 d22900 u81920 alloc=20*4096 Apr 10 13:28:49 Pi-Hole4 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 Apr 10 13:28:49 Pi-Hole4 kernel: Built 1 zonelists, mobility grouping on. Total pages: 515904 Apr 10 13:28:49 Pi-Hole4 kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:27:91:B0 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=tty1 root=PARTUUID=cf30de13-4777-415f-b7b2-92ad7c0e2315 rootfstype=f2fs fsck.repair=yes rootwait quiet net.ifnames=0 Apr 10 13:28:49 Pi-Hole4 kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: mem auto-init: stack:off, heap alloc:off, heap free:off Apr 10 13:28:49 Pi-Hole4 kernel: software IO TLB: mapped [mem 0x0000000025a00000-0x0000000029a00000] (64MB) Apr 10 13:28:49 Pi-Hole4 kernel: Memory: 1900768K/2070528K available (10240K kernel code, 1366K rwdata, 3196K rodata, 2048K init, 882K bss, 104224K reserved, 65536K cma-reserved, 1284096K highmem) Apr 10 13:28:49 Pi-Hole4 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Apr 10 13:28:49 Pi-Hole4 kernel: ftrace: allocating 34355 entries in 101 pages Apr 10 13:28:49 Pi-Hole4 kernel: ftrace: allocated 101 pages with 4 groups Apr 10 13:28:49 Pi-Hole4 kernel: rcu: Hierarchical RCU implementation. Apr 10 13:28:49 Pi-Hole4 kernel: Rude variant of Tasks RCU enabled. Apr 10 13:28:49 Pi-Hole4 kernel: Tracing variant of Tasks RCU enabled. Apr 10 13:28:49 Pi-Hole4 kernel: rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. Apr 10 13:28:49 Pi-Hole4 kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 Apr 10 13:28:49 Pi-Hole4 kernel: GIC: Using split EOI/Deactivate mode Apr 10 13:28:49 Pi-Hole4 kernel: random: get_random_bytes called from start_kernel+0x3c8/0x59c with crng_init=1 Apr 10 13:28:49 Pi-Hole4 kernel: sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns Apr 10 13:28:49 Pi-Hole4 kernel: clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns Apr 10 13:28:49 Pi-Hole4 kernel: bcm2835: system timer (irq = 25) Apr 10 13:28:49 Pi-Hole4 kernel: arch_timer: cp15 timer(s) running at 54.00MHz (phys). Apr 10 13:28:49 Pi-Hole4 kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns Apr 10 13:28:49 Pi-Hole4 kernel: sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns Apr 10 13:28:49 Pi-Hole4 kernel: Switching to timer-based delay loop, resolution 18ns Apr 10 13:28:49 Pi-Hole4 kernel: Console: colour dummy device 80x30 Apr 10 13:28:49 Pi-Hole4 kernel: printk: console [tty1] enabled Apr 10 13:28:49 Pi-Hole4 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=540000) Apr 10 13:28:49 Pi-Hole4 kernel: pid_max: default: 32768 minimum: 301 Apr 10 13:28:49 Pi-Hole4 kernel: LSM: Security Framework initializing Apr 10 13:28:49 Pi-Hole4 kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: cgroup: Disabling memory control group subsystem Apr 10 13:28:49 Pi-Hole4 kernel: CPU: Testing write buffer coherency: ok Apr 10 13:28:49 Pi-Hole4 kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Apr 10 13:28:49 Pi-Hole4 kernel: Setting up static identity map for 0x200000 - 0x20003c Apr 10 13:28:49 Pi-Hole4 kernel: rcu: Hierarchical SRCU implementation. Apr 10 13:28:49 Pi-Hole4 kernel: smp: Bringing up secondary CPUs ... Apr 10 13:28:49 Pi-Hole4 kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 Apr 10 13:28:49 Pi-Hole4 kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 Apr 10 13:28:49 Pi-Hole4 kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Apr 10 13:28:49 Pi-Hole4 kernel: smp: Brought up 1 node, 4 CPUs Apr 10 13:28:49 Pi-Hole4 kernel: SMP: Total of 4 processors activated (432.00 BogoMIPS). Apr 10 13:28:49 Pi-Hole4 kernel: CPU: All CPU(s) started in HYP mode. Apr 10 13:28:49 Pi-Hole4 kernel: CPU: Virtualization extensions available. Apr 10 13:28:49 Pi-Hole4 kernel: devtmpfs: initialized Apr 10 13:28:49 Pi-Hole4 kernel: VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0 Apr 10 13:28:49 Pi-Hole4 kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Apr 10 13:28:49 Pi-Hole4 kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: pinctrl core: initialized pinctrl subsystem Apr 10 13:28:49 Pi-Hole4 kernel: NET: Registered protocol family 16 Apr 10 13:28:49 Pi-Hole4 kernel: DMA: preallocated 1024 KiB pool for atomic coherent allocations Apr 10 13:28:49 Pi-Hole4 kernel: audit: initializing netlink subsys (disabled) Apr 10 13:28:49 Pi-Hole4 kernel: audit: type=2000 audit(0.010:1): state=initialized audit_enabled=0 res=1 Apr 10 13:28:49 Pi-Hole4 kernel: thermal_sys: Registered thermal governor 'step_wise' Apr 10 13:28:49 Pi-Hole4 kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. Apr 10 13:28:49 Pi-Hole4 kernel: hw-breakpoint: maximum watchpoint size is 8 bytes. Apr 10 13:28:49 Pi-Hole4 kernel: Serial: AMBA PL011 UART driver Apr 10 13:28:49 Pi-Hole4 kernel: bcm2835-mbox fe00b880.mailbox: mailbox enabled Apr 10 13:28:49 Pi-Hole4 kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2021-12-01T15:02:10, variant start_cd Apr 10 13:28:49 Pi-Hole4 kernel: raspberrypi-firmware soc:firmware: Firmware hash is 71bd3109023a0c8575585ba87cbb374d2eeb038f Apr 10 13:28:49 Pi-Hole4 kernel: Kprobes globally optimized Apr 10 13:28:49 Pi-Hole4 kernel: bcm2835-dma fe007000.dma: DMA legacy API manager, dmachans=0x1 Apr 10 13:28:49 Pi-Hole4 kernel: vgaarb: loaded Apr 10 13:28:49 Pi-Hole4 kernel: SCSI subsystem initialized Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver usbfs Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver hub Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new device driver usb Apr 10 13:28:49 Pi-Hole4 kernel: usb_phy_generic phy: supply vcc not found, using dummy regulator Apr 10 13:28:49 Pi-Hole4 kernel: clocksource: Switched to clocksource arch_sys_counter Apr 10 13:28:49 Pi-Hole4 kernel: VFS: Disk quotas dquot_6.6.0 Apr 10 13:28:49 Pi-Hole4 kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Apr 10 13:28:49 Pi-Hole4 kernel: FS-Cache: Loaded Apr 10 13:28:49 Pi-Hole4 kernel: CacheFiles: Loaded Apr 10 13:28:49 Pi-Hole4 kernel: NET: Registered protocol family 2 Apr 10 13:28:49 Pi-Hole4 kernel: IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: TCP: Hash tables configured (established 8192 bind 8192) Apr 10 13:28:49 Pi-Hole4 kernel: UDP hash table entries: 512 (order: 2, 16384 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) Apr 10 13:28:49 Pi-Hole4 kernel: NET: Registered protocol family 1 Apr 10 13:28:49 Pi-Hole4 kernel: RPC: Registered named UNIX socket transport module. Apr 10 13:28:49 Pi-Hole4 kernel: RPC: Registered udp transport module. Apr 10 13:28:49 Pi-Hole4 kernel: RPC: Registered tcp transport module. Apr 10 13:28:49 Pi-Hole4 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Apr 10 13:28:49 Pi-Hole4 kernel: PCI: CLS 0 bytes, default 64 Apr 10 13:28:49 Pi-Hole4 kernel: Initialise system trusted keyrings Apr 10 13:28:49 Pi-Hole4 kernel: workingset: timestamp_bits=14 max_order=19 bucket_order=5 Apr 10 13:28:49 Pi-Hole4 kernel: zbud: loaded Apr 10 13:28:49 Pi-Hole4 kernel: FS-Cache: Netfs 'nfs' registered for caching Apr 10 13:28:49 Pi-Hole4 kernel: NFS: Registering the id_resolver key type Apr 10 13:28:49 Pi-Hole4 kernel: Key type id_resolver registered Apr 10 13:28:49 Pi-Hole4 kernel: Key type id_legacy registered Apr 10 13:28:49 Pi-Hole4 kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering... Apr 10 13:28:49 Pi-Hole4 kernel: nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... Apr 10 13:28:49 Pi-Hole4 kernel: Key type asymmetric registered Apr 10 13:28:49 Pi-Hole4 kernel: Asymmetric key parser 'x509' registered Apr 10 13:28:49 Pi-Hole4 kernel: bounce: pool size: 64 pages Apr 10 13:28:49 Pi-Hole4 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) Apr 10 13:28:49 Pi-Hole4 kernel: io scheduler mq-deadline registered Apr 10 13:28:49 Pi-Hole4 kernel: io scheduler kyber registered Apr 10 13:28:49 Pi-Hole4 kernel: brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges: Apr 10 13:28:49 Pi-Hole4 kernel: brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500000, using [bus 00-ff] Apr 10 13:28:49 Pi-Hole4 kernel: brcm-pcie fd500000.pcie: MEM 0x0600000000..0x063fffffff -> 0x00c0000000 Apr 10 13:28:49 Pi-Hole4 kernel: brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x007fffffff -> 0x0400000000 Apr 10 13:28:49 Pi-Hole4 kernel: brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC) Apr 10 13:28:49 Pi-Hole4 kernel: brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00 Apr 10 13:28:49 Pi-Hole4 kernel: pci_bus 0000:00: root bus resource [bus 00-ff] Apr 10 13:28:49 Pi-Hole4 kernel: pci_bus 0000:00: root bus resource [mem 0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff]) Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400 Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:00:00.0: PME# supported from D0 D3hot Apr 10 13:28:49 Pi-Hole4 kernel: PCI: bus0: Fast back to back transfers disabled Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330 Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit] Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:01:00.0: PME# supported from D0 D3cold Apr 10 13:28:49 Pi-Hole4 kernel: PCI: bus1: Fast back to back transfers disabled Apr 10 13:28:49 Pi-Hole4 kernel: pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff] Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit] Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:00:00.0: PCI bridge to [bus 01] Apr 10 13:28:49 Pi-Hole4 kernel: pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff] Apr 10 13:28:49 Pi-Hole4 kernel: pcieport 0000:00:00.0: enabling device (0140 -> 0142) Apr 10 13:28:49 Pi-Hole4 kernel: pcieport 0000:00:00.0: PME: Signaling with IRQ 61 Apr 10 13:28:49 Pi-Hole4 kernel: bcm2708_fb soc:fb: FB found 1 display(s) Apr 10 13:28:49 Pi-Hole4 kernel: Console: switching to colour frame buffer device 240x67 Apr 10 13:28:49 Pi-Hole4 kernel: bcm2708_fb soc:fb: Registered framebuffer for display 0, size 1920x1080 Apr 10 13:28:49 Pi-Hole4 kernel: iproc-rng200 fe104000.rng: hwrng registered Apr 10 13:28:49 Pi-Hole4 kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3f000000 mem_size:0x3f600000(1014 MiB) Apr 10 13:28:49 Pi-Hole4 kernel: gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000 Apr 10 13:28:49 Pi-Hole4 kernel: brd: module loaded Apr 10 13:28:49 Pi-Hole4 kernel: loop: module loaded Apr 10 13:28:49 Pi-Hole4 kernel: Loading iSCSI transport class v2.0-870. Apr 10 13:28:49 Pi-Hole4 kernel: bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000 Apr 10 13:28:49 Pi-Hole4 kernel: unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver r8152 Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver lan78xx Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver smsc95xx Apr 10 13:28:49 Pi-Hole4 kernel: xhci_hcd 0000:01:00.0: enabling device (0140 -> 0142) Apr 10 13:28:49 Pi-Hole4 kernel: xhci_hcd 0000:01:00.0: xHCI Host Controller Apr 10 13:28:49 Pi-Hole4 kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 Apr 10 13:28:49 Pi-Hole4 kernel: xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000060000000890 Apr 10 13:28:49 Pi-Hole4 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10 Apr 10 13:28:49 Pi-Hole4 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Apr 10 13:28:49 Pi-Hole4 kernel: usb usb1: Product: xHCI Host Controller Apr 10 13:28:49 Pi-Hole4 kernel: usb usb1: Manufacturer: Linux 5.10.103-v7l+ xhci-hcd Apr 10 13:28:49 Pi-Hole4 kernel: usb usb1: SerialNumber: 0000:01:00.0 Apr 10 13:28:49 Pi-Hole4 kernel: hub 1-0:1.0: USB hub found Apr 10 13:28:49 Pi-Hole4 kernel: hub 1-0:1.0: 1 port detected Apr 10 13:28:49 Pi-Hole4 kernel: xhci_hcd 0000:01:00.0: xHCI Host Controller Apr 10 13:28:49 Pi-Hole4 kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2 Apr 10 13:28:49 Pi-Hole4 kernel: xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed Apr 10 13:28:49 Pi-Hole4 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10 Apr 10 13:28:49 Pi-Hole4 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Apr 10 13:28:49 Pi-Hole4 kernel: usb usb2: Product: xHCI Host Controller Apr 10 13:28:49 Pi-Hole4 kernel: usb usb2: Manufacturer: Linux 5.10.103-v7l+ xhci-hcd Apr 10 13:28:49 Pi-Hole4 kernel: usb usb2: SerialNumber: 0000:01:00.0 Apr 10 13:28:49 Pi-Hole4 kernel: hub 2-0:1.0: USB hub found Apr 10 13:28:49 Pi-Hole4 kernel: hub 2-0:1.0: 4 ports detected Apr 10 13:28:49 Pi-Hole4 kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Apr 10 13:28:49 Pi-Hole4 kernel: dwc_otg: FIQ enabled Apr 10 13:28:49 Pi-Hole4 kernel: dwc_otg: NAK holdoff enabled Apr 10 13:28:49 Pi-Hole4 kernel: dwc_otg: FIQ split-transaction FSM enabled Apr 10 13:28:49 Pi-Hole4 kernel: Module dwc_common_port init Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver uas Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver usb-storage Apr 10 13:28:49 Pi-Hole4 kernel: mousedev: PS/2 mouse device common for all mice Apr 10 13:28:49 Pi-Hole4 kernel: bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer Apr 10 13:28:49 Pi-Hole4 kernel: sdhci: Secure Digital Host Controller Interface driver Apr 10 13:28:49 Pi-Hole4 kernel: sdhci: Copyright(c) Pierre Ossman Apr 10 13:28:49 Pi-Hole4 kernel: sdhci-pltfm: SDHCI platform and OF driver helper Apr 10 13:28:49 Pi-Hole4 kernel: ledtrig-cpu: registered to indicate activity on CPUs Apr 10 13:28:49 Pi-Hole4 kernel: hid: raw HID events driver (C) Jiri Kosina Apr 10 13:28:49 Pi-Hole4 kernel: usbcore: registered new interface driver usbhid Apr 10 13:28:49 Pi-Hole4 kernel: usbhid: USB HID core driver Apr 10 13:28:49 Pi-Hole4 kernel: Initializing XFRM netlink socket Apr 10 13:28:49 Pi-Hole4 kernel: NET: Registered protocol family 17 Apr 10 13:28:49 Pi-Hole4 kernel: Key type dns_resolver registered Apr 10 13:28:49 Pi-Hole4 kernel: Registering SWP/SWPB emulation handler Apr 10 13:28:49 Pi-Hole4 kernel: registered taskstats version 1 Apr 10 13:28:49 Pi-Hole4 kernel: Loading compiled-in X.509 certificates Apr 10 13:28:49 Pi-Hole4 kernel: Key type ._fscrypt registered Apr 10 13:28:49 Pi-Hole4 kernel: Key type .fscrypt registered Apr 10 13:28:49 Pi-Hole4 kernel: Key type fscrypt-provisioning registered Apr 10 13:28:49 Pi-Hole4 kernel: uart-pl011 fe201000.serial: there is not valid maps for state default Apr 10 13:28:49 Pi-Hole4 kernel: uart-pl011 fe201000.serial: cts_event_workaround enabled Apr 10 13:28:49 Pi-Hole4 kernel: fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2 Apr 10 13:28:49 Pi-Hole4 kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver Apr 10 13:28:49 Pi-Hole4 kernel: of_cfs_init Apr 10 13:28:49 Pi-Hole4 kernel: of_cfs_init: OK Apr 10 13:28:49 Pi-Hole4 kernel: mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA Apr 10 13:28:49 Pi-Hole4 kernel: Waiting for root device PARTUUID=cf30de13-4777-415f-b7b2-92ad7c0e2315... Apr 10 13:28:49 Pi-Hole4 kernel: mmc0: new ultra high speed DDR50 SDHC card at address 5048 Apr 10 13:28:49 Pi-Hole4 kernel: mmcblk0: mmc0:5048 SD32G 28.9 GiB Apr 10 13:28:49 Pi-Hole4 kernel: mmcblk0: p1 p2 Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21 Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1: Product: USB2.0 Hub Apr 10 13:28:49 Pi-Hole4 kernel: hub 1-1:1.0: USB hub found Apr 10 13:28:49 Pi-Hole4 kernel: hub 1-1:1.0: 4 ports detected Apr 10 13:28:49 Pi-Hole4 kernel: usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd Apr 10 13:28:49 Pi-Hole4 kernel: usb 2-2: New USB device found, idVendor=090c, idProduct=2021, bcdDevice=11.00 Apr 10 13:28:49 Pi-Hole4 kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 10 13:28:49 Pi-Hole4 kernel: usb 2-2: Product: USB Flash Disk Apr 10 13:28:49 Pi-Hole4 kernel: usb 2-2: Manufacturer: General Apr 10 13:28:49 Pi-Hole4 kernel: usb 2-2: SerialNumber: 0308400000000449 Apr 10 13:28:49 Pi-Hole4 kernel: usb-storage 2-2:1.0: USB Mass Storage device detected Apr 10 13:28:49 Pi-Hole4 kernel: scsi host0: usb-storage 2-2:1.0 Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1.3: new low-speed USB device number 3 using xhci_hcd Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1.3: New USB device found, idVendor=413c, idProduct=2003, bcdDevice= 3.01 Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1.3: Product: Dell USB Keyboard Apr 10 13:28:49 Pi-Hole4 kernel: usb 1-1.3: Manufacturer: Dell Apr 10 13:28:49 Pi-Hole4 kernel: input: Dell Dell USB Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:413C:2003.0001/input/input0 Apr 10 13:28:49 Pi-Hole4 kernel: hid-generic 0003:413C:2003.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:01:00.0-1.3/input0 Apr 10 13:28:49 Pi-Hole4 kernel: scsi 0:0:0:0: Direct-Access General USB Flash Disk 1100 PQ: 0 ANSI: 6 Apr 10 13:28:49 Pi-Hole4 kernel: sd 0:0:0:0: [sda] 484659200 512-byte logical blocks: (248 GB/231 GiB) Apr 10 13:28:49 Pi-Hole4 kernel: sd 0:0:0:0: [sda] Write Protect is off Apr 10 13:28:49 Pi-Hole4 kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 Apr 10 13:28:49 Pi-Hole4 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 10 13:28:49 Pi-Hole4 kernel: sda: sda1 Apr 10 13:28:49 Pi-Hole4 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Apr 10 13:28:49 Pi-Hole4 kernel: F2FS-fs (sda1): recover fsync data on readonly fs Apr 10 13:28:49 Pi-Hole4 kernel: F2FS-fs (sda1): Mounted with checkpoint version = 5f118fe0 Apr 10 13:28:49 Pi-Hole4 kernel: VFS: Mounted root (f2fs filesystem) readonly on device 8:1. Apr 10 13:28:49 Pi-Hole4 kernel: devtmpfs: mounted Apr 10 13:28:49 Pi-Hole4 kernel: Freeing unused kernel memory: 2048K Apr 10 13:28:49 Pi-Hole4 kernel: Run /sbin/init as init process Apr 10 13:28:49 Pi-Hole4 kernel: with arguments: Apr 10 13:28:49 Pi-Hole4 kernel: /sbin/init Apr 10 13:28:49 Pi-Hole4 kernel: with environment: Apr 10 13:28:49 Pi-Hole4 kernel: HOME=/ Apr 10 13:28:49 Pi-Hole4 kernel: TERM=linux Apr 10 13:28:49 Pi-Hole4 systemd[1]: System time before build time, advancing clock. Apr 10 13:28:49 Pi-Hole4 kernel: NET: Registered protocol family 10 Apr 10 13:28:49 Pi-Hole4 kernel: Segment Routing with IPv6 Apr 10 13:28:49 Pi-Hole4 systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) Apr 10 13:28:49 Pi-Hole4 systemd[1]: Detected architecture arm. Apr 10 13:28:49 Pi-Hole4 systemd[1]: Set hostname to . Apr 10 13:28:49 Pi-Hole4 kernel: random: systemd: uninitialized urandom read (16 bytes read) Apr 10 13:28:49 Pi-Hole4 kernel: random: systemd: uninitialized urandom read (16 bytes read) Apr 10 13:28:49 Pi-Hole4 systemd[1]: Started Forward Password Requests to Wall Directory Watch. Apr 10 13:28:49 Pi-Hole4 kernel: random: systemd: uninitialized urandom read (16 bytes read) Apr 10 13:28:49 Pi-Hole4 systemd[1]: Listening on Journal Socket. Apr 10 13:28:49 Pi-Hole4 systemd[1]: Starting Create list of required static device nodes for the current kernel... Apr 10 13:28:49 Pi-Hole4 systemd[1]: Mounting Kernel Debug File System... Apr 10 13:28:49 Pi-Hole4 systemd[1]: Reached target Slices. Apr 10 13:28:49 Pi-Hole4 systemd[1]: Listening on initctl Compatibility Named Pipe. Apr 10 13:28:49 Pi-Hole4 systemd[1]: Listening on RPCbind Server Activation Socket. Apr 10 13:28:49 Pi-Hole4 systemd-journald[132]: Journal started -- Subject: The journal has been started -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The system journal process has started up, opened the journal -- files for writing and is now ready to process requests. Apr 10 13:28:49 Pi-Hole4 systemd-journald[132]: Runtime journal (/run/log/journal/d958eb55ba6b44d7b033f9a3ddb9a4ed) is 8.0M, max 96.1M, 88.1M free. -- Subject: Disk space used by the journal -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Runtime journal (/run/log/journal/d958eb55ba6b44d7b033f9a3ddb9a4ed) is currently using 8.0M. -- Maximum allowed usage is set to 96.1M. -- Leaving at least 144.1M free (of currently available 953.0M of disk space). -- Enforced usage limit is thus 96.1M, of which 88.1M are still available. -- -- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Apr 10 13:28:49 Pi-Hole4 systemd-fsck[146]: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system. Apr 10 13:28:49 Pi-Hole4 fake-hwclock[119]: Mon 10 Apr 18:28:49 UTC 2023 Apr 10 13:28:49 Pi-Hole4 systemd[1]: Started Set the console keyboard layout. -- Subject: A start job for unit keyboard-setup.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit keyboard-setup.service has finished successfully. -- -- The job identifier is 37. Apr 10 13:28:49 Pi-Hole4 systemd[1]: Started udev Coldplug all Devices. -- Subject: A start job for unit systemd-udev-trigger.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-udev-trigger.service has finished successfully. -- -- The job identifier is 47. Apr 10 13:28:49 Pi-Hole4 systemd[1]: Starting Helper to synchronize boot up for ifupdown... -- Subject: A start job for unit ifupdown-pre.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifupdown-pre.service has begun execution. -- -- The job identifier is 82. Apr 10 13:28:54 Pi-Hole4 kernel: random: crng init done Apr 10 13:28:54 Pi-Hole4 kernel: random: 7 urandom warning(s) missed due to ratelimiting Apr 10 13:30:19 Pi-Hole4 systemd[1]: dev-disk-by\x2dpartuuid-6c586e13\x2d01.device: Job dev-disk-by\x2dpartuuid-6c586e13\x2d01.device/start timed out. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Timed out waiting for device /dev/disk/by-partuuid/6c586e13-01. -- Subject: A start job for unit dev-disk-by\x2dpartuuid-6c586e13\x2d01.device has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dev-disk-by\x2dpartuuid-6c586e13\x2d01.device has finished with a failure. -- -- The job identifier is 17 and the job result is timeout. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Dependency failed for File System Check on /dev/disk/by-partuuid/6c586e13-01. -- Subject: A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service has finished with a failure. -- -- The job identifier is 15 and the job result is dependency. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Dependency failed for /boot. -- Subject: A start job for unit boot.mount has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit boot.mount has finished with a failure. -- -- The job identifier is 14 and the job result is dependency. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Dependency failed for Local File Systems. -- Subject: A start job for unit local-fs.target has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit local-fs.target has finished with a failure. -- -- The job identifier is 10 and the job result is dependency. Apr 10 13:30:19 Pi-Hole4 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Apr 10 13:30:19 Pi-Hole4 systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Apr 10 13:30:19 Pi-Hole4 systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'. Apr 10 13:30:19 Pi-Hole4 systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service: Job systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service/start failed with result 'dependency'. Apr 10 13:30:19 Pi-Hole4 systemd[1]: dev-disk-by\x2dpartuuid-6c586e13\x2d01.device: Job dev-disk-by\x2dpartuuid-6c586e13\x2d01.device/start failed with result 'timeout'. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Started vmtouch. -- Subject: A start job for unit vmtouch.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit vmtouch.service has finished successfully. -- -- The job identifier is 19. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Starting Set console font and keymap... -- Subject: A start job for unit console-setup.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit console-setup.service has begun execution. -- -- The job identifier is 100. Apr 10 13:30:19 Pi-Hole4 vmtouch[168]: vmtouch: WARNING: unable to stat /boot/dietpi (No such file or directory) Apr 10 13:30:19 Pi-Hole4 vmtouch[168]: vmtouch: WARNING: unable to stat /boot/dietpi.txt (No such file or directory) Apr 10 13:30:19 Pi-Hole4 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 76. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Reached target Timers. -- Subject: A start job for unit timers.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit timers.target has finished successfully. -- -- The job identifier is 59. Apr 10 13:30:19 Pi-Hole4 systemd[1]: systemd-ask-password-console.path: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-ask-password-console.path has successfully entered the 'dead' state. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. -- Subject: A stop job for unit systemd-ask-password-console.path has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit systemd-ask-password-console.path has finished. -- -- The job identifier is 158 and the job result is done. Apr 10 13:30:19 Pi-Hole4 systemd[1]: systemd-ask-password-wall.path: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-ask-password-wall.path has successfully entered the 'dead' state. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch. -- Subject: A stop job for unit systemd-ask-password-wall.path has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit systemd-ask-password-wall.path has finished. -- -- The job identifier is 157 and the job result is done. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Reached target Host and Network Name Lookups. -- Subject: A start job for unit nss-lookup.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nss-lookup.target has finished successfully. -- -- The job identifier is 102. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Reached target Login Prompts. -- Subject: A start job for unit getty.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit getty.target has finished successfully. -- -- The job identifier is 86. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Reached target Network (Pre). -- Subject: A start job for unit network-pre.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit network-pre.target has finished successfully. -- -- The job identifier is 93. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Reached target Sockets. -- Subject: A start job for unit sockets.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit sockets.target has finished successfully. -- -- The job identifier is 64. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. -- Subject: A start job for unit systemd-machine-id-commit.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-machine-id-commit.service has finished successfully. -- -- The job identifier is 38. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Started Emergency Shell. -- Subject: A start job for unit emergency.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit emergency.service has finished successfully. -- -- The job identifier is 118. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Reached target Emergency Mode. -- Subject: A start job for unit emergency.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit emergency.target has finished successfully. -- -- The job identifier is 117. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Started Set console font and keymap. -- Subject: A start job for unit console-setup.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit console-setup.service has finished successfully. -- -- The job identifier is 100. Apr 10 13:30:19 Pi-Hole4 systemd[1]: nfs-config.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit nfs-config.service has successfully entered the 'dead' state. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Started Preprocess NFS configuration. -- Subject: A start job for unit nfs-config.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nfs-config.service has finished successfully. -- -- The job identifier is 76. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped. -- Subject: A start job for unit rpc-svcgssd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpc-svcgssd.service has finished successfully. -- -- The job identifier is 77. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped. -- Subject: A start job for unit rpc-gssd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpc-gssd.service has finished successfully. -- -- The job identifier is 74. Apr 10 13:30:19 Pi-Hole4 systemd[1]: Reached target NFS client services. -- Subject: A start job for unit nfs-client.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nfs-client.target has finished successfully. -- -- The job identifier is 71. Apr 10 13:30:24 Pi-Hole4 systemd[174]: emergency.service: Executable /bin/plymouth missing, skipping: No such file or directory -- Subject: Process /bin/plymouth could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /bin/plymouth could not be executed and failed. -- -- The error number returned by this process is ERRNO. Apr 10 13:30:49 Pi-Hole4 systemd[1]: Started Helper to synchronize boot up for ifupdown. -- Subject: A start job for unit ifupdown-pre.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifupdown-pre.service has finished successfully. -- -- The job identifier is 82. Apr 10 13:30:49 Pi-Hole4 systemd[1]: Starting Raise network interfaces... -- Subject: A start job for unit networking.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit networking.service has begun execution. -- -- The job identifier is 81. Apr 10 13:30:50 Pi-Hole4 systemd[1]: Started Raise network interfaces. -- Subject: A start job for unit networking.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit networking.service has finished successfully. -- -- The job identifier is 81. Apr 10 13:30:50 Pi-Hole4 systemd[1]: Reached target Network. -- Subject: A start job for unit network.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit network.target has finished successfully. -- -- The job identifier is 83. Apr 10 13:30:50 Pi-Hole4 systemd[1]: Reached target Network is Online. -- Subject: A start job for unit network-online.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit network-online.target has finished successfully. -- -- The job identifier is 85. Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: Force to fix corruption Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: Mounted device! Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: Check FS only due to RO Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: [/dev/sda1] Disk Model: USB Flash Disk 1100 Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [2B blob data] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: smi Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [1B blob data] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: Segments per section = 1 Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: Sections per zone = 1 Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: sector size = 512 Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: total sectors = 484655104 (236648 MB) Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: MKFS version Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: "Linux version 5.10.103-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:24:00 GMT 2022" Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: FSCK version Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: from "Linux version 5.10.103-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:24:00 GMT 2022" Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: to "Linux version 5.10.103-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:24:00 GMT 2022" Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: superblock features = 0 : Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000 Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: total FS sectors = 484655104 (236648 MB) Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: CKPT version = 5f118fe0 Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Info: checkpoint state = 41 : crc unmount Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] Unreachable nat entries [Ok..] [0x0] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] SIT valid block bitmap checking [Ok..] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] Hard link checking for regular file [Ok..] [0x7] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] valid_block_count matching with CP [Ok..] [0x3d9aee] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0xd834] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0xd834] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] valid_inode_count matched with CP [Ok..] [0xc9f4] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] free segment_count matched with CP [Ok..] [0x1adf4] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] next block offset is free [Ok..] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] fixing SIT types Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: [FSCK] other corrupted bugs [Ok..] Apr 10 13:31:15 Pi-Hole4 systemd-fsck[146]: Done. Apr 10 13:31:15 Pi-Hole4 systemd[1]: Started File System Check on Root Device. -- Subject: A start job for unit systemd-fsck-root.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsck-root.service has finished successfully. -- -- The job identifier is 20. Apr 10 13:31:15 Pi-Hole4 systemd[1]: Starting Remount Root and Kernel File Systems... -- Subject: A start job for unit systemd-remount-fs.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-remount-fs.service has begun execution. -- -- The job identifier is 21. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Started Remount Root and Kernel File Systems. -- Subject: A start job for unit systemd-remount-fs.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-remount-fs.service has finished successfully. -- -- The job identifier is 21. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Starting Load/Save Random Seed... -- Subject: A start job for unit systemd-random-seed.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-random-seed.service has begun execution. -- -- The job identifier is 44. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Activating swap /var/swap... -- Subject: A start job for unit var-swap.swap has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-swap.swap has begun execution. -- -- The job identifier is 24. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. -- Subject: A start job for unit systemd-hwdb-update.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-hwdb-update.service has finished successfully. -- -- The job identifier is 45. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Starting Create System Users... -- Subject: A start job for unit systemd-sysusers.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-sysusers.service has begun execution. -- -- The job identifier is 34. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Started Load/Save Random Seed. -- Subject: A start job for unit systemd-random-seed.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-random-seed.service has finished successfully. -- -- The job identifier is 44. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Activated swap /var/swap. -- Subject: A start job for unit var-swap.swap has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-swap.swap has finished successfully. -- -- The job identifier is 24. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Reached target Swap. -- Subject: A start job for unit swap.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit swap.target has finished successfully. -- -- The job identifier is 23. Apr 10 13:31:16 Pi-Hole4 kernel: Adding 60412k swap on /var/swap. Priority:-2 extents:5 across:76508k FS Apr 10 13:31:16 Pi-Hole4 systemd[1]: Started Create System Users. -- Subject: A start job for unit systemd-sysusers.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-sysusers.service has finished successfully. -- -- The job identifier is 34. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Starting Create Static Device Nodes in /dev... -- Subject: A start job for unit systemd-tmpfiles-setup-dev.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup-dev.service has begun execution. -- -- The job identifier is 26. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Started Create Static Device Nodes in /dev. -- Subject: A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully. -- -- The job identifier is 26. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Starting udev Kernel Device Manager... -- Subject: A start job for unit systemd-udevd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-udevd.service has begun execution. -- -- The job identifier is 41. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Reached target Local File Systems (Pre). -- Subject: A start job for unit local-fs-pre.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit local-fs-pre.target has finished successfully. -- -- The job identifier is 22. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Mounting /tmp... -- Subject: A start job for unit tmp.mount has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit tmp.mount has begun execution. -- -- The job identifier is 11. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Mounting /var/log... -- Subject: A start job for unit var-log.mount has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-log.mount has begun execution. -- -- The job identifier is 13. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Mounted /tmp. -- Subject: A start job for unit tmp.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit tmp.mount has finished successfully. -- -- The job identifier is 11. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Mounted /var/log. -- Subject: A start job for unit var-log.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-log.mount has finished successfully. -- -- The job identifier is 13. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Starting Flush Journal to Persistent Storage... -- Subject: A start job for unit systemd-journal-flush.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-journal-flush.service has begun execution. -- -- The job identifier is 48. Apr 10 13:31:16 Pi-Hole4 systemd-udevd[238]: Network interface NamePolicy= disabled on kernel command line, ignoring. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Started udev Kernel Device Manager. -- Subject: A start job for unit systemd-udevd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-udevd.service has finished successfully. -- -- The job identifier is 41. Apr 10 13:31:16 Pi-Hole4 systemd-journald[132]: Runtime journal (/run/log/journal/d958eb55ba6b44d7b033f9a3ddb9a4ed) is 8.0M, max 96.1M, 88.1M free. -- Subject: Disk space used by the journal -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Runtime journal (/run/log/journal/d958eb55ba6b44d7b033f9a3ddb9a4ed) is currently using 8.0M. -- Maximum allowed usage is set to 96.1M. -- Leaving at least 144.1M free (of currently available 953.0M of disk space). -- Enforced usage limit is thus 96.1M, of which 88.1M are still available. -- -- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Started Flush Journal to Persistent Storage. -- Subject: A start job for unit systemd-journal-flush.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-journal-flush.service has finished successfully. -- -- The job identifier is 48. Apr 10 13:31:16 Pi-Hole4 systemd[1]: Starting Create Volatile Files and Directories... -- Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup.service has begun execution. -- -- The job identifier is 33. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Started Create Volatile Files and Directories. -- Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup.service has finished successfully. -- -- The job identifier is 33. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Starting Network Time Synchronization... -- Subject: A start job for unit systemd-timesyncd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-timesyncd.service has begun execution. -- -- The job identifier is 51. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Starting Update UTMP about System Boot/Shutdown... -- Subject: A start job for unit systemd-update-utmp.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp.service has begun execution. -- -- The job identifier is 108. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Starting RPC bind portmap service... -- Subject: A start job for unit rpcbind.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpcbind.service has begun execution. -- -- The job identifier is 109. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Started Update UTMP about System Boot/Shutdown. -- Subject: A start job for unit systemd-update-utmp.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp.service has finished successfully. -- -- The job identifier is 108. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Starting Update UTMP about System Runlevel Changes... -- Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp-runlevel.service has begun execution. -- -- The job identifier is 107. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Started RPC bind portmap service. -- Subject: A start job for unit rpcbind.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpcbind.service has finished successfully. -- -- The job identifier is 109. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Reached target RPC Port Mapper. -- Subject: A start job for unit rpcbind.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpcbind.target has finished successfully. -- -- The job identifier is 110. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Reached target Remote File Systems (Pre). -- Subject: A start job for unit remote-fs-pre.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit remote-fs-pre.target has finished successfully. -- -- The job identifier is 72. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Reached target Remote File Systems. -- Subject: A start job for unit remote-fs.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit remote-fs.target has finished successfully. -- -- The job identifier is 96. Apr 10 13:31:17 Pi-Hole4 systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state. Apr 10 13:31:17 Pi-Hole4 kernel: rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000 Apr 10 13:31:17 Pi-Hole4 kernel: rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000 Apr 10 13:31:17 Pi-Hole4 kernel: rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000 Apr 10 13:31:17 Pi-Hole4 kernel: rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000 Apr 10 13:31:17 Pi-Hole4 systemd[1]: Started Update UTMP about System Runlevel Changes. -- Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp-runlevel.service has finished successfully. -- -- The job identifier is 107. Apr 10 13:31:17 Pi-Hole4 systemd-udevd[246]: Using default interface naming scheme 'v240'. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Started Network Time Synchronization. -- Subject: A start job for unit systemd-timesyncd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-timesyncd.service has finished successfully. -- -- The job identifier is 51. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Reached target System Time Synchronized. -- Subject: A start job for unit time-sync.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit time-sync.target has finished successfully. -- -- The job identifier is 52. Apr 10 13:31:17 Pi-Hole4 systemd[1]: Startup finished in 3.313s (kernel) + 2min 29.785s (userspace) = 2min 33.098s. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- All system services necessary queued for starting at boot have been -- started. Note that this does not mean that the machine is now idle as services -- might still be busy with completing start-up. -- -- Kernel start-up required 3313119 microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 149785639 microseconds. Apr 10 13:31:17 Pi-Hole4 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Apr 10 13:31:20 Pi-Hole4 systemd[1]: Condition check resulted in /sys/subsystem/net/devices/eth0 being skipped. -- Subject: A start job for unit sys-subsystem-net-devices-eth0.device has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit sys-subsystem-net-devices-eth0.device has finished successfully. -- -- The job identifier is 163. Apr 10 13:31:20 Pi-Hole4 systemd[1]: Starting ifup for eth0... -- Subject: A start job for unit ifup@eth0.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifup@eth0.service has begun execution. -- -- The job identifier is 160. Apr 10 13:31:20 Pi-Hole4 kernel: bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay) Apr 10 13:31:20 Pi-Hole4 kernel: bcmgenet fd580000.ethernet eth0: Link is Down Apr 10 13:31:21 Pi-Hole4 systemd[1]: Started ifup for eth0. -- Subject: A start job for unit ifup@eth0.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifup@eth0.service has finished successfully. -- -- The job identifier is 160. Apr 10 13:31:21 Pi-Hole4 systemd[1]: Reloading. Apr 10 13:31:23 Pi-Hole4 systemd[1]: emergency.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit emergency.service has successfully entered the 'dead' state. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Stopped Emergency Shell. -- Subject: A stop job for unit emergency.service has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit emergency.service has finished. -- -- The job identifier is 180 and the job result is done. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. -- Subject: A start job for unit systemd-binfmt.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-binfmt.service has finished successfully. -- -- The job identifier is 199. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Stopping File System Check Daemon to report status... -- Subject: A stop job for unit systemd-fsckd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit systemd-fsckd.service has begun execution. -- -- The job identifier is 282. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Started Forward Password Requests to Wall Directory Watch. -- Subject: A start job for unit systemd-ask-password-wall.path has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-ask-password-wall.path has finished successfully. -- -- The job identifier is 267. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Stopped target Emergency Mode. -- Subject: A stop job for unit emergency.target has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit emergency.target has finished. -- -- The job identifier is 181 and the job result is done. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Starting File System Check on /dev/disk/by-partuuid/6c586e13-01... -- Subject: A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service has begun execution. -- -- The job identifier is 213. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped. -- Subject: A start job for unit auth-rpcgss-module.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit auth-rpcgss-module.service has finished successfully. -- -- The job identifier is 261. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Condition check resulted in FUSE Control File System being skipped. -- Subject: A start job for unit sys-fs-fuse-connections.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit sys-fs-fuse-connections.mount has finished successfully. -- -- The job identifier is 210. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Started Dispatch Password Requests to Console Directory Watch. -- Subject: A start job for unit systemd-ask-password-console.path has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-ask-password-console.path has finished successfully. -- -- The job identifier is 179. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. -- Subject: A start job for unit systemd-hwdb-update.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-hwdb-update.service has finished successfully. -- -- The job identifier is 183. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Condition check resulted in Huge Pages File System being skipped. -- Subject: A start job for unit dev-hugepages.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dev-hugepages.mount has finished successfully. -- -- The job identifier is 190. Apr 10 13:31:23 Pi-Hole4 systemd[1]: systemd-fsckd.service: Main process exited, code=killed, status=15/TERM -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit systemd-fsckd.service has exited. -- -- The process' exit code is 'killed' and its exit status is 15. Apr 10 13:31:23 Pi-Hole4 systemd[1]: systemd-fsckd.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-fsckd.service has successfully entered the 'dead' state. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Stopped File System Check Daemon to report status. -- Subject: A stop job for unit systemd-fsckd.service has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit systemd-fsckd.service has finished. -- -- The job identifier is 282 and the job result is done. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Started File System Check Daemon to report status. -- Subject: A start job for unit systemd-fsckd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsckd.service has finished successfully. -- -- The job identifier is 283. Apr 10 13:31:23 Pi-Hole4 systemd-fsck[389]: fsck.fat 4.1 (2017-01-24) Apr 10 13:31:23 Pi-Hole4 systemd-fsck[389]: /dev/mmcblk0p1: 493 files, 127706/516190 clusters Apr 10 13:31:23 Pi-Hole4 systemd[1]: Started File System Check on /dev/disk/by-partuuid/6c586e13-01. -- Subject: A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-6c586e13\x2d01.service has finished successfully. -- -- The job identifier is 213. Apr 10 13:31:23 Pi-Hole4 systemd[1]: Mounting /boot... -- Subject: A start job for unit boot.mount has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit boot.mount has begun execution. -- -- The job identifier is 212. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Mounted /boot. -- Subject: A start job for unit boot.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit boot.mount has finished successfully. -- -- The job identifier is 212. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Reached target Local File Systems. -- Subject: A start job for unit local-fs.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit local-fs.target has finished successfully. -- -- The job identifier is 211. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 264. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. -- Subject: A start job for unit systemd-machine-id-commit.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-machine-id-commit.service has finished successfully. -- -- The job identifier is 195. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Reached target System Initialization. -- Subject: A start job for unit sysinit.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit sysinit.target has finished successfully. -- -- The job identifier is 168. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Daily Cleanup of Temporary Directories. -- Subject: A start job for unit systemd-tmpfiles-clean.timer has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-clean.timer has finished successfully. -- -- The job identifier is 234. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Listening on D-Bus System Message Bus Socket. -- Subject: A start job for unit dbus.socket has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dbus.socket has finished successfully. -- -- The job identifier is 237. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Clean PHP session files every 30 mins. -- Subject: A start job for unit phpsessionclean.timer has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit phpsessionclean.timer has finished successfully. -- -- The job identifier is 233. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Reached target Basic System. -- Subject: A start job for unit basic.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit basic.target has finished successfully. -- -- The job identifier is 167. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting OpenBSD Secure Shell server... -- Subject: A start job for unit ssh.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ssh.service has begun execution. -- -- The job identifier is 276. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)... -- Subject: A start job for unit raspi-config.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit raspi-config.service has begun execution. -- -- The job identifier is 278. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting LSB: DynDNS client... -- Subject: A start job for unit inadyn.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit inadyn.service has begun execution. -- -- The job identifier is 249. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting LSB: Network UPS Tools monitor initscript... -- Subject: A start job for unit nut-client.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nut-client.service has begun execution. -- -- The job identifier is 277. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Regular background program processing daemon. -- Subject: A start job for unit cron.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit cron.service has finished successfully. -- -- The job identifier is 266. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting Pi-hole FTL... -- Subject: A start job for unit pihole-FTL.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit pihole-FTL.service has begun execution. -- -- The job identifier is 280. Apr 10 13:31:24 Pi-Hole4 cron[402]: (CRON) INFO (pidfile fd = 3) Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting dhcpcd on all interfaces... -- Subject: A start job for unit dhcpcd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dhcpcd.service has begun execution. -- -- The job identifier is 254. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting Permit User Sessions... -- Subject: A start job for unit systemd-user-sessions.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-user-sessions.service has begun execution. -- -- The job identifier is 255. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped. -- Subject: A start job for unit rsync.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rsync.service has finished successfully. -- -- The job identifier is 245. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started D-Bus System Message Bus. -- Subject: A start job for unit dbus.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dbus.service has finished successfully. -- -- The job identifier is 279. Apr 10 13:31:24 Pi-Hole4 cron[402]: (CRON) INFO (Running @reboot jobs) Apr 10 13:31:24 Pi-Hole4 dhcpcd[408]: Not running dhcpcd because /etc/network/interfaces Apr 10 13:31:24 Pi-Hole4 dhcpcd[408]: defines some interfaces that will use a Apr 10 13:31:24 Pi-Hole4 dhcpcd[408]: DHCP client or static address Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting rng-tools.service... -- Subject: A start job for unit rng-tools.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rng-tools.service has begun execution. -- -- The job identifier is 274. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting Lighttpd Daemon... -- Subject: A start job for unit lighttpd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit lighttpd.service has begun execution. -- -- The job identifier is 270. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Synchronize Pi-hole instances. -- Subject: A start job for unit gravity-sync.timer has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit gravity-sync.timer has finished successfully. -- -- The job identifier is 231. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Synchronize Pi-hole instances. -- Subject: A start job for unit gravity-sync.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit gravity-sync.service has finished successfully. -- -- The job identifier is 232. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting DietPi-RAMlog... -- Subject: A start job for unit dietpi-ramlog.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-ramlog.service has begun execution. -- -- The job identifier is 275. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting Check for Raspberry Pi EEPROM updates... -- Subject: A start job for unit rpi-eeprom-update.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpi-eeprom-update.service has begun execution. -- -- The job identifier is 256. Apr 10 13:31:24 Pi-Hole4 systemd[1]: nfs-config.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit nfs-config.service has successfully entered the 'dead' state. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Preprocess NFS configuration. -- Subject: A start job for unit nfs-config.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nfs-config.service has finished successfully. -- -- The job identifier is 264. Apr 10 13:31:24 Pi-Hole4 systemd[1]: dhcpcd.service: Control process exited, code=exited, status=6/NOTCONFIGURED -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit dhcpcd.service has exited. -- -- The process' exit code is 'exited' and its exit status is 6. Apr 10 13:31:24 Pi-Hole4 systemd[1]: dhcpcd.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit dhcpcd.service has entered the 'failed' state with result 'exit-code'. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Failed to start dhcpcd on all interfaces. -- Subject: A start job for unit dhcpcd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dhcpcd.service has finished with a failure. -- -- The job identifier is 254 and the job result is failed. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Permit User Sessions. -- Subject: A start job for unit systemd-user-sessions.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-user-sessions.service has finished successfully. -- -- The job identifier is 255. Apr 10 13:31:24 Pi-Hole4 rngd[427]: rngd 2-unofficial-mt.14 starting up... Apr 10 13:31:24 Pi-Hole4 rng-tools[415]: Starting Hardware RNG entropy gatherer daemon: rngd. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started rng-tools.service. -- Subject: A start job for unit rng-tools.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rng-tools.service has finished successfully. -- -- The job identifier is 274. Apr 10 13:31:24 Pi-Hole4 rngd[427]: entropy feed to the kernel ready Apr 10 13:31:24 Pi-Hole4 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off Apr 10 13:31:24 Pi-Hole4 raspi-config[398]: Checking if shift key is held down: No. Switching to ondemand scaling governor. Apr 10 13:31:24 Pi-Hole4 CRON[413]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 10 13:31:24 Pi-Hole4 CRON[412]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 10 13:31:24 Pi-Hole4 inadyn[399]: inadyn: Not starting. Disabled in /etc/default/inadyn. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed). -- Subject: A start job for unit raspi-config.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit raspi-config.service has finished successfully. -- -- The job identifier is 278. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started LSB: DynDNS client. -- Subject: A start job for unit inadyn.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit inadyn.service has finished successfully. -- -- The job identifier is 249. Apr 10 13:31:24 Pi-Hole4 CRON[443]: (root) CMD (/usr/sbin/logrotate --state /var/lib/logrotate/pihole /etc/pihole/logrotate) Apr 10 13:31:24 Pi-Hole4 CRON[444]: (root) CMD ( PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker reboot) Apr 10 13:31:24 Pi-Hole4 gravity-sync[418]: ∞ Initializing Gravity Sync (4.0.4) Apr 10 13:31:24 Pi-Hole4 CRON[413]: (CRON) info (No MTA installed, discarding output) Apr 10 13:31:24 Pi-Hole4 CRON[413]: pam_unix(cron:session): session closed for user root Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started Getty on tty1. -- Subject: A start job for unit getty@tty1.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit getty@tty1.service has finished successfully. -- -- The job identifier is 241. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped. -- Subject: A start job for unit rpc-gssd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpc-gssd.service has finished successfully. -- -- The job identifier is 265. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped. -- Subject: A start job for unit rpc-svcgssd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpc-svcgssd.service has finished successfully. -- -- The job identifier is 262. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started LSB: Network UPS Tools monitor initscript. -- Subject: A start job for unit nut-client.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nut-client.service has finished successfully. -- -- The job identifier is 277. Apr 10 13:31:24 Pi-Hole4 gravity-sync[418]: [59B blob data] Apr 10 13:31:24 Pi-Hole4 gravity-sync[418]: [81B blob data] Apr 10 13:31:24 Pi-Hole4 systemd[1]: Started DietPi-RAMlog. -- Subject: A start job for unit dietpi-ramlog.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-ramlog.service has finished successfully. -- -- The job identifier is 275. Apr 10 13:31:24 Pi-Hole4 systemd[1]: Starting DietPi-PreBoot... -- Subject: A start job for unit dietpi-preboot.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-preboot.service has begun execution. -- -- The job identifier is 272. Apr 10 13:31:25 Pi-Hole4 sshd[455]: Server listening on 0.0.0.0 port 22. Apr 10 13:31:25 Pi-Hole4 sshd[455]: Server listening on :: port 22. Apr 10 13:31:25 Pi-Hole4 systemd[1]: Started Pi-hole FTL. -- Subject: A start job for unit pihole-FTL.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit pihole-FTL.service has finished successfully. -- -- The job identifier is 280. Apr 10 13:31:25 Pi-Hole4 systemd[1]: Started OpenBSD Secure Shell server. -- Subject: A start job for unit ssh.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ssh.service has finished successfully. -- -- The job identifier is 276. Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] Using log file /var/log/pihole/FTL.log Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] ########## FTL started on Pi-Hole4! ########## Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] FTL branch: master Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] FTL version: v5.22 Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] FTL commit: eb197891 Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] FTL date: 2023-03-22 21:21:35 +0000 Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] FTL user: pihole Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] Compiled for armv7hf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0 Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] Starting config file parsing (/etc/pihole/pihole-FTL.conf) Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] SOCKET_LISTENING: only local Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] AAAA_QUERY_ANALYSIS: Show AAAA queries Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] MAXDBDAYS: max age for stored queries is 365 days Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] RESOLVE_IPV6: Resolve IPv6 addresses Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] RESOLVE_IPV4: Resolve IPv4 addresses Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] DBINTERVAL: saving to DB file every minute Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] DBFILE: Using /etc/pihole/pihole-FTL.db Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] MAXLOGAGE: Importing up to 24.0 hours of log data Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] PRIVACYLEVEL: Set to 0 Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] IGNORE_LOCALHOST: Show queries from localhost Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] BLOCKINGMODE: Null IPs for blocked domains Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] DBIMPORT: Importing history from database Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.461 459M] PIDFILE: Using /run/pihole-FTL.pid Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] SOCKETFILE: Using /run/pihole/FTL.sock Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] MACVENDORDB: Using /etc/pihole/macvendor.db Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] GRAVITYDB: Using /etc/pihole/gravity.db Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] PARSE_ARP_CACHE: Active Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] CNAME_DEEP_INSPECT: Active Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] DELAY_STARTUP: No delay requested. Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain} Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] NICE: Set process niceness to -10 (default) Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] MAXNETAGE: Removing IP addresses and host names from network table after 365 days Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] NAMES_FROM_NETDB: Enabled, trying to get names from network database Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] EDNS0_ECS: Overwrite client from ECS information Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] REFRESH_HOSTNAMES: Periodically refreshing IPv4 names Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] RATE_LIMIT: Rate-limiting client making more than 1000 queries in 60 seconds Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] LOCAL_IPV4: Automatic interface-dependent detection of address Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] LOCAL_IPV6: Automatic interface-dependent detection of address Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] BLOCK_IPV4: Automatic interface-dependent detection of address Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] BLOCK_IPV6: Automatic interface-dependent detection of address Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] SHOW_DNSSEC: Enabled, showing automatically generated DNSSEC queries Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] MOZILLA_CANARY: Enabled Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] PIHOLE_PTR: internal PTR generation enabled (pi.hole) Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] ADDR2LINE: Enabled Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.462 459M] REPLY_WHEN_BUSY: Drop queries when the database is busy Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M] BLOCK_TTL: 2 seconds Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M] BLOCK_ICLOUD_PR: Enabled Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M] CHECK_LOAD: Enabled Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M] CHECK_SHMEM: Warning if shared-memory usage exceeds 90% Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M] CHECK_DISK: Warning if certain disk usage exceeds 90% Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M] Finished config file parsing Apr 10 13:31:25 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M] Creating mutex Apr 10 13:31:25 Pi-Hole4 DietPi-PreBoot[457]: DietPi-CPU_set Apr 10 13:31:25 Pi-Hole4 DietPi-PreBoot[457]: ───────────────────────────────────────────────────── Apr 10 13:31:25 Pi-Hole4 DietPi-PreBoot[457]: Mode: Applying CPU governor settings: ondemand Apr 10 13:31:25 Pi-Hole4 DietPi-PreBoot[457]: [ INFO ] DietPi-CPU_set | Setting up_threshold: 85 % Apr 10 13:31:25 Pi-Hole4 DietPi-PreBoot[457]: [ INFO ] DietPi-CPU_set | Setting sampling_rate: 25000 microseconds Apr 10 13:31:25 Pi-Hole4 DietPi-PreBoot[457]: [ INFO ] DietPi-CPU_set | Setting sampling_down_factor: 40 x Apr 10 13:31:25 Pi-Hole4 DietPi-PreBoot[457]: [ OK ] DietPi-CPU_set | Applied CPU governor settings: ondemand Apr 10 13:31:25 Pi-Hole4 systemd[1]: Started DietPi-PreBoot. -- Subject: A start job for unit dietpi-preboot.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-preboot.service has finished successfully. -- -- The job identifier is 272. Apr 10 13:31:25 Pi-Hole4 systemd[1]: Started DietPi-PostBoot. -- Subject: A start job for unit dietpi-postboot.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-postboot.service has finished successfully. -- -- The job identifier is 257. Apr 10 13:31:26 Pi-Hole4 systemd[1]: Started Lighttpd Daemon. -- Subject: A start job for unit lighttpd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit lighttpd.service has finished successfully. -- -- The job identifier is 270. Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: BOOTLOADER: up to date Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: CURRENT: Wed 11 Jan 17:40:52 UTC 2023 (1673458852) Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: LATEST: Wed 11 Jan 17:40:52 UTC 2023 (1673458852) Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable) Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: Use raspi-config to change the release. Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: VL805_FW: Dedicated VL805 EEPROM Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: VL805: up to date Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: CURRENT: 000138c0 Apr 10 13:31:26 Pi-Hole4 rpi-eeprom-update[421]: LATEST: 000138c0 Apr 10 13:31:26 Pi-Hole4 systemd[1]: Started Check for Raspberry Pi EEPROM updates. -- Subject: A start job for unit rpi-eeprom-update.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rpi-eeprom-update.service has finished successfully. -- -- The job identifier is 256. Apr 10 13:31:26 Pi-Hole4 systemd[1]: Reached target Multi-User System. -- Subject: A start job for unit multi-user.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit multi-user.target has finished successfully. -- -- The job identifier is 166. Apr 10 13:31:26 Pi-Hole4 systemd[1]: Reached target Graphical Interface. -- Subject: A start job for unit graphical.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit graphical.target has finished successfully. -- -- The job identifier is 165. Apr 10 13:31:26 Pi-Hole4 systemd[1]: Starting Update UTMP about System Runlevel Changes... -- Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp-runlevel.service has begun execution. -- -- The job identifier is 268. Apr 10 13:31:26 Pi-Hole4 systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state. Apr 10 13:31:26 Pi-Hole4 systemd[1]: Started Update UTMP about System Runlevel Changes. -- Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp-runlevel.service has finished successfully. -- -- The job identifier is 268. Apr 10 13:31:26 Pi-Hole4 login[446]: pam_unix(login:session): session opened for user root by LOGIN(uid=0) Apr 10 13:31:26 Pi-Hole4 login[551]: ROOT LOGIN on '/dev/tty1' Apr 10 13:31:28 Pi-Hole4 gravity-sync[418]: ∞ Detecting remote Pi-hole installationssh: connect to host 192.168.3.3 port 22: No route to host Apr 10 13:31:28 Pi-Hole4 pihole-FTL[459]: [2023-04-10 13:31:25.463 459M Apr 10 13:31:34 Pi-Hole4 gravity-sync[418]: [42B blob data] Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: ∞ Checking on peerssh: connect to host 192.168.3.3 port 22: No route to host Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: [47B blob data] Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: ! Please configure Gravity Sync on remote host Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: [56B blob data] Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: » Remote target root@192.168.3.3 Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: [69B blob data] Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: [69B blob data] Apr 10 13:31:37 Pi-Hole4 gravity-sync[418]: » Starting SMART Analysis Apr 10 13:31:40 Pi-Hole4 gravity-sync[418]: ∞ Hashing the remote Gravity Databasessh: connect to host 192.168.3.3 port 22: No route to host Apr 10 13:31:40 Pi-Hole4 gravity-sync[418]: [40B blob data] Apr 10 13:31:41 Pi-Hole4 gravity-sync[418]: [87B blob data] Apr 10 13:31:41 Pi-Hole4 gravity-sync[418]: ! Differences detected in the Gravity Database Apr 10 13:31:43 Pi-Hole4 gravity-sync[418]: ssh: connect to host 192.168.3.3 port 22: No route to host Apr 10 13:31:43 Pi-Hole4 gravity-sync[418]: ! DNS Records not detected on the remote Pi-hole Apr 10 13:31:46 Pi-Hole4 gravity-sync[418]: ssh: connect to host 192.168.3.3 port 22: No route to host Apr 10 13:31:46 Pi-Hole4 gravity-sync[418]: ! DNS CNAMEs not detected on the local Pi-hole Apr 10 13:31:50 Pi-Hole4 gravity-sync[418]: ssh: connect to host 192.168.3.3 port 22: No route to host Apr 10 13:31:50 Pi-Hole4 gravity-sync[418]: ! Static DHCP Addresses not detected on the local Pi-hole Apr 10 13:31:50 Pi-Hole4 gravity-sync[418]: ! Replication of Pi-hole settings is required Apr 10 13:31:50 Pi-Hole4 sudo[640]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/pihole-FTL sql /etc/pihole/gravity.db .backup '/etc/pihole/gravity.db.gsb' Apr 10 13:31:50 Pi-Hole4 sudo[640]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 10 13:31:53 Pi-Hole4 systemd[1]: systemd-fsckd.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-fsckd.service has successfully entered the 'dead' state. Apr 10 13:32:12 Pi-Hole4 systemd-timesyncd[257]: Synchronized to time server for the first time 204.17.205.8:123 (2.north-america.pool.ntp.org). Apr 10 13:32:43 Pi-Hole4 sudo[640]: pam_unix(sudo:session): session closed for user root Apr 10 13:32:43 Pi-Hole4 gravity-sync[418]: [95B blob data] Apr 10 13:32:44 Pi-Hole4 CRON[412]: pam_unix(cron:session): session closed for user root Apr 10 13:32:48 Pi-Hole4 gravity-sync[418]: [155B blob data] Apr 10 13:32:48 Pi-Hole4 gravity-sync[418]: ∞ Removing failed copies Gravity Databaserm: cannot remove '/etc/pihole/gravity.db.gsb': No such file or directory Apr 10 13:32:48 Pi-Hole4 gravity-sync[418]: [44B blob data] Apr 10 13:32:48 Pi-Hole4 systemd[1]: gravity-sync.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit gravity-sync.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Apr 10 13:32:48 Pi-Hole4 systemd[1]: gravity-sync.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit gravity-sync.service has entered the 'failed' state with result 'exit-code'. Apr 10 13:34:13 Pi-Hole4 sshd[924]: Accepted publickey for root from 192.168.3.3 port 36212 ssh2: RSA SHA256:z4OWcgsvu6Z6bYoC3NrdxlnfzD9EHa2vL5XkK3nOmOs Apr 10 13:34:13 Pi-Hole4 sshd[924]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 10 13:34:14 Pi-Hole4 sshd[924]: Received disconnect from 192.168.3.3 port 36212:11: disconnected by user Apr 10 13:34:14 Pi-Hole4 sshd[924]: Disconnected from user root 192.168.3.3 port 36212 Apr 10 13:34:14 Pi-Hole4 sshd[924]: pam_unix(sshd:session): session closed for user root Apr 10 13:34:14 Pi-Hole4 sshd[931]: Accepted publickey for root from 192.168.3.3 port 36216 ssh2: RSA SHA256:z4OWcgsvu6Z6bYoC3NrdxlnfzD9EHa2vL5XkK3nOmOs Apr 10 13:34:14 Pi-Hole4 sshd[931]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 10 13:34:14 Pi-Hole4 sshd[931]: Received disconnect from 192.168.3.3 port 36216:11: disconnected by user Apr 10 13:34:14 Pi-Hole4 sshd[931]: Disconnected from user root 192.168.3.3 port 36216 Apr 10 13:34:14 Pi-Hole4 sshd[931]: pam_unix(sshd:session): session closed for user root Apr 10 13:34:14 Pi-Hole4 sshd[938]: Accepted publickey for root from 192.168.3.3 port 36218 ssh2: RSA SHA256:z4OWcgsvu6Z6bYoC3NrdxlnfzD9EHa2vL5XkK3nOmOs Apr 10 13:34:14 Pi-Hole4 sshd[938]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 10 13:34:14 Pi-Hole4 sshd[938]: Received disconnect from 192.168.3.3 port 36218:11: disconnected by user Apr 10 13:34:14 Pi-Hole4 sshd[938]: Disconnected from user root 192.168.3.3 port 36218 Apr 10 13:34:14 Pi-Hole4 sshd[938]: pam_unix(sshd:session): session closed for user root Apr 10 13:34:15 Pi-Hole4 sshd[945]: Accepted publickey for root from 192.168.3.3 port 36224 ssh2: RSA SHA256:z4OWcgsvu6Z6bYoC3NrdxlnfzD9EHa2vL5XkK3nOmOs Apr 10 13:34:15 Pi-Hole4 sshd[945]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 10 13:34:15 Pi-Hole4 sshd[945]: Received disconnect from 192.168.3.3 port 36224:11: disconnected by user Apr 10 13:34:15 Pi-Hole4 sshd[945]: Disconnected from user root 192.168.3.3 port 36224 Apr 10 13:34:15 Pi-Hole4 sshd[945]: pam_unix(sshd:session): session closed for user root Apr 10 13:34:15 Pi-Hole4 sshd[952]: Accepted publickey for root from 192.168.3.3 port 36240 ssh2: RSA SHA256:z4OWcgsvu6Z6bYoC3NrdxlnfzD9EHa2vL5XkK3nOmOs Apr 10 13:34:15 Pi-Hole4 sshd[952]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 10 13:34:15 Pi-Hole4 sshd[952]: Received disconnect from 192.168.3.3 port 36240:11: disconnected by user Apr 10 13:34:15 Pi-Hole4 sshd[952]: Disconnected from user root 192.168.3.3 port 36240 Apr 10 13:34:15 Pi-Hole4 sshd[952]: pam_unix(sshd:session): session closed for user root Apr 10 13:34:15 Pi-Hole4 sshd[961]: Accepted publickey for root from 192.168.3.3 port 36252 ssh2: RSA SHA256:z4OWcgsvu6Z6bYoC3NrdxlnfzD9EHa2vL5XkK3nOmOs Apr 10 13:34:15 Pi-Hole4 sshd[961]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 10 13:34:15 Pi-Hole4 sshd[961]: Received disconnect from 192.168.3.3 port 36252:11: disconnected by user Apr 10 13:34:15 Pi-Hole4 sshd[961]: Disconnected from user root 192.168.3.3 port 36252 Apr 10 13:34:15 Pi-Hole4 sshd[961]: pam_unix(sshd:session): session closed for user root Apr 10 13:34:16 Pi-Hole4 sshd[968]: Accepted publickey for root from 192.168.3.3 port 36258 ssh2: RSA SHA256:z4OWcgsvu6Z6bYoC3NrdxlnfzD9EHa2vL5XkK3nOmOs Apr 10 13:34:16 Pi-Hole4 sshd[968]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 10 13:34:16 Pi-Hole4 sshd[968]: Received disconnect from 192.168.3.3 port 36258:11: disconnected by user Apr 10 13:34:16 Pi-Hole4 sshd[968]: Disconnected from user root 192.168.3.3 port 36258 Apr 10 13:34:16 Pi-Hole4 sshd[968]: pam_unix(sshd:session): session closed for user root Apr 10 13:39:01 Pi-Hole4 CRON[999]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 10 13:39:01 Pi-Hole4 CRON[1000]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) Apr 10 13:39:01 Pi-Hole4 CRON[999]: pam_unix(cron:session): session closed for user root Apr 10 13:39:44 Pi-Hole4 systemd[1]: Starting Clean php session files... -- Subject: A start job for unit phpsessionclean.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit phpsessionclean.service has begun execution. -- -- The job identifier is 303. Apr 10 13:39:45 Pi-Hole4 systemd[1]: phpsessionclean.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit phpsessionclean.service has successfully entered the 'dead' state. Apr 10 13:39:45 Pi-Hole4 systemd[1]: Started Clean php session files. -- Subject: A start job for unit phpsessionclean.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit phpsessionclean.service has finished successfully. -- -- The job identifier is 303. Apr 10 13:41:30 Pi-Hole4 sshd[1055]: Accepted password for root from 192.168.3.59 port 57733 ssh2 Apr 10 13:41:30 Pi-Hole4 sshd[1055]: pam_unix(sshd:session): session opened for user root by (uid=0)