Here are only a few of them. I deleted a lot of them so the bug report isnt bloat so much. DHCP Server: Unknown Entries: DDNS: cleaning up lease pointer for a cancel cb=0x14619d0: 856 Time(s) DDNS: cleaning up lease pointer for a cancel cb=0x1461a00: 1 Time(s) DDNS: cleaning up lease pointer for a cancel cb=0x1461a30: 1 Time(s) DDNS: cleaning up lease pointer for a cancel cb=0x1461bf0: 1 Time(s) DDNS: cleaning up lease pointer for a cancel cb=0x1463f50: 2 Time(s) DDNS: cleaning up lease pointer for a cancel cb=0x1464510: 1 Time(s) execute: /usr/sbin/unbound-dhcp-leases-client exit status 256: 1271 Time(s) execute_statement argv[0] = /usr/sbin/unbound-dhcp-leases-client: 1271 Time(s) execute_statement argv[1] = commit: 1269 Time(s) execute_statement argv[1] = expiry: 2 Time(s) execute_statement argv[2] = ADDRESS=192.168.6.11: 9 Time(s) execute_statement argv[2] = ADDRESS=192.168.6.112: 55 Time(s) execute_statement argv[2] = ADDRESS=192.168.6.12: 16 Time(s) execute_statement argv[2] = ADDRESS=192.168.6.35: 1 Time(s) execute_statement argv[2] = ADDRESS=192.168.6.37: 49 Time(s) execute_statement argv[3] = NAME=: 148 Time(s) execute_statement argv[3] = NAME=Apparillo: 16 Time(s) execute_statement argv[3] = NAME=iPhonevonMarc: 17 Time(s) execute_statement argv[3] = NAME=shellyem-485519D787A0: 47 Time(s) execute_statement argv[3] = NAME=shellyem-485519DA3093: 47 Time(s) execute_statement argv[3] = NAME=shellyplug-s-E190CE: 49 Time(s) execute_statement argv[3] = NAME=shellyplus1pm-0cdc7ef5b21c: 50 Time(s) It would be nice if we could cleanup this a bit.
The same as with bug13802 I don't see these messages at all in my dhcp log and I have looked for the whole of December. The words cleaning and execute are not present in the log at all. Are you using a mixture of fixed and dynamic leases and how many of each? I am only using fixed leases on my production system except when I have visitors staying for a while, when they go on the blue network and I use only dynamic for those.
In the forum this has also been raised and @Bernhard has said that these messages are part of the normal operation of the modified unbound-dhcp-leases-bridge code and that after everything is stable then those messages should be fed to null and no longer logged.
I have realised that I had misunderstood which log they were being found in. I had been looking in the System Logs section under dhcp server. I now realise they are from the Log Summary page. I also see them in there but just not so many as I don't have so many clients.