Closed pengelana closed 1 year ago
There has been a bug fix, slated for upcoming releases, that is in the code repository. https://github.com/NLnetLabs/unbound/commit/4517dcd439562cb1df07e77738153c0c906bb069 could solve the issue, perhaps.
This fix deals with install paths. Different python components can report different install paths. And the fix picks the ones that seem most relevant given the python version.
Does that fix the issue for you, the version from the code repository?
Thanks @wcawijngaards Unbound 1.17.1 with patch from https://github.com/NLnetLabs/unbound/commit/4517dcd439562cb1df07e77738153c0c906bb069 working fine.
I'm experiencing this on 1.17.1_2
2023-02-20T14:25:24-07:00 | Critical | unbound | [89033:0] fatal error: failed to setup modules | |
---|---|---|---|---|
2023-02-20T14:25:24-07:00 | Error | unbound | [89033:0] error: module init for module python failed | |
2023-02-20T14:25:24-07:00 | Error | unbound | [89033:0] error: pythonmod: python error: NoneType: None | |
2023-02-20T14:25:24-07:00 | Error | unbound | [89033:0] error: pythonmod: can't parse Python script dnsbl_module.py |
Describe the bug Unbound 1.17.1 Successfully build with python 3.6 but failed after start.
Expected behavior Working fine until Unbound 1.17.0
System:
unbound -V
output: