Closed Kwbmm closed 5 years ago
Great catch!
@Kwbmm , thanks for raising this issue. Looking at your activity (and mine), I'm not seeing anything in the log which suggests that the vm is executing the daily crontab. I'll look into this further and see if I can figure out why it is not working.
@Kwbmm , I configured postfix on my VM to get the error that was being logged. That clued me in to a script fail on my part, which I've now corrected. Doing that and waiting a day resolved my issue. Any chance you can make the config change and give us a test too?
@Kwbmm , I configured postfix on my VM to get the error that was being logged. That clued me in to a script fail on my part, which I've now corrected. Doing that and waiting a day resolved my issue. Any chance you can make the config change and give us a test too?
I have performed the same changes you made in the PR. It will hopefully work.
Please let me know when you folks think the PR with the fix for this issue is ready for merging.
I have been trying to figure out whether autoupdate has been running on its own or not, I believe it does:
pihole.log
...
Sep 8 04:35:02 dnsmasq[2884]: query[AAAA] pi.hole from 127.0.0.1
Sep 8 04:35:02 dnsmasq[2884]: forwarded pi.hole to 8.8.4.4
Sep 8 04:35:02 dnsmasq[2884]: forwarded pi.hole to 8.8.8.8
Sep 8 04:35:02 dnsmasq[2884]: reply pi.hole is NODATA-IPv6
Sep 8 04:35:02 dnsmasq[2884]: query[AAAA] --- from 127.0.0.1
Sep 8 04:35:02 dnsmasq[2884]: forwarded --- to 8.8.4.4
Sep 8 04:35:02 dnsmasq[2884]: reply --- is NXDOMAIN
Sep 8 04:35:02 dnsmasq[2884]: query[AAAA] --- from 127.0.0.1
Sep 8 04:35:02 dnsmasq[2884]: forwarded --- to 8.8.4.4
Sep 8 04:35:02 dnsmasq[2884]: reply --- is NXDOMAIN
Sep 8 04:35:02 dnsmasq[2884]: query[AAAA] pi.hole.google.internal from 127.0.0.1
Sep 8 04:35:02 dnsmasq[2884]: forwarded pi.hole.google.internal to 8.8.4.4
Sep 8 04:35:02 dnsmasq[2884]: reply pi.hole.google.internal is NXDOMAIN
Sep 8 04:35:02 dnsmasq[2884]: query[A] pi.hole from 127.0.0.1
Sep 8 04:35:02 dnsmasq[2884]: /etc/pihole/local.list pi.hole is ---
Sep 8 04:35:02 dnsmasq[2884]: query[A] raw.githubusercontent.com from 127.0.0.1
Sep 8 04:35:02 dnsmasq[2884]: forwarded raw.githubusercontent.com to 8.8.4.4
Sep 8 04:35:02 dnsmasq[2884]: reply raw.githubusercontent.com is <CNAME>
...
Sep 8 04:35:13 dnsmasq[2884]: read /etc/hosts - 6 addresses
Sep 8 04:35:13 dnsmasq[2884]: read /etc/pihole/local.list - 2 addresses
Sep 8 04:35:13 dnsmasq[2884]: read /etc/pihole/black.list - 0 addresses
pihole-FTL.log
[2019-09-08 04:35:13.152 2884] Received SIGHUP, reloading cache
[2019-09-08 04:35:13.152 2884] Blocking status is enabled
[2019-09-08 04:35:13.152 2884] Compiled 0 Regex filters and 3 whitelisted domains in 0.1 msec (0 errors)
[2019-09-08 04:35:13.835 2884] /etc/pihole/black.list: parsed 0 domains (took 0.0 ms)
[2019-09-08 04:35:16.812 2884] /etc/pihole/gravity.list: parsed 1461877 domains (took 2977.7 ms)
[2019-09-08 11:22:00.544 2884] Resizing "/FTL-strings" from 28672 to 32768
[2019-09-08 20:24:38.499 2884] Resizing "/FTL-queries" from 688128 to 917504
Crontab log:
Sep 8 04:30:01 pi-hole CRON[16652]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole updatechecker local)
Sep 8 04:35:01 pi-hole CRON[16701]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log)
Sep 8 04:39:01 pi-hole CRON[16900]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
I can't tell if the autorestart works though, I think it was not needed in this case
Describe the bug The autoupdate described in the README.md file seems to not work for me. Here is crontab log (from
/var/log/syslog
):This is
pihole.log
:Expected behavior Pi-hole is updated daily. Web interface shouldn't show that there are updates available