Automated Configuration Backup Fails To Upload
-
@stephenw10 I do not see a backupdebug.txt file in my tmp directory. I upgraded from 22.05 to 23.01 in February
-
And ACB has been working OK in 23.01 until recently?
-
@stephenw10 Honestly I haven't made many configuration changes in 23.01 - the ones I have made have failed initially, but I just got around to posting about it now.
I see all the backups, including a test I took yesterday that completed on the first try, so perhaps this is just an intermittent issue.
-
Ah, so it does actually backup? Hmm, that's even more weird then if it shows that error every time.
-
@stephenw10 For clarity, it does not back up on the attempt that I get the message for - but from what I saw in the logs, it retries 15 minutes later or so, and I get no error.
-
Ah, hmm. Do you see any other DNS resolution issues?
Are you using DNSoverTLS? With Quad9 perhaps? There seems to be an issue with that, as yet, undefined.
-
@stephenw10 No, no other DNS resolution issues to speak of, Unbound is typically rock solid. I do use DNS over SSL/TLS
To give you a better sense of my configuration - I have pfBlockerNG installed, so all traffic for all clients on my primary LAN Interface/VLANs go through Unbound, with no downstream server.
The only exception is my guest interface/VLAN used for wireless and IOT - the DHCP server on that Interface/VLAN is set up to dole out external DNS servers (starts with Cloudflare, then to Google, then to Quad9), and I have firewall rules in place to prevent that Interface from exchanging traffic with my primary VLANs. I was actually adding secondary Google DNS server and Quad9 to that DNS server list when I got this error - I wouldn't think that would affect the resolver, but I attempted to replicate the error by changing the order of the DNS servers in the DHCP settings for the Guest network.
The error did reoccur - see below for the logs, the resolver is not showing any issues, but it is showing that Unbound was restarted. The General log shows the error message about the config upload failing.
Unbound log:
General log:
It has been 1/2 hour now since I made that change, and the backup has not attempted to reupload. Also, as another datapoint, the backup didn't fail when I changed some UPS settings in NUT a few days ago.
-
@pdavis said in Automated Configuration Backup Fails To Upload:
I do use DNS over SSL/TLS
To Quad9?
That error sure looks like it actually failed to resolve. I can't see what else could trigger it.
-
@stephenw10 No, not to Quad9 - no downstream servers configured for primary LAN interface, just Unbound.
And Unbound has no problem resolving that URL - I really think it's an issue of timing, DNS services loading as the backup is trying to upload. It is backed up now, and other changes upload immediately.
-
Hmm, it could be I guess if it's under significant load.
-
@stephenw10 Um, I do tend to go a wee bit overboard on the pfBlockerNG lists... ;-)
