Not using configured address because it was previously declined

tiritibambix · July 22, 2023, 12:14pm

Expected Behaviour:

operating system :
Version: Linux version 6.1.21-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP Mon Apr 3 17:20:52 BST 2023
hardware: RaspberryPi 3
Pihole version:
Pi-hole v5.17.1
FTL v5.23
Web Interface v5.20.1

I recently changed my Static DHCP leases configuration to switch 2 machines on my network (one of my servers and my PC).
While my server was attributed the right IP address (the one formerly used by my PC), my PC is attributed another address in the range I specified.
I got the error message "Not using configured address because it was previously declined".

I need my PC to get the right IP address.

Actual Behaviour:

PC gets a random address in my IP addresses range: "Not using configured address because it was previously declined".

Debug Token:

I tried manually delete / edit the entries in /etc/pihole/dhcp.leases with no luck.

https://tricorder.pi-hole.net/fT0G3Gaz/

Bucking_Horn · July 22, 2023, 12:35pm

Run from your RPi3, what's the output of:

sudo grep -n DHCP.*192.168.1.106 /var/log/pihole/pihole.log*

followed by

sudo pihole-FTL arp-scan

tiritibambix · July 22, 2023, 12:45pm

sudo grep -n DHCP.*192.168.1.106 /var/log/pihole/pihole.log*

Returns DHCP 192.168.1.106 is nvidiashield.lan

That's weird because I assigned 192.168.1.107 to it but it is not visible in the currently active DHCP leases.

So this might be the problem. But how can I force it ?

sudo pihole-FTL arp-scan

returns this (and only this ?):


ARP scan on interface eth0 (192.168.1.101/24) finished
IP address       Interface        Hostname                 MAC address        Reply rate
192.168.1.101    eth0             N/A                      b8:27:eb:bf:dd:88  100 %
192.168.1.102    eth0             N/A                      dc:a6:32:9f:d7:98  100 %
192.168.1.103    eth0             N/A                      d0:50:99:11:05:75  100 %
192.168.1.104    eth0             N/A                      90:1b:0e:66:cb:0b  100 %

Bucking_Horn · July 22, 2023, 12:49pm

That seems to be shortened - please provide the full output.

tiritibambix · July 22, 2023, 12:51pm

Just endlessly repeating lines

/var/log/pihole/pihole.log:Oct 29 07:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 29 08:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 29 09:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 29 10:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 29 11:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 29 12:00:01 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 30 13:00:00 dnsmasq[2190]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 30 14:00:00 dnsmasq[2190]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 30 15:00:00 dnsmasq[2190]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 30 16:00:00 dnsmasq[2190]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 30 17:00:00 dnsmasq[2190]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:Oct 30 18:00:00 dnsmasq[2190]: DHCP 192.168.1.106 is nvidiashield.lan
[...]

Bucking_Horn · July 22, 2023, 1:00pm

Ok, those look to be triggered by Pi-hole's hourly reverse lookups for observed client IPs, indicating that address is in use by a DHCP lease to a client named nvidiashield.lan.

You probably ran that grep before I finished finetuning it.
It seems the grep you ran just analysed one file, as your output is missing file names and line numbers.
I'd like to further extend that to all available logs, including the compressed ones.

Could you run the following statement, please:

sudo zgrep -n DHCP.*192.168.1.106 /var/log/pihole/pihole.log*

We can ignore the already known output for that, but I'd be curious to know whether it would show the actual DHCP lease negotiation for that client.

tiritibambix · July 22, 2023, 1:08pm

Copied the entirety of the log.
edit: nope, because "An error occurred: Body is limited to 40000 characters; you entered 192881."
So I truncated including only most recent lines.

Summary

