Package Details: pi-hole-server 3.3-2

Git Clone URL: https://aur.archlinux.org/pi-hole-server.git (read-only)
Package Base: pi-hole-server
Description: The Pi-hole is an advertising-aware DNS/Web server. Arch adaptation for lan wide DNS server.
Upstream URL: https://github.com/pi-hole/pi-hole
Keywords: ad block pi-hole
Licenses: EUPL-1.1
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 28
Popularity: 1.597273
First Submitted: 2016-01-13 12:50
Last Updated: 2018-02-16 15:34

Pinned Comments

max.bra commented on 2018-02-09 16:45

ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream. First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips. When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.

Latest Comments

max.bra commented on 2018-02-16 15:37

@ryan updated! thanks for reporting.

ryanpetrello commented on 2018-02-16 14:50

@max.bra

Looks like a change in dnsmasq log format requirements:

https://github.com/pi-hole/pi-hole/issues/1956#issuecomment-366253763

https://github.com/pi-hole/pi-hole/issues/1956#issuecomment-366255479

Configuring dnsmasq with log-queries=extra 100% solved the problem for me. Maybe we could update the wiki?

max.bra commented on 2018-02-16 14:33

@ryanpetrello my dnsmasq log format is standard and the id is parsed correctly

are you on arm or x86_64? is your archlinux official? what's in your locale.conf? 'locale' output?

ryanpetrello commented on 2018-02-16 14:05

@max.bra

This indeed looks like an FTL bug. I tried building my own with this patched version of parser.c:

https://gist.github.com/ryanpetrello/8ecd4ea7cb94b84be939c1dc873cf3f8

After making this change, it works - I can see queries in the SQLite database and in the web UI.

Maybe the format of my dnsmasq changed somehow?

ryanpetrello commented on 2018-02-16 13:09

@max.bra very recent arch install (last few days), and I installed from AUR. Here's a snippet of pihole-FTL.log immediately after a systemctl restart:

https://gist.github.com/ryanpetrello/9850707cf9a2130c713f36b7faa50b97

It's definitely answering DNS, it's just that the database file is never written to (and so the admin console shows nothing).

Perhaps those Error getting ID for query are related?

max.bra commented on 2018-02-16 12:53

hey ryanpetrello, a little bit more about your system and install method: Is your arch clean and did you install from AUR packages only? Can you pastebin your FTL log? (/run/log/pihole-ftl/pihole-FTL.log)

ryanpetrello commented on 2018-02-16 12:40

@max.bra @graysky I've got pi-hole-ftl installed and it's properly blocking ads, but the statistics database never gets written to, so I can't see statistics:

~ dig s.amazon-adsystem.com | grep amazon ; <<>> DiG 9.8.3-P1 <<>> s.amazon-adsystem.com ;s.amazon-adsystem.com. IN A s.amazon-adsystem.com. 300 IN A (ip-of-pi.hole)

~ sudo grep DBFILE /etc/pihole/pihole-FTL.conf

DBFILE=/etc/pihole/pihole-FTL.db

~ ls -la /etc/pihole/pihole-FTL.db

-rw-r--r-- 1 pihole pihole 20480 Feb 16 07:21 /etc/pihole/pihole-FTL.db

~ sudo sqlite3 /etc/pihole/pihole-FTL.db

SQLite version 3.22.0 2018-01-22 18:45:57

Enter ".help" for usage hints.

sqlite> SELECT COUNT(*) FROM queries;

0

Any ideas or leads?

max.bra commented on 2018-02-09 16:45

ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream. First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips. When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.

max.bra commented on 2018-01-24 09:45

Hi Taijian and thanks for reporting. You are perfectly right! synced with upstream.

Taijian commented on 2018-01-23 22:42

I have the problem that my pi-hole resets the FTL output at midnight of every day, even though I have the config option 'TIMEFRAME=rolling24h' set in my pihole-FTL.conf. Investigating, I found that upstream calls pihole flush with the parameter 'once' when doing the nightly flushing, specifically so that the data of the previous day is still visible to FTL. Leaving out this parameter causes logrotate to be called twice. See here: https://github.com/pi-hole/pi-hole/blob/master/advanced/Scripts/piholeLogFlush.sh

I would therefore propose to change pi-hole-logtruncate.service as follows:

ExecStart=/usr/bin/pihole flush ONCE

All comments