Package Details: pi-hole-server 5.3.1-3

Git Clone URL: https://aur.archlinux.org/pi-hole-server.git (read-only, click to copy)
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: 86
Popularity: 0.59
First Submitted: 2016-01-13 12:50
Last Updated: 2021-06-15 10:52

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

1 2 3 4 5 6 ... Next › Last »

pepper_chico commented on 2021-06-15 15:23

@max.bra, ok, thanks for the fix. I just thought that maybe other excerpts could need rebase reviewing, not only this special case. Maybe not.

max.bra commented on 2021-06-15 10:48

@pepper_chico oh! now i get it.
do you mean that our mimic_basic-install.sh functions are not the same of upstream ones?
ok, it's true. thanks for reporting.
small oversight sorry, but this is not a job for anyone here. if you find a problem, report it and it will be fixed, if possible, ASAP.

max.bra commented on 2021-06-15 10:31

@pepper_chico i really don't understand

pepper_chico commented on 2021-06-15 10:24

It seems forked sources here may need review & update. For example, I'm facing an issue that has been long fixed uptream, and should have been fixed here too, but isn't, because forked sources are not tracking upstream. See this fix present on 5.1.2 for example:

https://github.com/pi-hole/pi-hole/commit/643d2c0f3ea7871b64f9eaa2c9a5a2060d9ad14e

wazlecracker commented on 2021-05-09 00:26

Nevermind, deleting /etc/pihole/pihole-FTL.db and restarting the service fixed it.

wazlecracker commented on 2021-05-09 00:22

My long term data is not populating. Noticing some errors in the service when I run sudo systemctl status pihole-FTL.service:

● pihole-FTL.service - Pi-hole FTLDNS engine
     Loaded: loaded (/usr/lib/systemd/system/pihole-FTL.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2021-04-16 11:13:00 EDT; 3 weeks 1 days ago
    Process: 352 ExecStartPre=/bin/chown -R pihole:pihole /etc/pihole (code=exited, status=0/SUCCESS)
    Process: 358 ExecStartPre=/bin/chown root:root /etc/pihole/logrotate (code=exited, status=0/SUCCESS)
   Main PID: 359 (pihole-FTL)
      Tasks: 7 (limit: 4915)
        CPU: 213ms
     CGroup: /system.slice/pihole-FTL.service
             └─359 /usr/bin/pihole-FTL no-daemon

Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.431 359M] Finished config file parsing
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.516 359M] Database version is 8
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] Updating long-term database to version 9
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] SQLite3 message: table aliasclient already exists in "CREATE TABLE aliasclient (id INTEGER PRIMARY KEY NOT NULL, name TEXT NOT NULL, comment TEXT);" (1)
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] ERROR: SQL query "CREATE TABLE aliasclient (id INTEGER PRIMARY KEY NOT NULL, name TEXT NOT NULL, comment TEXT);" failed: SQL logic error
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] ERROR: create_aliasclients_table() failed!
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] Aliasclients table not initialized, database not available
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] SQLite3 message: API call with invalid database connection pointer (21)
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] SQLite3 message: misuse at line 165242 of [5d4c65779d] (21)
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] Error while trying to clos

steadybright commented on 2021-04-23 20:59

I know this is getting off track, but I've since enabled IPv6 (within the last hour): All's well on the LAN side, but my ISP does not support IPv6, so I'm limited to to IP4 on the WAN, which is why I see the IPv6 connection errors, I suppose.

max.bra commented on 2021-04-23 19:52

I don't want to be intrusive: maybe ipv6 configuration was incomplete or only link-local (fe80::/10). mmmh, actually, specially with win10 clients a pi-hole protected lan should be fully ipv6 enabled.

steadybright commented on 2021-04-23 18:28

@max.bra My pi-hole-server instance is running on my Arch Linux server. I have a Raspberry Pi 4B that also runs on Arch Linux (linux-raspberrypi, thanks to @graysky), but I do not run pi-hole on it. Some time ago, I disabled IPv6 on my Arch server because I was receiving incessant messages about connection failures from urbackup (among others) because they were looking to connect on IPv6. Disabling IPv6 fixed that issue, but apparently is causing other problems. It was a band-aid approach, and I suppose I should re-enable IPv6 on the server and just delete the logs more frequently.

max.bra commented on 2021-04-23 16:54

you are welcome, thanks to you.
p.s.: obviously it would have been possible to solve by enabling a full ipv6 on your lan. if you are interested (choosing archlinux instead of a more classic raspberry distribution makes me think of it) would solve all your future problems without any system "hacking".

read: ... a more classic and pihole supported distribution ...