@max.bra - You might want to comment on that github issue. I found it by googling the error so it's reasonable to think that others will too.
Also, filesystem-2018.8-1 ships with an empty /etc/hosts
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.134716 |
First Submitted: | 2016-01-13 12:50 (UTC) |
Last Updated: | 2024-08-10 12:32 (UTC) |
« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 82 Next › Last »
@max.bra - You might want to comment on that github issue. I found it by googling the error so it's reasonable to think that others will too.
Also, filesystem-2018.8-1 ships with an empty /etc/hosts
yes but that comments are not correct.
$ cat /etc/resolv.conf
# Generated by resolvconf
search domain.local
nameserver 127.0.0.1
assuming 'archpi' as the local hostname
$ cat /etc/hosts
127.0.0.1 localhost.domain.local localhost
::1 localhost.domain.local localhost
<lanip_v4> archpi.domain.local archpi
<lanip_v6> archpi.domain.local archpi
127.0.0.1 is localhost and should never be the hostname
edit: corrected localhost domain
This is affecting out package: https://github.com/pi-hole/pi-hole/issues/1800
% pihole -g
[✗] DNS resolution is currently unavailable
[i] Time until retry: 85
The solution is to add an entry to /etc/hosts
BUT doing so breaks the ability of the webui to resolve local IP addresses to local hostnames, at least with my setup.
Others?
hi lmhp82, do you have some free ram memory and/or some swap? it seems you have reached some kind of limit in your box.
free -m
ulimit -a
will help you to find out your problem.
I’m running pi-hole on a Raspberry Pi Zero W on Arch Linux. Everything seems to be running correctly except when running pihole -g
Expected Behaviour: Update ad serving domains
Actual Behaviour: $ pihole -g [i] Neutrino emissions detected… /opt/pihole/gravity.sh: xmalloc: cannot allocate 93249269 bytes /opt/pihole/gravity.sh: xrealloc: cannot allocate 94812160 bytes $
Debug Token: Pi-hole debug options are disabled.
ArchLinux distribution of Pi-hole is not supported by official project and this debug report CAN NOT be uploaded to their debug team. Follow instructions carefully on the project wiki page (https://wiki.archlinux.org/index.php/Pi-hole 1) and please refer to AUR package web page for support and debugging (https://aur.archlinux.org/packages/pi-hole-server 1).
no, FTL should not remain stopped. pihole script "unlink" blocklists and restart FTL (dnsmasq) to block zero IP, wait for requested timeout then "relink" blocklists and restart FTL again to reload blocked IPs.
my web admin page show 0 domain blocked, the countdown and meantime all is usable.
any syslog relevant? are you in a container?
@max.bra - If I hit the 'disable for 5 minutes' the entire web GUI freezes up for about 25 seconds. When it unfreezes, I show 0 domains on the block list and FTL is offline (the offline bit is expected, no)? When 5 min is up, FTL reloads and the normal amount of blocklisted domains returns.
@graysky seems to work here. your behavior?
@max.bra - Any thoughts on how to get the "disable pihole for xxx min" to work under 4.x?
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.