What about:
# grep -R -i resolved /etc/systemd/system/*
# grep -R -i resolved /lib/systemd/system/*
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) |
« First ‹ Previous 1 .. 30 31 32 33 34 35 36 37 38 39 40 .. 82 Next › Last »
What about:
# grep -R -i resolved /etc/systemd/system/*
# grep -R -i resolved /lib/systemd/system/*
@max.bra I don't recall doing so, however, I built the system quite a long time ago now. I could not swear to it. More to the point, even if I did enable it, I should be able to disable it in the usual way (which I cannot). If the implication is that I am not using Arch, I am using Arch Linux Arm.
@lewis2e in arch systemd-resolved it is not automatically enabled. that said, it should have been you who configured and enabled it.
Following every reboot, pihole.FTL fails to start. I have to manually stop the systemd-resolved.service and then restart pihole.FTL or it won't work.
I've tried disabling the systemd-resolved.service as described in the Arch Wiki, but it still starts up. I don't know how to find out what is calling for it. Any suggestions?
Please note that sudo
is required when using the UI:
lighttpd-angel[11938]: sh: sudo: command not found
@setBoolean
That worked for me. Thanks!
But I only added "ReadWritePaths" in the php-fm.service. That was enough.
I have 2 piholes running and it must changed after the php update to 7.4, because it worked before. I'm going to move/merge my old server to the new server. So one pihole installation is quite new. The old one is with openbasedir and the new one is without. Was the same problem.
'Network overview' isn't working on the new server. I don't care at the moment ;)
Edit:
There is also a permission problem when I flush the logs. At least in the terminal:
sudo pihole -f
[i] Flushing /run/log/pihole/pihole.log ...error: Ignoring /etc/pihole/logrotate because the file owner is wrong (should be root or user with uid 0).
error: Ignoring /etc/pihole/logrotate because the file owner is wrong (should be root or user with uid 0).
[✓] Restarting DNS service
[✓] Flushed /run/log/pihole/pihole.log
[✓] Deleted 149518 queries from database
I can change it to root but every restart of pihole will change it anyway.
@DanSman: Had the same problem and fixed it by adding the pihole http and /etc/pihole directory to "ReadWritePaths" in the php-fm.service file via drop-in.
@beedaddy mmm, yes maybe...
but I'm on php 7.4 on my PI and no problem here...
My guess is that DanSman experienced the same problem I did (see my comment from 2019-12-03 07:52). The solution was to downgrade from php 7.4 to 7.3.
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.