/var/log/pihole/pihole.log:16594566:Feb  3 03:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16600549:Feb  3 04:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16605039:Feb  3 05:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16606880:Feb  3 05:27:21 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:16607223:Feb  3 05:28:23 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:16611991:Feb  3 06:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16616579:Feb  3 07:00:01 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16620850:Feb  3 08:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16628660:Feb  3 09:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16634835:Feb  3 10:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16640128:Feb  3 11:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16648168:Feb  3 12:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16654187:Feb  3 13:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16660545:Feb  3 14:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16667322:Feb  3 15:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16674695:Feb  3 16:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16681396:Feb  3 17:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16686468:Feb  3 18:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16692848:Feb  3 19:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16699268:Feb  3 20:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16706609:Feb  3 21:00:00 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16713106:Feb  3 21:52:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16714555:Feb  3 22:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16719985:Feb  3 23:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16725641:Feb  4 00:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16731534:Feb  4 01:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16735277:Feb  4 02:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16738607:Feb  4 03:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16744137:Feb  4 04:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16747735:Feb  4 05:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:16752112:Feb  4 06:00:00 dnsmasq[24106]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:22329236:Mar 15 20:47:06 dnsmasq-dhcp[637]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:22951469:Mar 20 21:13:34 dnsmasq-dhcp[637]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:23334857:Mar 23 21:41:06 dnsmasq-dhcp[637]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:23593437:Mar 26 15:53:42 dnsmasq-dhcp[11022]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:25062241:Apr 12 19:46:32 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:25297890:Apr 14 19:18:05 dnsmasq[644]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log:25297894:Apr 14 19:18:05 dnsmasq[644]: DHCP nvidiashield.lan is 192.168.1.106
/var/log/pihole/pihole.log:25727162:Apr 19 04:47:55 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:25727354:Apr 19 04:48:56 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:31659851:May 28 22:05:24 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:31660137:May 28 22:06:25 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
grep: /var/log/pihole/pihole.log: binary file matches
/var/log/pihole/pihole.log.1:7403:Oct 28 01:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:13914:Oct 28 02:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:18933:Oct 28 03:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:26407:Oct 28 04:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:31673:Oct 28 05:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:37862:Oct 28 06:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:44527:Oct 28 07:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:51119:Oct 28 08:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:58330:Oct 28 09:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:64461:Oct 28 10:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:74048:Oct 28 11:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:82073:Oct 28 12:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:89902:Oct 28 13:00:01 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:98734:Oct 28 14:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:108241:Oct 28 15:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:113619:Oct 28 16:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:119765:Oct 28 17:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:126788:Oct 28 18:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:134791:Oct 28 19:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.1:141230:Oct 28 20:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:5807:Oct 27 01:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:9417:Oct 27 02:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:13545:Oct 27 03:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:19976:Oct 27 04:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:24419:Oct 27 05:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:29561:Oct 27 06:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:34179:Oct 27 07:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:40667:Oct 27 08:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:46196:Oct 27 09:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:50848:Oct 27 10:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:56618:Oct 27 11:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:62421:Oct 27 12:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:67846:Oct 27 13:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:74701:Oct 27 14:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:80564:Oct 27 15:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:87531:Oct 27 16:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:94680:Oct 27 17:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:103463:Oct 27 18:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:108996:Oct 27 19:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:117891:Oct 27 20:00:01 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:123684:Oct 27 21:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:130034:Oct 27 22:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:137527:Oct 27 23:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.2.gz:144565:Oct 28 00:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:7112:Oct 26 01:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:12029:Oct 26 02:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:17118:Oct 26 03:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:23620:Oct 26 04:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:28252:Oct 26 05:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:34153:Oct 26 06:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:40208:Oct 26 07:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:45761:Oct 26 08:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:51666:Oct 26 09:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:59551:Oct 26 10:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:68141:Oct 26 11:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:79456:Oct 26 12:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:88199:Oct 26 13:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:96703:Oct 26 14:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:104161:Oct 26 15:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:111291:Oct 26 16:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:158570:Oct 26 23:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.3.gz:166816:Oct 27 00:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:5286:Oct 25 01:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:10902:Oct 25 02:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:15556:Oct 25 03:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:22263:Oct 25 04:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:28239:Oct 25 05:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:34251:Oct 25 06:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:39517:Oct 25 07:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:44752:Oct 25 08:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:51212:Oct 25 09:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:57564:Oct 25 10:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:67224:Oct 25 11:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:84473:Oct 25 12:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:98250:Oct 25 13:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:105459:Oct 25 14:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:114499:Oct 25 15:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:158334:Oct 25 22:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:166981:Oct 25 23:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.4.gz:175082:Oct 26 00:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:6167:Oct 24 01:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:40766:Oct 24 08:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:46192:Oct 24 09:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:51422:Oct 24 10:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:56592:Oct 24 11:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:62111:Oct 24 12:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:68654:Oct 24 13:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:74957:Oct 24 14:00:01 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:80534:Oct 24 15:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:87518:Oct 24 16:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:93337:Oct 24 17:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:105218:Oct 24 18:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:112017:Oct 24 19:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:117757:Oct 24 20:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:123784:Oct 24 21:00:01 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:129563:Oct 24 22:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:136144:Oct 24 23:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan
/var/log/pihole/pihole.log.5.gz:142414:Oct 25 00:00:00 dnsmasq[683]: DHCP 192.168.1.106 is nvidiashield.lan

Bucking_Horn · July 22, 2023, 1:13pm

That tells me you've missed an important character and used grep instead of zgrep.
(And only zgrep will handle compressed files, which grep sees as binaries.)

Also, let's try to shorten that output:

sudo zgrep -n dnsmasq-dhcp.*192.168.1.106 /var/log/pihole/pihole.log*

tiritibambix · July 22, 2023, 1:24pm

I double checked and I didn't forget the "z"

