Not able to update to release 4.0

v4-0
#1

Hi I’m running pi-hole on a rasperry pi.

i tried to update to the newest version with pihole -up. this failed.

pi@raspberrypi:~ $ pihole -up
[i] Checking for updates…
fatal: unable to access ‘https://github.com/pi-hole/pi-hole/’: Could not resolve host: github.com
fatal: HEAD does not point to a branch

Error: Remote revision could not be obtained, please contact Pi-hole Support
Additional debugging output:
HEAD detached at v3.2.1
nothing to commit, working directory clean
pi@raspberrypi:~ $

I was shure that the current version was 3.3 but when i check version it tells me that the version is 3.2.1

pi@raspberrypi:~ $ pihole version
Pi-hole version is v3.2.1 (Latest: ERROR)
AdminLTE version is v3.2.1 (Latest: ERROR)
FTL version is v3.0 (Latest: ERROR)

By the way pihole -d is getting me this error:

[?] Would you like to upload the log? [y/N] y
* Using openssl for transmission.
[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.

How can I fix this?
Regards,
Chris

Output of pihole -d

pi@raspberrypi:~ $ cat /var/log/pihole_debug-sanitized.log
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2018-08-21:16:20:00 debug log has been initiated.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf…

*** [ DIAGNOSING ]: Core version
[i] Core: v3.2.1 (How do I update Pi-hole?)
[i] Branch: HEAD (The pihole Command With Examples)
[i] Commit: v3.2.1-0-ge602008

*** [ DIAGNOSING ]: Web version
[i] Web: v3.2.1 (How do I update Pi-hole?)
[i] Branch: HEAD (The pihole Command With Examples)
[i] Commit: v3.2.1-0-g31dddd8

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0 (How do I update Pi-hole?)

*** [ DIAGNOSING ]: dnsmasq version
[i] 2.76

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.35

*** [ DIAGNOSING ]: php version
[i] 5.6.30

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 8 (jessie)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.165.10.15/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
2a02:1205:5005:2770:2ad8:169b:1315:2cf9 matches the IP found in /etc/pihole/setupVars.conf
fe80::3162:9baa:3988:e8a4 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.165.10.1

  • Pinging 192.165.10.1…
    [✓] Gateway responded.
    [i] Default IPv6 gateway: fe80::226:42ff:fea6:67b0
  • Pinging fe80::226:42ff:fea6:67b0…
    [✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[] is in use by
[22] is in use by sshd
[4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve mercadoiqoption.com via localhost (127.0.0.1)
[✗] Failed to resolve mercadoiqoption.com via Pi-hole (192.165.10.15)
[✓] doubleclick.com is 172.217.168.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve statistics.theonion.com via localhost (::1)
[✗] Failed to resolve statistics.theonion.com via Pi-hole (2a02:1205:5005:2770:2ad8:169b:1315:2cf9)
[✓] doubleclick.com is 2a00:1450:400a:802::200e via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is failed
[✗] lighttpd daemon is inactive
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.165.10.15/24
IPV6_ADDRESS=2a02:1205:5005:2770:2ad8:169b:1315:2cf9
PIHOLE_DNS_1=195.186.1.111
PIHOLE_DNS_2=
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1

*** [ DIAGNOSING ]: Dashboard and block page
[✗] X-Header does not match or could not be retrieved.

[✗] X-Header does not match or could not be retrieved.

*** [ DIAGNOSING ]: Gravity list
-rw-r–r-- 1 root root 15565878 Aug 19 03:58 /etc/pihole/gravity.list
-----head of gravity.list------
192.165.10.15 0.0.0.0
2a02:120b:2c09:7540:9689:bc6e:7ace:97c1 0.0.0.0
192.165.10.15 0.r.msn.com
2a02:120b:2c09:7540:9689:bc6e:7ace:97c1 0.r.msn.com

-----tail of gravity.list------
192.165.10.15 zzzrtrcm2.com
2a02:120b:2c09:7540:9689:bc6e:7ace:97c1 zzzrtrcm2.com
192.165.10.15 zzzzz4.52896368.com
2a02:120b:2c09:7540:9689:bc6e:7ace:97c1 zzzzz4.52896368.com

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r–r-- 1 root root 1047 Mar 31 15:12 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt
https://raw.githubusercontent.com/crazy-max/WindowsSpyBlocker/master/data/hosts/win10/spy.txt
https://raw.githubusercontent.com/quidsup/notrack/master/trackers.txt
https://raw.githubusercontent.com/notracking/hosts-blocklists/master/hostnames.txt
https://raw.githubusercontent.com/notracking/hosts-blocklists/master/domains.txt

-rw-r–r-- 1 root root 2667 Jun 11 20:13 /etc/pihole/blacklist.txt
scontent-frt3-1.xx.fbcdn.net
www.andyetanotherthing.com
ioam.de
safebrowsing.google.com
mazkvgok.home
safebrowsing-cache.google.com
alt1-safebrowsing.google.com
v10.vortex-win.data.microsoft.com
689739acd0a6a66ed9e631cd49992e50c3e6f9ba.2.damoh.chip.de
b67d34b6f9d140d7974126dd22320bf067e176c2.2.damoh.chip.de
74ddb8d0b208ec005a79946f252710dc1105eb66.2.damoh.chip.de
54c13f1b69dc53bbae635d48c1af27d31d249ae5.2.damoh.chip.de
664932c1867cbb6e36ad257602ab81df98c4e525.2.damoh.chip.de
01ede4538b1563cea451ef8504f9213f9253d90d.1.damoh.chip.de
b8c749a108329842ea214690be8e74c8204e5922.1.damoh.chip.de
8db186bd15a1ae326d206f93d8a665f0c57990ec.1.damoh.chip.de
6322901f8d5c9d1b37bff38186bb66c4366734fc.1.damoh.chip.de
compatexchange.cloudapp.net
a-0001.a-msedge.net
choice.microsoft.com
choice.microsoft.com.nsatc.net
corpext.msitadfs.glbdns2.microsoft.com
df.telemetry.microsoft.com
oca.telemetry.microsoft.com
oca.telemetry.microsoft.com.nsatc.net
redir.metaservices.microsoft.com
reports.wes.df.telemetry.microsoft.com
services.wes.df.telemetry.microsoft.com
settings-sandbox.data.microsoft.com
sls.update.microsoft.com.akadns.net
sqm.df.telemetry.microsoft.com
sqm.telemetry.microsoft.com
sqm.telemetry.microsoft.com.nsatc.net
statsfe2.ws.microsoft.com
telecommand.telemetry.microsoft.com
telemetry.appex.bing.net
telemetry.microsoft.com
telemetry.urs.microsoft.com
vortex-sandbox.data.microsoft.com
vortex-win.data.microsoft.com
vortex.data.microsoft.com
watson.ppe.telemetry.microsoft.com
ssw.live.com
pre.footprintpredict.com
i1.services.social.microsoft.com.nsatc.net
i1.services.social.microsoft.com
cs1.wpc.v0cdn.net
statsfe1.ws.microsoft.com
survey.watson.microsoft.com
feedback.search.microsoft.com
feedback.windows.com
diagnostics.support.microsoft.com
corp.sts.microsoft.com
watson.microsoft.com
watson.live.com
c.urs.microsoft.com
px.wa.ui-portal.de
pubads.g.doubleclick.net
api-global.netflix.com
connect.facebook.net
www.google.de
geo3.ggpht.com
array401-prod.do.dsp.mp.microsoft.com
iecvlist.microsoft.com
t.urs.microsoft.com
urs.microsoft.com
blob.weather.microsoft.com
gfcajuzjmvm.home
sybblohlexnjbat.home
npbnbfvm.home
1.voxde.damoh.schneevonmorgen.com
94a6e351ebc689b20a468d61d1d8bc8542576570.2.damoh.vox.de
homad-global-configs.schneevonmorgen.com.s3.amazonaws.com
camgasm.com
r16—sn-p5qlsn7l.googlevideo.com
watson.telemetry.microsoft.com
cd.microsoft.com
win10.ipv6.microsoft.com
putlowna.de
logger.navigator.gmx.net
trackbar.navigator.gmx.net
www.google-analytics.com
brwd80f993b9b72.home
playrix.helpshift.com
rms.bluewin.ch
www.googleapis.com
r3—sn-nfpnnjvh-1gid.googlevideo.com
r5—sn-q4flrn7k.googlevideo.com
settings-win.data.microsoft.com

-rw-r–r-- 1 root root 148 Aug 19 03:58 /etc/pihole/local.list
192.165.10.15 raspberrypi
2a02:120b:2c09:7540:9689:bc6e:7ace:97c1 raspberrypi
192.165.10.15 pi.hole
2a02:120b:2c09:7540:9689:bc6e:7ace:97c1 pi.hole

-rw-r–r-- 1 root root 234 Aug 21 16:09 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}

-rw-r–r-- 1 root root 1194 Aug 9 10:23 /etc/pihole/whitelist.txt
raw.githubusercontent.com
mirror1.malwaredomains.com
sysctl.org
s3.amazonaws.com
hosts-file.net
de-ipd.cdn.videoplaza.tv
dsp.adfarm1.adition.com
track.adform.net
ip.nuggad.net
js.revsci.net
cdn.adrtx.net
xpl.theadex.com
fe2.update.microsoft.com
android.clients.google.com
clients4.google.com
isatap.home
ssl.google-analytics.com
secure-eu.imrworldwide.com
dc.services.visualstudio.com
www.gstatic.com
wpad.home
www.googleadservices.com
cdn-gl.imrworldwide.com
cdn.optimizely.com
ad.sxp.smartclip.net
cm.g.doubleclick.net
api.adrtx.net
pix04.revsci.net
dmp.theadex.com
script.ioam.de
pixel.advertising.com
sync.adap.tv
googleads.g.doubleclick.net
zeustracker.abuse.ch
d393t6hijygk98.cloudfront.net
go.microsoft.com
dns.msftncsi.com
csi.gstatic.com
navigator.gmx.net
api.github.com
www.facebook.com
api.mobula.sdk.duapps.com
t.appsflyer.com
api.crittercism.com
config.ioam.de
impact.applifier.com
rts.mobula.sdk.duapps.com
appload.ingest.crittercism.com
udm.scorecardresearch.com
portal.fb.com
cdn-highwinds.unityads.unity3d.com
px1.vtrtl.de
connect.tapjoy.com
fls-eu.amazon.de
api.vungle.com
g.alicdn.com
wd.adcolony.com
consent.google.com
gfe.nvidia.com
events.gfe.nvidia.com
gfwsl.geforce.com

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r–r-- 1 root root 1493 Aug 21 16:09 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=195.186.1.111
interface=eth0

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r–r-- 1 root root 3027 Aug 21 16:09 /etc/lighttpd/lighttpd.conf
server.modules = (
“mod_access”,
“mod_accesslog”,
“mod_auth”,
“mod_expire”,
“mod_compress”,
“mod_redirect”,
“mod_setenv”,
“mod_rewrite”
)
server.document-root = “/var/www/html”
server.error-handler-404 = “pihole/index.php”
server.upload-dirs = ( “/var/cache/lighttpd/uploads” )
server.errorlog = “/var/log/lighttpd/error.log”
server.pid-file = “/var/run/lighttpd.pid”
server.username = “www-data”
server.groupname = “www-data”
server.port = 80
accesslog.filename = “/var/log/lighttpd/access.log”
accesslog.format = “%{%s}t|%V|%r|%s|%b”
index-file.names = ( “index.php”, “index.html”, “index.lighttpd.html” )
url.access-deny = ( “~”, “.inc”, “.md”, “.yml”, “.ini” )
static-file.exclude-extensions = ( “.php”, “.pl”, “.fcgi” )
compress.cache-dir = “/var/cache/lighttpd/compress/”
compress.filetype = ( “application/javascript”, “text/css”, “text/html”, “text/plain” )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell “/usr/share/lighttpd/create-mime.assign.pl”
include_shell “find /etc/lighttpd/conf-enabled -name ‘*.conf’ -a ! -name ‘letsencrypt.conf’ -printf 'include “%p”
’ 2>/dev/null”
$HTTP[“url”] =~ “^/admin/” {

   setenv.add-response-header = (
       "X-Pi-hole" => "The Pi-hole Web interface is working!",
       "X-Frame-Options" => "DENY"
   )
   $HTTP["url"] =~ ".ttf$" {

       setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
   }

}
$HTTP[“url”] =~ “^/admin/.(.*)” {
url.access-deny = ("")
}
include_shell “cat external.conf 2>/dev/null”

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r–r-- 1 root root 1630 Aug 21 16:09 /etc/cron.d/pihole
29 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
27 19 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r–r-- 1 www-data www-data 388 Aug 21 15:27 /var/log/lighttpd/error.log
2018-08-20 06:25:03: (server.c.1242) logfiles cycled UID = 0 PID = 24146
2018-08-21 14:57:33: (server.c.1558) server stopped by UID = 0 PID = 1
2018-08-21 14:57:34: (log.c.164) server started
2018-08-21 15:04:23: (server.c.1558) server stopped by UID = 0 PID = 1
2018-08-21 15:04:23: (log.c.164) server started
2018-08-21 15:27:45: (server.c.1558) server stopped by UID = 0 PID = 1

*** [ DIAGNOSING ]: contents of /var/log

-rw-r–r-- 1 pihole pihole 12213 Aug 21 15:59 /var/log/pihole-FTL.log
[2018-08-21 00:00:03.270] NOTICE: pihole.log has been flushed
[2018-08-21 00:00:03.270] Resetting internal data structure
[2018-08-21 00:00:03.270] Queries in memory before flushing: 34544
[2018-08-21 00:00:03.271] FATAL: Trying to free NULL pointer in pihole_log_flushed() (flush.c:61)
[2018-08-21 00:00:03.631] Gravity list entries: 159584
[2018-08-21 00:00:03.631] Blacklist entries: 89
[2018-08-21 00:00:03.631] No wildcard blocking list present
[2018-08-21 00:00:03.632] Notice: Increasing queries struct size from 0 to 10000 (455.90 KB)
[2018-08-21 00:00:03.632] Notice: Increasing domains struct size from 0 to 1000 (475.90 KB)
[2018-08-21 00:00:03.632] Notice: Increasing clients struct size from 0 to 10 (476.06 KB)
[2018-08-21 00:00:03.644] New client: 192.165.10.1 n10p001.cloettafazer.se (0/10)
[2018-08-21 00:00:03.644] Notice: Increasing overTime struct size from 0 to 100 (480.11 KB)
[2018-08-21 00:00:03.644] Notice: Increasing forwarded struct size from 0 to 4 (480.23 KB)
[2018-08-21 00:00:03.739] New forward server: 213.73.91.35 (0/4)
[2018-08-21 00:00:03.860] New forward server: 85.214.20.141 h1768020.stratoserver.net (1/4)
[2018-08-21 00:00:03.964] New client: 127.0.0.1 localhost (1/10)
[2018-08-21 00:00:04.043] Notice: Increasing overTime struct size from 100 to 200 (501.61 KB)
[2018-08-21 00:00:04.043] Notice: Increasing queries struct size from 10000 to 20000 (941.61 KB)
[2018-08-21 00:00:04.123] Imported 13301 queries from the long-term database
[2018-08-21 00:00:04.124] Reading from /var/log/pihole.log (rw-r–r--)
[2018-08-21 00:01:00.105] Notice: Database size is 385.65 MB, deleted 3 rows
[2018-08-21 00:59:01.164] Notice: Database size is 385.65 MB, deleted 173 rows
[2018-08-21 01:59:01.141] Notice: Database size is 385.65 MB, deleted 229 rows
[2018-08-21 02:59:01.078] Notice: Database size is 385.65 MB, deleted 184 rows
[2018-08-21 03:59:01.116] Notice: Database size is 385.66 MB, deleted 140 rows

*** [ DIAGNOSING ]: Pi-hole log
-rw-r–r-- 1 dnsmasq root 4312337 Aug 21 15:04 /var/log/pihole.log
-----head of pihole.log------
Aug 21 00:00:03 dnsmasq[4602]: 2176998 127.0.0.1/52107 query[PTR] 1.10.165.192.in-addr.arpa from 127.0.0.1
Aug 21 00:00:03 dnsmasq[4602]: 2176998 127.0.0.1/52107 cached 192.165.10.1 is n10p001.cloettafazer.se
Aug 21 00:00:03 dnsmasq[4602]: 2176999 127.0.0.1/41668 query[PTR] 35.91.73.213.in-addr.arpa from 127.0.0.1
Aug 21 00:00:03 dnsmasq[4602]: 2176999 127.0.0.1/41668 forwarded 35.91.73.213.in-addr.arpa to 213.73.91.35
Aug 21 00:00:03 dnsmasq[4602]: 2176999 127.0.0.1/41668 forwarded 35.91.73.213.in-addr.arpa to 85.214.20.141
Aug 21 00:00:03 dnsmasq[4602]: 2176999 127.0.0.1/41668 reply 213.73.91.35 is NXDOMAIN
Aug 21 00:00:03 dnsmasq[4602]: 2177000 127.0.0.1/49405 query[PTR] 141.20.214.85.in-addr.arpa from 127.0.0.1
Aug 21 00:00:03 dnsmasq[4602]: 2177000 127.0.0.1/49405 forwarded 141.20.214.85.in-addr.arpa to 85.214.20.141
Aug 21 00:00:03 dnsmasq[4602]: 2177000 127.0.0.1/49405 reply 85.214.20.141 is h1768020.stratoserver.net
Aug 21 00:00:04 dnsmasq[4602]: 2177001 127.0.0.1/41425 query[PTR] 1.10.165.192.in-addr.arpa from 127.0.0.1
Aug 21 00:00:04 dnsmasq[4602]: 2177001 127.0.0.1/41425 cached 192.165.10.1 is n10p001.cloettafazer.se
Aug 21 00:01:13 dnsmasq[4602]: 2177002 192.165.10.1/54132 query[AAAA] www.google.com from 192.165.10.1
Aug 21 00:01:13 dnsmasq[4602]: 2177002 192.165.10.1/54132 forwarded www.google.com to 213.73.91.35
Aug 21 00:01:13 dnsmasq[4602]: 2177002 192.165.10.1/54132 forwarded www.google.com to 85.214.20.141
Aug 21 00:01:13 dnsmasq[4602]: 2177003 192.165.10.1/57297 query[A] www.google.com from 192.165.10.1
Aug 21 00:01:13 dnsmasq[4602]: 2177003 192.165.10.1/57297 forwarded www.google.com to 85.214.20.141
Aug 21 00:01:18 dnsmasq[4602]: 2177004 192.165.10.1/63663 query[AAAA] www.googleapis.com from 192.165.10.1
Aug 21 00:01:18 dnsmasq[4602]: 2177004 192.165.10.1/63663 /etc/pihole/black.list www.googleapis.com is 2a02:120b:2c09:7540:9689:bc6e:7ace:97c1
Aug 21 00:01:18 dnsmasq[4602]: 2177005 192.165.10.1/50834 query[A] www.googleapis.com from 192.165.10.1
Aug 21 00:01:18 dnsmasq[4602]: 2177005 192.165.10.1/50834 /etc/pihole/black.list www.googleapis.com is 192.165.10.15

0 Likes

#2

Please run the following command it should solve your issues

pihole checkout master

0 Likes

#3

If that does not work, what is the output of sudo service dnsmasq status -l

0 Likes

#4

I got the following error when running the command.

pi@raspberrypi:~ $ pihole checkout master
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y

[i] Shortcut “master” detected - checking out master branches…
[i] Pi-hole core
fatal: unable to access ‘https://github.com/pi-hole/pi-hole/’: Could not resolve host: github.com
[✗] Unable to pull Core master branch

0 Likes

#5

I got the following by running sudo service dnsmasq status -l

pi@raspberrypi:~ $ sudo service dnsmasq status -l
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled)
Drop-In: /run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: failed (Result: exit-code) since Tue 2018-08-21 16:09:54 CEST; 1h 12m in ago
Process: 9013 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status= 1/FAILURE)
Process: 9011 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUC CESS)
Main PID: 4602 (code=exited, status=0/SUCCESS)

