secureboot: Secure boot could not be determined (mode 0) x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. x86/fpu: xstate_offset: 576, xstate_sizes: 256 x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' T19:18:40+10:00 systemd: : Start request repeated too quickly.
T19:18:40+10:00 systemd: Stopped Service for snap application adguard-home.adguard-home.
T19:18:40+10:00 systemd: : Scheduled restart job, restart counter is at 10.
T19:18:39+10:00 systemd: : Main process exited, code=exited, status=1/FAILURE T19:18:39+10:00 adguard-home.adguard-home: 7 19:18:39.695214 couldn't start forwarding DNS server: listening to udp socket: listen udp 192.168.0.2:53: bind: cannot assign requested address
This is the error log prior to restarting the snap instance. I generally resolve this by utilising SSH and manually restart the AdGuard Home snap service to get it running again. I need some help, when we have a power outage & the power is restored AdGuard Home doesn’t seem to load correctly after boot.
0 kommentar(er)
