Like the head says:
Ans i see no changing dashboard, while pihole is running:
Looks like Pihole is working...
Only will see the graphs and the log
maby try pihole -r then setup again so you choose logging on
Run pihole -d for a debug token. If you chose to not log queries during setup, then this is expected.
Did what u both ask...
I am not a linux pro guys....
inaro@odroidxu4:~$ pihole status
::: DNS service is running
::: Pi-hole blocking is Enabled
linaro@odroidxu4:~$ pihole disable
::: Blocking has been disabled!
linaro@odroidxu4:~$ pihole -r
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
:::
::: You are root.
::: Repair option selected.
::: Verifying free disk space...
:::
::: Updating local cache of available packages... done!
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with Pi-hole installation...
::: Checking for apt-utils... installed!
::: Checking for dialog... installed!
::: Checking for debconf... installed!
::: Checking for dhcpcd5... installed!
::: Checking for git... installed!
::: Checking for iproute2... installed!
::: Checking for whiptail... installed!
::: --reconfigure passed to install script. Not downloading/updating local repos
::: Checking for bc... installed!
::: Checking for cron... installed!
::: Checking for curl... installed!
::: Checking for dnsmasq... installed!
::: Checking for dnsutils... installed!
::: Checking for iputils-ping... installed!
::: Checking for lsof... installed!
::: Checking for netcat... installed!
::: Checking for sudo... installed!
::: Checking for unzip... installed!
::: Checking for wget... installed!
::: Checking for lighttpd... installed!
::: Checking for php-common... installed!
::: Checking for php-cgi... installed!
:::
::: Installing scripts from /etc/.pihole... done.
:::
::: Installing configs from /etc/.pihole...
::: Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
::: Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf... done.
:::
::: Creating log file and changing owner to dnsmasq... already exists!
:::
::: Installing pihole custom index page...
::: Existing index.php detected, not overwriting
::: Existing index.js detected, not overwriting
::: Existing blockingpage.css detected, not overwriting
:::
::: Installing sudoer file... done!
:::
::: Installing latest Cron script... done!
:::
::: Installing latest logrotate script... done!
:::
::: Downloading latest version of FTL...
::: Detected ARM-hf architecture (armv7+)
::: Installing FTL... transferred... done.
::: Restarting services...
:::
::: Starting dnsmasq service... done.
:::
::: Enabling dnsmasq service to start on reboot... done.
:::
::: Starting lighttpd service... done.
:::
::: Enabling lighttpd service to start on reboot... done.
:::
::: Preparing to run gravity.sh to refresh hosts...
::: Cleaning up previous install (preserving whitelist/blacklist)
::: Running gravity.sh
:::
::: Neutrino emissions detected...
:::
::: Pulling source lists into range... done!
:::
::: Getting raw.githubusercontent.com list... done
::: Status: Success (OK)
::: List updated, transport successful!
::: Getting mirror1.malwaredomains.com list... done
::: Status: Success (OK)
::: List updated, transport successful!
::: Getting sysctl.org list... done
::: Status: Success (OK)
::: List updated, transport successful!
::: Getting zeustracker.abuse.ch list... done
::: Status: Success (OK)
::: List updated, transport successful!
::: Getting s3.amazonaws.com list... done
::: Status: Success (OK)
::: List updated, transport successful!
::: Getting s3.amazonaws.com list... done
::: Status: Success (OK)
::: List updated, transport successful!
::: Getting hosts-file.net list... done
::: Status: Success (OK)
::: List updated, transport successful!
:::
::: Aggregating list of domains... done!
::: Formatting list of domains to remove comments.... done!
::: 133050 domains being pulled in by gravity...
::: Removing duplicate domains.... done!
::: 109401 unique domains trapped in the event horizon.
:::
::: Adding adlist sources to the whitelist... done!
::: Whitelisting 8 domains... done!
::: Nothing to blacklist!
::: No wildcards used!
::: Formatting domains into a HOSTS file... done!
:::
::: Cleaning up un-needed files... done!
:::
::: Refresh lists in dnsmasq... done!
::: DNS service is running
::: Pi-hole blocking is Enabled
:::
::: Starting pihole-FTL service... done.
:::
::: Enabling pihole-FTL service to start on reboot... done.
::: done.
:::
::: Update complete!
:::
::: The install log is located at: /etc/pihole/install.log
linaro@odroidxu4:~$ pihole -d
::: Beginning Pi-hole debug at Mon Jun 12 15:43:11 CEST 2017!
:::
::: This process collects information from your Pi-hole, and optionally uploads
::: it to a unique and random directory on tricorder.pi-hole.net.
:::
::: 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.
:::
::: Please read and note any issues, and follow any directions advised during this process.
:::
::: ---= Detecting Installed Package Versions:
::: Pi-hole: v3.0.1 (master:v3.0.1-0-g26fcb1b)
::: Pi-hole Dashboard: v3.0.1 (master:v3.0.1-0-ge204cea)
::: lighttpd/1.4.35
::: PHP 7.0.18-0ubuntu0.16.04.1 (cli) ( NTS )
:::
::: ---= Detecting existence of /etc/pihole/setupVars.conf:
::: File exists, parsing...done and was successfully sourced
:::
::: ---= Detecting installed OS Distribution
:::
::: ---= Checking processor variety
:::
::: ---= Checking IPv6 Stack
::: IPv6 addresses located on enx001e06325acc
::: No gateway detected.
:::
::: ---= Checking IPv4 Stack
::: IPv4 addresses located on enx001e06325acc
::: Pinging default IPv4 gateway: Gateway responded.
::: Pinging Internet via IPv4: Query responded.
:::
::: ---= Daemon Process Information
::: Checking http port for lighttpd listener.
::: Correctly configured.
:::
::: ---= Daemon Process Information
::: Checking domain port for dnsmasq listener.
::: Correctly configured.
:::
::: ---= Daemon Process Information
::: Checking 4711 port for pihole-FTL listener.
::: Correctly configured.
:::
::: ---= Processes Check
::: Logging status of lighttpd, dnsmasq and pihole-FTL...
:::
::: ---= Resolver Functions Check (IPv4)
::: Checking for necessary lighttpd files.
:::
::: ---= Detecting existence of /etc/lighttpd/lighttpd.conf:
::: File exists, parsing...done
:::
::: ---= Detecting existence of /var/log/lighttpd/error.log:
::: /var/log/lighttpd/error.log not found!
:::
:::
::: ---= Detecting existence of /etc/dnsmasq.conf:
::: File exists, parsing...done
:::
::: ---= Detecting contents of /etc/dnsmasq.d/*:
:::
::: ---= File /etc/dnsmasq.d/01-pihole.conf found
::: Parsing...done
:::
::: ---= File /etc/dnsmasq.d/network-manager found
::: Parsing...done
:::
::: ---= File /etc/dnsmasq.d/README found
::: Parsing...done
:::
:::
::: ---= Detecting existence of /etc/pihole/whitelist.txt:
::: File exists, parsing...done
:::
::: ---= Detecting existence of /etc/pihole/blacklist.txt:
::: /etc/pihole/blacklist.txt not found!
:::
::: ---= Detecting existence of /etc/pihole/adlists.list:
::: File exists, parsing...done
:::
::: ---= Analyzing gravity.list
:::
::: ---= Analyzing pihole.log
::: Warning: No pihole.log file found!
:::
::: ---= Analyzing pihole-FTL.log
::: Warning: No pihole-FTL.log file found!
:::
::: --= User Action Required =--
::: Try loading a site that you are having trouble with now from a client web browser..
::: (Press CTRL+C to finish logging.)
:::
::: ---= pihole.log
::: Logging will automatically teminate in 60 seconds
::: Finshed debugging!.
cat: write error: No space left on device
::: The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
::: Would you like to upload the log? [y/N] n
::: Log will NOT be uploaded to tricorder.
::: There was an error uploading your debug log.
::: Please try again or contact the Pi-hole team for assistance.
Initially, I was going to ask if you have any clients using Pi-hole as their DNS server, but then I saw this:
This is likely your problem if dnsmasq cannot write any information the log file there would be zero values in the log.
mmm how can i solve that?
there is a 8 gig micro in.
use some place for home automation.
How many space is pihole using?
Is there a way to see what stuff use the space?
The best way to remove / clean the stuff that i do not need..
linaro@odroidxu4:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 931M 0 931M 0% /dev
tmpfs 200M 22M 178M 11% /run
/dev/mmcblk1p1 7.1G 4.1G 3.0G 58% /
tmpfs 997M 140K 997M 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 997M 0 997M 0% /sys/fs/cgroup
tmpfs 997M 77M 921M 8% /tmp
log2ram 50M 2.0M 49M 4% /var/log
tmpfs 200M 8.0K 200M 1% /run/user/1001
tmpfs 200M 0 200M 0% /run/user/999
linaro@odroidxu4:~$
Well, according to that you have space available...
Will you send the output of cat /var/log/pihole.log to us securely?
Hi!!
I have a really similar problem.
I think the pi.hole is working properly but it's not logging the activity. I also get this message when I run pihole -d.
cat: write error: No space left on device
Do you have any idea how to fix this? I have plenty of space in my sd for logging.
/dev/mmcblk0p1 14588M 2266M 12146M 16% /
Thanks!
This is a log2ram issue, besides using RAM for the /var/log directory, you will lose the data stored in /var/log on every reboot of the device.
1 Like