Messages

1

23.1 Legacy Series / Re: unbound dns issues (logging, graphs and blocking)

« on: February 02, 2023, 04:49:11 am »

I created a new opnSense proxmox instance and will see what happens - maybe something went wonky during the upgrade. It's too much of a coincidence that unbound graphs stop right when the databases are vacuumed don't you think?

Anyway - I limited my block list to 1 list for now to also see if that makes a difference.

2

23.1 Legacy Series / Re: unbound dns issues (logging, graphs and blocking)

« on: February 01, 2023, 08:53:01 pm »

[update] New instance running of opnSense restored with settings (no issues installing/restoring) will give an update if I run into the issue again

3

23.1 Legacy Series / unbound dns issues (logging, graphs and blocking)

« on: February 01, 2023, 06:08:45 pm »

First of all: thanks for such a great open source firewall!

I updated from 22.7 to 23.1 manually and the parts that are supposed to work to get a stable connection still work.

However it seem that right after a vacuum command for a SQLLite3 database has been received the unbound logging that drives the graph and block log is not running anymore. Unbound works fine and there are no issues there.

Around 3:08 I see these messages in my logs.

2023-02-01T03:08:17-08:00   Notice   flowd_aggregate.py   vacuum done   
2023-02-01T03:08:17-08:00   Notice   flowd_aggregate.py   vacuum interface_086400.sqlite   
2023-02-01T03:08:17-08:00   Notice   flowd_aggregate.py   vacuum interface_003600.sqlite

This means that the database have been cleaned up and 'stray data' has been removed

But at that same moment the vacuum runs the logging stops for unbound queries which also results in a graph not being updated.

I also imported the same block list as I had running for my PiHole and it seems that it seems to ignore some block requests. I'm not sure why this happens but there might be a pattern match issue somewhere in the code (yes I double checked my block list)

Manually restarting unbound helps to get things moving again.

I have a replacement re-install (ProxMox) ready to go live at the end of the day but I'll keep my old instance in case there are questions with regards to logs or anything.