Your message dated Wed, 14 Feb 2024 09:27:17 +0300
with message-id <[email protected]>
and subject line Re: Bug#907314: unbound: exception in python module due to the
dnameAsStr() function
has caused the Debian Bug report #907314,
regarding unbound: exception in python module due to the dnameAsStr() function
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
907314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907314
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: unbound
Version: 1.7.3-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
trying to implement an unbound python module (python code executed
while the unbound server is handling requests and responses, see the
pythonmod/ in unbound's source code).
* What exactly did you do (or not do) that was effective (or
ineffective)?
starting with the log.py example (included in the unbound's source
code), modified the print functions to make it work with Python3, and
added a single print() to illustrate the problem:
print("=> %s"%q.qname_str)
When a client requests a resolution, the ubound server reports an exception
where it should not.
* What was the outcome of this action?
the exception reported is:
Traceback (most recent call last):
File "/etc/unbound/unbound.conf.d/log.py", line 120, in operate
logDnsMsg(qstate)
File "/etc/unbound/unbound.conf.d/log.py", line 70, in logDnsMsg
print("=> %s"%q.qname_str)
File "/usr/lib/python3/dist-packages/unboundmodule.py", line 132, in
_get_qname_str
def _get_qname_str(self): return dnameAsStr(self.qname)
TypeError: in method 'dnameAsStr', argument 1 of type 'char const *'
* What outcome did you expect instead?
the basic example should have worked, I wheched and it works fine
(exactly the same code) with unbound as packaged by CentOS. Same bug
with the unbound packaged in stretch though. Google did not help much
here.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.17.17-100.fc27.x86_64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect (in a Docker container)
Versions of packages unbound depends on:
ii adduser 3.117
ii dns-root-data 2018013001
ii libc6 2.27-4
ii libevent-2.1-6 2.1.8-stable-4
ii libfstrm0 0.3.0-1+b1
ii libprotobuf-c1 1.3.1-1
ii libpython3.6 3.6.6-2
ii libssl1.1 1.1.1~~pre9-1
ii libsystemd0 239-5
ii lsb-base 9.20170808
ii openssl 1.1.1~~pre9-1
ii unbound-anchor 1.7.3-1
unbound recommends no packages.
Versions of packages unbound suggests:
pn apparmor <none>
-- Configuration Files:
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf [Errno 2] No such
file or directory:
'/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf'
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.13.0-1
On Tue, 19 Apr 2022 20:18:02 +0300 Michael Tokarev <[email protected]> wrote:
[]
Can you please verify the problem still exists with current version of
unbound (1.13.1 or 1.15 currently in experimental)?
I tried this with log.py, - the examples provided by upstream in there
weren't updated for python3 still, but the thing appears to be working
at least. I know right to nothing about python so I can't say for sure.
Okay, almost 2 years without response, and it's been mentioned before
that this is fixed in upstream version >1.7. Let's close this one
finally, with more or less arbitrary version which seems to be working.
/mjt
--- End Message ---
