Issue with Pi-hole -up

General Beta 6.0
1

Hi All,

I have just done an update on pi-hole, and it seems it came back with a couple of issues, it would seem.

@raspberrypi:~ $ sudo pihole -v
Core
    Version is v5.18.3-457-ga8d305d5 (Latest: null)
    Branch is development-v6
    Hash is a8d305d5 (Latest: a8d305d5)
Web
    Version is v5.21-929-g085c2880 (Latest: null)
    Branch is development-v6
    Hash is 085c2880 (Latest: N/A)
FTL
    Version is vDev-e5a24bd (Latest: null)
    Branch is development-v6
    Hash is e5a24bdd (Latest: N/A)
  1. Issue
  [✓] Deleting existing list cache
  [✗] DNS service is not running
  [i] Restarting DNS server...==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to restart 'pihole-FTL.service'.
Authenticating as: ,,, (xxxxxxx)
Password: xxxxxxxxxxx: pam_authenticate failed: Authentication failure
  [✗] Failed to restart pihole-FTL.service: Connection timed out
See system logs and 'systemctl status pihole-FTL.service' for details.
  [✓] DNS resolution is now available
  1. Issue
  [✓] Swapping databases
  [✓] The old database remains available
  [✓] Cleaning up stray matter

  [✓] Done.
fatal: unable to access 'https://github.com/pi-hole/web/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/pi-hole/FTL/': Could not resolve host: github.com

  [i] The install log is located at: /etc/pihole/install.log
  [✓] Update complete!

https://tricorder.pi-hole.net/8fmhFc4D/

Any solution please.

Cheers.

2

Two things here.

  1. Please try to run a pihole checkout dev
    As noted in our latest blog post, the development-v6 branches are now discontinued and merged into the "regular" development cycle.

  2. Please explain what the commas and xxx are in the following:

    as it is currently unclear to me what might be part of the error and what you have obscured to protect some private information. Don't get me wrong here: the latter is of course perfectly fine, I would just need to know which part of the quote is accurate and which has been manipulated.

3

Problem resolved, the problem laid with the DD-WRT router after a firmware update, which caused a cascading effect.