Here is the output of sudo zgrep -n dnsmasq-dhcp.*192.168.1.106 /var/log/pihole/pihole.log*:

root@RPi3:~# sudo zgrep -n dnsmasq-dhcp.*192.168.1.106 /var/log/pihole/pihole.log*
/var/log/pihole/pihole.log:1618947:Nov  7 19:35:07 dnsmasq-dhcp[2190]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:8174621:Dec 12 20:40:47 dnsmasq-dhcp[680]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:10984525:Jan  3 18:33:42 dnsmasq-dhcp[678]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:16606880:Feb  3 05:27:21 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:16607223:Feb  3 05:28:23 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:22329236:Mar 15 20:47:06 dnsmasq-dhcp[637]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:22951469:Mar 20 21:13:34 dnsmasq-dhcp[637]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:23334857:Mar 23 21:41:06 dnsmasq-dhcp[637]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:23593437:Mar 26 15:53:42 dnsmasq-dhcp[11022]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:25062241:Apr 12 19:46:32 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:25727162:Apr 19 04:47:55 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:25727354:Apr 19 04:48:56 dnsmasq-dhcp[644]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:31659851:May 28 22:05:24 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
/var/log/pihole/pihole.log:31660137:May 28 22:06:25 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
grep: /var/log/pihole/pihole.log: binary file matches

Bucking_Horn · July 22, 2023, 1:53pm

There's something odd about that output, as it contains quite old entries.
By default, Pi-hole would rotate log files once every day.

What's the output of

sudo ls -lah /var/log/pihole/pihole.log*

Did you perhaps change Pi-hole's logrotate schedule?

The most recent entry seems to be from May 28 - that is almost two months ago.
Also, there seems to be no preceding DHCPREQUEST before the listed DHCPACK?
Could you check the log files around that last match in the current log file?

sudo grep "May 28 22:0.*dnsmasq-dhcp" /var/log/pihole/pihole.log

tiritibambix · July 22, 2023, 2:42pm

root@RPi3:~# sudo ls -lah /var/log/pihole/pihole.log*
-rw-r----- 1 pihole pihole 3.0G Jul 22 16:05 /var/log/pihole/pihole.log
-rw-r----- 1 pihole pihole  13M Oct 29  2022 /var/log/pihole/pihole.log.1
-rw-r----- 1 pihole pihole 646K Oct 28  2022 /var/log/pihole/pihole.log.2.gz
-rw-r----- 1 pihole pihole 812K Oct 27  2022 /var/log/pihole/pihole.log.3.gz
-rw-r----- 1 pihole pihole 800K Oct 26  2022 /var/log/pihole/pihole.log.4.gz
-rw-r----- 1 pihole pihole 650K Oct 25  2022 /var/log/pihole/pihole.log.5.gz

No, I didn't.

root@RPi3:~# sudo grep "May 28 22:0.*dnsmasq-dhcp" /var/log/pihole/pihole.log
May 28 22:00:30 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:00:30 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:01:04 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:01:04 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:01:38 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:01:38 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:02:13 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:02:13 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:02:47 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:02:47 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:03:21 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:03:21 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:03:55 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:03:55 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:04:29 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:04:29 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:05:03 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:05:03 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:05:24 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) 48:b0:2d:6d:18:81
May 28 22:05:24 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
May 28 22:05:36 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:05:36 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:05:37 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:05:37 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:05:38 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:05:38 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:05:41 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:05:41 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:05:46 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:05:46 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:05:51 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:05:51 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:05:55 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:05:55 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:05:59 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:05:59 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:06:03 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:06:03 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:06:07 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:06:07 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:06:11 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:06:11 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:06:12 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:06:12 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:06:25 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) 48:b0:2d:6d:18:81
May 28 22:06:25 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.106 48:b0:2d:6d:18:81 nvidiashield
May 28 22:06:26 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) ea:9b:97:63:33:7c
May 28 22:06:26 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.137 ea:9b:97:63:33:7c OnePlus-Nord2-5G
May 28 22:06:46 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:06:46 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:07:20 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:07:20 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:07:54 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:07:54 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:08:15 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) a4:cf:12:f7:76:ac
May 28 22:08:15 dnsmasq-dhcp[8458]: DHCPOFFER(eth0) 192.168.1.116 a4:cf:12:f7:76:ac
May 28 22:08:15 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.116 a4:cf:12:f7:76:ac
May 28 22:08:15 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.116 a4:cf:12:f7:76:ac ESP_F776AC
May 28 22:08:26 dnsmasq-dhcp[8458]: DHCPDISCOVER(eth0) 34:ab:95:2c:6b:6b
May 28 22:08:26 dnsmasq-dhcp[8458]: DHCPOFFER(eth0) 192.168.1.136 34:ab:95:2c:6b:6b
May 28 22:08:26 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.136 34:ab:95:2c:6b:6b
May 28 22:08:26 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.136 34:ab:95:2c:6b:6b android-54f732452329cd8d
May 28 22:08:28 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:08:28 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:09:03 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:09:03 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink
May 28 22:09:37 dnsmasq-dhcp[8458]: DHCPREQUEST(eth0) 192.168.1.120 28:87:ba:ab:af:cc
May 28 22:09:37 dnsmasq-dhcp[8458]: DHCPACK(eth0) 192.168.1.120 28:87:ba:ab:af:cc tplink

