Many Unbound Log Errors after updating to 22.7.10

Started by IsaacFL, December 21, 2022, 05:13:18 PM

Previous topic - Next topic
I'm seeing multiple of these in the unbound logs:

2022-12-21T08:09:58-08:00 Error unbound [67156:3] error: pythonmod: python error: Traceback (most recent call last):
2022-12-21T08:09:58-08:00 Error unbound [67156:3] error: pythonmod: Exception occurred in function operate, event: module_event_new
      AttributeError: 'NoneType' object has no attribute 'query_reply'
      if reply_list.query_reply:
      File "dnsbl_module.py", line 168, in filter_query
      return ctx.filter_query(id, qstate, qdata)
      File "dnsbl_module.py", line 281, in operate

if prefetch support is enabled on Services: Unbound DNS: Advanced can you try to disable it ?

Can you try the following patch? https://github.com/opnsense/core/commit/2177d3e93b

# opnsense-patch 2177d3e93b
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

I just got back and applied the patch. It seems at first glance to have stopped the errors. I did not disable the prefetch support in Advanced.

Will watch to see if any problems.

Thanks! This was with restarting unbound or without? I think a restart might be required for it to render correctly.


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT


Perfect, thanks!
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

(Hotfix published)
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

I applied the hotfix (opnsense-22.7.10_2), but the hotfix itself doesn't restart unbound. Wouldn't that be necessary for it to pick up the changes?
Note: This post may have been lightly edited by AI for spelling and minor readability improvements. The content and findings are entirely my own.

Using 22.7.10_2 and patch applied. Still get these Unbound errors

You need to restart Unbound. It's literally what I said and IsaacFL confirmed and dinguz asked about...

@dinguz As a general rule we don't restart services on updates except when rebooting obviously. I'd consider the hotfix a problem solver for 22.7.9 or lower to 22.7.9_2, not necessarily from 22.7.9 to 22.7.9_2.


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

PS: Applying the hotfix followed by applying the patch will of course unfix the problem. Either patch on 22.7.10 or don't patch on 22.7.10_2.
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

Not applying the patch to 22.7.10_2 was not mentioned. So now what do I do. Still getting the Unbound errors.
Also, I did do a restart after applying the 22.7.10_2 update and still had the errors before I applied the patch.

@dcol
can you provide a full error text (with error text, line numbers etc.)?
it looks like patch revert. in this case you can try to patch again )

Fright,
Applied patch again, rebooted. No errors so far.