Aug 21 16:09:54 raspberrypi dnsmasq[9011]: dnsmasq: syntax check OK.
Aug 21 16:09:54 raspberrypi dnsmasq[9013]: dnsmasq: junk found in command line
Aug 21 16:09:54 raspberrypi systemd[1]: dnsmasq.service: control process exi…1
Aug 21 16:09:54 raspberrypi systemd[1]: Failed to start dnsmasq - A lightwei…
Aug 21 16:09:54 raspberrypi systemd[1]: Unit dnsmasq.service entered failed …
Hint: Some lines were ellipsized, use -l to show in full.

0 Likes

#6

Use the following commands in the following order please

  1. sudo nano /etc/resolv.conf
  2. Change 127.0.0.1 or whatever is in the file to 9.9.9.9
  3. Save the file
  4. re-run pihole checkout master
0 Likes

#7

[That helped thank you. Pihole Version 4.0 is now running.

Should I reconfigure namserver to 127.0.0.1 ?

If I run sudo service dnsmasq status -l i still get errors.

pi@raspberrypi:~ $ sudo service dnsmasq status -l
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled)
Drop-In: /run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: failed (Result: exit-code) since Tue 2018-08-21 16:09:54 CEST; 1h 20min ago
Main PID: 4602 (code=exited, status=0/SUCCESS)