Bucking_Horn · July 22, 2023, 3:34pm

So your presumed nvidiashield device (48:b0:2d) has acquired that 192.168.1.106 via a rapid commit following a DHCPDISCOVER broadcast on May 28.

This seems like a regular operation.
But it's strange that the most recent occurence seems to be that May 28.

If you inspect currently active leases under Pi-hole's Settings | DHCP, would there be an entry for that nvidiashield device (48:b0:2d)?
If so, would you be able to delete it?
Would that allow your aspired device to acquire .106?

It's also strange that your logs haven't been rotated for a long time (since October 2022):

tiritibambix:

root@RPi3:~# sudo ls -lah /var/log/pihole/pihole.log*
-rw-r----- 1 pihole pihole 3.0G Jul 22 16:05 /var/log/pihole/pihole.log
-rw-r----- 1 pihole pihole  13M Oct 29  2022 /var/log/pihole/pihole.log.1

What's the output of:

ls -lah /etc/pihole/logrotate

cat /var/lib/logrotate/pihole

sudo logrotate --debug /etc/pihole/logrotate

tiritibambix · July 22, 2023, 4:03pm

Ok so I just simply unplugged my nvidiashield and my PC got the address I wanted it to have. So I guess the problem is solved. sudo grep -n DHCP.*192.168.1.106 /var/log/pihole/pihole.log* showed me the way, so thank you.

Yet, it is weird it acted like this.

-rw-r--r-- 1 pihole pihole 241 Sep  6  2022 /etc/pihole/logrotate

logrotate state -- version 2
"/var/log/pihole/FTL.log" 2022-10-29-0:0:1
"/var/log/pihole/pihole.log" 2022-10-29-0:0:1

WARNING: logrotate in debug mode does nothing except printing debug messages!  Consider using verbose mode (-v) instead if this is not what you want.

error: Ignoring /etc/pihole/logrotate because the file owner is wrong (should be root or user with uid 0).
Reading state from file: /var/lib/logrotate/status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state

Handling 0 logs

Bucking_Horn · July 22, 2023, 4:14pm

That ownership is wrong:

Should instead be listed as:

-rw-r--r-- 1 root root 241 Sep  6  2022 /etc/pihole/logrotate

Try applying

sudo chown root:root /etc/pihole/logrotate

and rerun

sudo logrotate --debug /etc/pihole/logrotate

tiritibambix · July 22, 2023, 4:31pm

Whoops, i get chmod: invalid mode: ‘root:root’

But I have root:x:0:0:root:/root:/bin/bash when I list users...

Edit: wouldn't it be chown instead ?

Edit2: So yeah, I sudo chown root:root /etc/pihole/logrotate
Now, ls -lah /etc/pihole/logrotate returns

-rw-r--r-- 1 root root 241 Sep  6  2022 /etc/pihole/logrotate

So now

sudo logrotate --debug /etc/pihole/logrotate

returns

WARNING: logrotate in debug mode does nothing except printing debug messages!  Consider using verbose mode (-v) instead if this is not what you want.

reading config file /etc/pihole/logrotate
Reading state from file: /var/lib/logrotate/status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state

Handling 2 logs

rotating pattern: /var/log/pihole/pihole.log  after 1 days (5 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/pihole/pihole.log
Creating new state
  Now: 2023-07-22 18:33
  Last rotated at 2023-07-22 18:00
  log does not need rotating (log has already been rotated)

rotating pattern: /var/log/pihole/FTL.log  weekly (3 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/pihole/FTL.log
Creating new state
  Now: 2023-07-22 18:33
  Last rotated at 2023-07-22 18:00
  log does not need rotating (log has already been rotated)

rdwebdesign · July 22, 2023, 5:40pm

Yes. This was probably a typo.

Bucking_Horn · July 23, 2023, 10:18am

Indeed - I've edited my post accordingly.

Your logrotate --debug output looks ok now.
To verify that logs have been properly rotated since yesterday, you could check the logs again:

sudo ls -lah /var/log/pihole/pihole.log*

tiritibambix · July 23, 2023, 10:55am

Yes, logs have been properly rotated.

Everything is good now. Thank you very much for your kind and patient help

system · August 13, 2023, 10:56am

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.