CARVIEW |
Navigation Menu
-
-
Notifications
You must be signed in to change notification settings - Fork 397
Description
I'm on Win-10 and seems to have built Unbound and the Pytho3 module OK.
Test outputs from:
-
libunbound/python/examples/async-lookup.py:
Resolve error: could not fork -
libunbound/python/examples/ns-lookup.py
: Result:
raw data: 05 70 69 70 69 74 03 63 69 73 05 76 75 74 62 72 02 63 7A 00;05 72 68 69 6E 6F 03 63 69 73 05 76 75 74 62 72 02 63 7A 00
host: pipit.cis.vutbr.cz.
host: rhino.cis.vutbr.cz. -
libunbound/python/examples/dns-lookup.py
: Result: ['217.31.205.50'] -
libunbound/python/examples/example8-1.py
: Result:
raw data: 00 14 02 6D 78 03 6E 69 63 02 63 7A 00;00 0A 04 6D 61 69 6C 03 6E 69 63 02 63 7A 00
priority:10 address:mail.nic.cz.
priority:20 address:mx.nic.cz.
Result:
raw data: D9 1F CD 32
address:217.31.205.50
Result:
raw data: 01 64 02 6E 73 03 6E 69 63 02 63 7A 00;01 61 02 6E 73 03 6E 69 63 02 63 7A 00;01 62 02 6E 73 03 6E 69 63 02 63 7A 00
host: a.ns.nic.cz.
host: b.ns.nic.cz.
host: d.ns.nic.cz.
Seems pretty okay to me. But using an Python3 adaption of ubmodule-tst.py
, shows these errors:
bin/unbound.exe -ddvv -c F:/MinGW32/src/inet/DNS/Unbound/run/example.conf
[1696943035] unbound.exe[12256:0] notice: Start of Unbound 1.18.1.
[1696943035] unbound.exe[12256:0] debug: chdir to F:/MinGW32/src/inet/DNS/Unbound/run
[1696943035] unbound.exe[12256:0] debug: switching log to stderr
[1696943035] unbound.exe[12256:0] debug: module config: "python validator iterator"
[1696943035] unbound.exe[12256:0] notice: init module 0: python
[1696943035] unbound.exe[12256:0] info: F:/MinGW32/src/inet/DNS/Unbound/run/ubmodule-tst.py: script loaded.
[1696943035] unbound.exe[12256:0] info: F:/MinGW32/src/inet/DNS/Unbound/run/ubmodule-tst.py: init called, module id is 0 port: 53 script: <u
nboundmodule.config_strlist; proxy of <Swig Object of type 'config_strlist *' at 0x000001BA27916040> >
[1696943035] unbound.exe[12256:0] notice: init module 1: validator
[1696943035] unbound.exe[12256:0] notice: init module 2: iterator
[1696943035] unbound.exe[12256:0] debug: target fetch policy for level 0 is 3
[1696943035] unbound.exe[12256:0] debug: target fetch policy for level 1 is 2
[1696943035] unbound.exe[12256:0] debug: target fetch policy for level 2 is 1
[1696943035] unbound.exe[12256:0] debug: target fetch policy for level 3 is 0
[1696943035] unbound.exe[12256:0] debug: target fetch policy for level 4 is 0
[1696943035] unbound.exe[12256:0] error: could not create control compt.
[1696943035] unbound.exe[12256:0] fatal error: Could not initialize main thread
I did cook up an run/example.conf
based on doc/example.conf.in
containing:
server:
module-config: "python validator iterator"
python-script: "F:/MinGW32/src/inet/DNS/Unbound/run/ubmodule-tst.py"
What is this "control compt"
an how can I fix this?
System:
- Unbound version: 1.18.1
- OS: Win-10
unbound -V
output:
Version 1.18.1
Configure line: --with-libexpat --with-openssl --with-pyunbound --with-pythonmodule
[warn] signal.c: socketpair: Programmet har ikke kalt WSAStartup, eller WSAStartup mislyktes.
Linked libs: event winsock (it uses WSAWaitForMultipleEvents), OpenSSL 3.2.0-alpha3-dev
Linked modules: dns64 python cachedb respip validator iterator
BSD licensed, see LICENSE in source package for details.
Report bugs to https://github.com/NLnetLabs/unbound/issues
The [warn] signal.c:
seems unimportant for this issue (WSAStartup()
was not called).