Package Details: pi-hole-server 5.18.3-4

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.50
First Submitted: 2016-01-13 12:50 (UTC)
Last Updated: 2024-08-10 12:32 (UTC)

Dependencies (18)

Required by (2)

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 .. 21 22 23 24 25 26 27 28 29 30 31 .. 82 Next › Last »

Taijian commented on 2020-08-12 08:37 (UTC)

Reporting back: I have disabled pi-hole-logtruncate.timer on my server and instead copied /etc/pihole/logrotate to /etc/logrotate.d.

Works! No conflict, logs got rotated.

One thing though: In order to keep the old behaviour of daily log rotation, the entry for pihole-ftl.log needs to be changed from 'weekly' to 'daily'.

eh8 commented on 2020-08-12 02:18 (UTC)

@Taijian I didn't pick up on this until you mentioned. I have modified my pi-hole-logtruncate.timer file to run at a non-intersecting time with logrotate.timer

Taijian commented on 2020-08-11 10:28 (UTC) (edited on 2020-08-11 10:29 (UTC) by Taijian)

@max.bra & @grayski:

I am noticing a persistent issue on my pihole-server (which is also running various other services for me), namely that logrotate.service will regularly fail because of a concurrency issue with both logrotate.service and pi-hole-logtruncate.service attempting to execute the logrotate binary at the same time.

This got me thinking: Wouldn't it be a more 'clean' approach to scrap pi-hole-logtruncate.{service,timer} and instead add a proper config-snippet into /etc/logrotate.d/?

EDIT: speeeling is hrad!

k.w commented on 2020-08-10 09:01 (UTC)

@krupan yes, base-devel is needed for AUR. See https://wiki.archlinux.org/index.php/Aur#Getting_started

wingsuit commented on 2020-07-31 23:17 (UTC)

@graysky No tried on various cleared browsers. Seem to be having a lot of database related issues, many stats aren't showing up. Will try a fresh install.

graysky commented on 2020-07-31 12:41 (UTC)

@wingsuit - Browser cache? See recent discussion belo.

wingsuit commented on 2020-07-31 11:38 (UTC) (edited on 2020-07-31 11:41 (UTC) by wingsuit)

Dashboard completely empty after upgrade, no more graphs or anything, any ideas?

Also, when going to the Group tab I get "DataTables warning: table id=groupsTable - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1"

max.bra commented on 2020-07-19 07:01 (UTC)

@adityaruplaha all is funcional here, but i'm on lighttpd

adityaruplaha commented on 2020-07-19 04:04 (UTC) (edited on 2020-07-19 06:46 (UTC) by adityaruplaha)

Issue: "Unable to write to readonly database". This happens for group management, Local DNS Records, etc.

Configuration: Manjaro + Apache (PHP-FPM) + PiHole 5.1

Web server user http is in group pihole, and /etc/pihole/gravity.db has 'g+w' permissions.

I also asked on the PiHole forums: https://discourse.pi-hole.net/t/unable-to-write-to-a-readonly-database-pi-hole-5-x-manjaro-apache/35802?u=adityaruplaha

krupan commented on 2020-07-18 19:29 (UTC) (edited on 2020-07-18 19:29 (UTC) by krupan)

I got:

==> ERROR: Cannot find the strip binary required for object file stripping.

Installing binutils fixed that. Then I got:

==> Starting prepare()...
/home/bmurdock/.cache/yay/pi-hole-ftl/PKGBUILD: line 38: patch: command not found
==> ERROR: A failure occurred in prepare().
    Aborting...

Installing patch fixed that.

Then I got:

==> ERROR: Cannot find the fakeroot binary.

Installing fakeroot fixed that. Then I got another error at at this point I just installed all of base-devel.