AUR (en) - pi-hole-server

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: pi-hole-server 5.18.3-4

Package Actions

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.2
Conflicts:	pi-hole-standalone
Submitter:	max.bra
Maintainer:	max.bra (graysky)
Last Packager:	max.bra
Votes:	112
Popularity:	0.49
First Submitted:	2016-01-13 12:50 (UTC)
Last Updated:	2024-08-10 12:32 (UTC)

Dependencies (18)

bc (bc-gh^AUR)
bind-tools (bind-development^AUR, bind-git^AUR, bind)
inetutils (inetutils-git^AUR, busybox-coreutils^AUR)
iproute2 (iproute2-git^AUR, busybox-coreutils^AUR, iproute2-selinux^AUR)
jq (jq-git^AUR)
logrotate (logrotate-git^AUR, logrotate-selinux^AUR)
lsof (lsof-git^AUR)
netcat (nmap-netcat^AUR, openbsd-netcat-git^AUR, gnu-netcat-svn^AUR, gnu-netcat, openbsd-netcat)
perl (perl-git^AUR)
pi-hole-ftl^AUR
procps-ng (procps-ng-git^AUR, busybox-coreutils^AUR)
sudo (fake-sudo^AUR, polkit-fakesudo^AUR, sudo-git^AUR, doas-sudo-shim^AUR, doas-sudo-shim-minimal^AUR, sudo-hg^AUR, sudo-selinux^AUR, fudo-git^AUR)
git (git-git^AUR, git-gl^AUR) (make)
lighttpd (optional) – a secure, fast, compliant and very flexible web-server
nginx-mainline (nginx-quic-openssl-hg^AUR, nginx-quic-libressl^AUR) (optional) – lightweight http server
php-cgi (optional) – CGI and FCGI SAPI for PHP needed only for lighttpd
php-fpm (optional) – FastCGI process manager for php needed for nginx
php-sqlite (optional) – sqlite db access for nginx

Required by (2)

padd-git
pi-hole-whitelist-git (optional)

Sources (15)

Pinned Comments

max.bra commented on 2018-02-09 16:45 (UTC) (edited on 2019-10-18 23:14 (UTC) by max.bra)

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

« First ‹ Previous 1 .. 58 59 60 61 62 63 64 65 66 67 68 .. 82 Next › Last »

ahrs commented on 2017-08-02 05:31 (UTC) (edited on 2017-08-02 05:34 (UTC) by ahrs)

sudo should be added as a dependency since it's used to display the Status in the web interface (https://github.com/pi-hole/AdminLTE/blob/f204b717078c89b6401b362f084734350ce13a51/scripts/pi-hole/php/header.php#L308)

graysky commented on 2017-07-22 15:18 (UTC)

I haven't used it as a DHCP before. You might wanna wait for max to comment. If not, report upstream. Do know that the Arch package does modified their files as you see in the PKGBUILD so it's possibly something we're doing. The best test is for you to spin up an ubuntu lxc and try it via their script. If it repeats, they're to blame :)

tsago commented on 2017-07-22 14:59 (UTC)

@graysky: Indeed. Pi-hole is the DHCP server. Config almost default (clean reinstall recently), only added DHCP range, local domain name, and manually imported static leases. (Note: tested with empty/no static leases file too) No improvement after restarting ftl or dnsmasq. The IP of the static lease is out of the DHCP range, though I don't think that should matter.

graysky commented on 2017-07-22 14:45 (UTC)

@tsago - That is using pi-hole as a DHCP server I assume?

tsago commented on 2017-07-22 14:31 (UTC)

Before I start blaming upstream, anybody observing this issue as well? Web-interface does not show any static leases. However, it successfully adds new static leases (I see new additions in /etc/dnsmasq.d/04-pihole-static-dhcp.conf). Several times even, if I retry the same static lease. Seems to be an issue purely with reading or displaying the static leases by the web interface.

graysky commented on 2017-07-01 19:41 (UTC)

Wild guess: does /usr/bin/makepkg honor aliases setup by users? I can't check the source now to see.

max.bra commented on 2017-07-01 15:08 (UTC)

any sed guru in the house? in ChuckHL configuration (and only for him, right now) in PKGBUILD prepare section, a sed seems to fail: # change log and bin location to logrotate sed -i "s|/var/log/pihole.log|/run/log/pihole/pihole.log|w $_ssc" "$srcdir"/$_pkgname-$pkgver/advanced/logrotate if [ -s $_ssc ] ; then rm $_ssc ; else echo " ==> Sed error: change log and bin location to logrotate 1" && return 1 ; fi sed -i "s|/var/log/pihole-FTL.log|/run/log/pihole-ftl/pihole-FTL.log|w $_ssc" "$srcdir"/$_pkgname-$pkgver/advanced/logrotate if [ -s $_ssc ] ; then rm $_ssc ; else echo " ==> Sed error: change log and bin location to logrotate 2" && return 1 ; fi first is successful, second fails. Moreover, if not able to substitute requested string second sed should fail and abort package creation...

max.bra commented on 2017-07-01 14:45 (UTC)

mmm, here it is let me try to understand why...

ChuckHL commented on 2017-07-01 14:26 (UTC) (edited on 2017-07-01 14:36 (UTC) by ChuckHL)

I completely reinstalled everything (piholeserver and ftl). I can see both directories: [root@alarm pihole]# ls -lah /run/log/ drwxr-xr-x 2 dnsmasq root 160 Jul 1 00:00 pihole drwxr-xr-x 2 pihole pihole 60 Jan 31 19:09 pihole-ftl [root@alarm pihole]# ls -lah /var/run/log/ drwxr-xr-x 2 dnsmasq root 160 Jul 1 00:00 pihole drwxr-xr-x 2 pihole pihole 60 Jan 31 19:09 pihole-ftl I still have the error. The interesting thing is that logrotate from the latest version on my devices seems different than yours. Here is the output of logrotate on the latest version on my machine: [root@alarm pihole]# cat logrotate /run/log/pihole/pihole.log { ... } /var/log/pihole-FTL.log { ...} Edit: I just modified logrotate I changed: /var/log/pihole-FTL.log { to this: /run/log/pihole-ftl/pihole-FTL.log { And finally, the problem was fixed.

max.bra commented on 2017-07-01 10:43 (UTC) (edited on 2017-07-01 10:43 (UTC) by max.bra)

this is current logrotate contents: $ cat /etc/pihole/logrotate /run/log/pihole/pihole.log { [...] } /run/log/pihole-ftl/pihole-FTL.log { [...] } and this is the situation since it was released FTL. Nothing point to /var, at least for now. have you ever executed official shell script 'basic-install.sh'?