Aug 21 16:09:54 raspberrypi dnsmasq[9011]: dnsmasq: syntax check OK.
Aug 21 16:09:54 raspberrypi dnsmasq[9013]: dnsmasq: junk found in command line
Aug 21 16:09:54 raspberrypi systemd[1]: dnsmasq.service: control process exited, code=exited status=1
Aug 21 16:09:54 raspberrypi systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
Aug 21 16:09:54 raspberrypi systemd[1]: Unit dnsmasq.service entered failed state.
Aug 21 17:28:50 raspberrypi systemd[1]: Stopped dnsmasq - A lightweight DHCP and caching DNS server.

0 Likes

#8

This is because in Pi-Hole V4, FTLDNS does the work previously done by dnsmasq and dnsmasq is no longer started. In your debug log now you should see that dnsmasq is not active - here is what that section looks like on a typical V4 install (dnsmasq is inactive or failed):

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is inactive
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

This is not required. The configuration reverts to the correct configuration when you updated P-Hole. You can verify the contents of the file with

cat /etc/resolv.conf

0 Likes

#9

you are right resolv.conf shows the correct nameserver yet :slight_smile:

The diagnostics shows the following:

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is failed
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

Is it possible to deactive this deamon that i do not have the red failed message in the diagnostic file ?

0 Likes

#12

Regardless of whether it is disabled or uninstalled from your system that line will remain as is until the debugger is updated
Tthe reason being is that it checks the statius and depending on what it recieves says working or not.

The debugger will be updated soon™

0 Likes

closed #14

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

0 Likes