These are abnormal in your debug log, and at the time the debug log was generated indicate a connectivity problem:
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the ens160 interface.
[✗] No IPv6 address(es) found on the ens160 interface.
[i] Default IPv4 gateway: 10.191.100.2
- Pinging 10.191.100.2...
[✗] Gateway did not respond. (Why is a default gateway important for Pi-hole?)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] metrics.oregonlive.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve metrics.oregonlive.com via Pi-hole (10.191.100.142)
The 24 hour history of DNS queries shows quite a bit of activity.
[2020-05-28 12:12:22.319 14491] Imported 498203 queries from the long-term database
[2020-05-28 12:12:22.319 14491] -> Total DNS queries: 498203
[2020-05-28 12:12:22.319 14491] -> Cached DNS queries: 486642
[2020-05-28 12:12:22.319 14491] -> Forwarded DNS queries: 10348
[2020-05-28 12:12:22.319 14491] -> Blocked DNS queries: 1193
[2020-05-28 12:12:22.319 14491] -> Unknown DNS queries: 20
[2020-05-28 12:12:22.319 14491] -> Unique domains: 371
[2020-05-28 12:12:22.319 14491] -> Unique clients: 26
[2020-05-28 12:12:22.319 14491] -> Known forward destinations: 4
Check in the following logs for any errors:
/var/log/pihole.log
/var/log/pihole.log.1
/var/log/pihole-FTL.log
/var/log/pihole-FTL.log.1
/var/log/syslog