Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#60956 - [bind] No longer able to resolve names with 9.13.4-1, logfile state "unable to set effective uid"

Attached to Project: Arch Linux
Opened by Nobody (ch888) - Monday, 03 December 2018, 10:34 GMT
Last edited by Sébastien Luttringer (seblu) - Sunday, 07 April 2019, 13:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Updating to the latest bind packages results in bind not anymore able to resolve any names; reverting to previous version solves the problem.
only difference between the versions are two lines in logfile where the new version complains about being not able to set the effective uid.

Additional info:
* package version(s)
working : /var/cache/pacman/pkg/bind-9.13.3-3-x86_64.pkg.tar.xz
failing : /var/cache/pacman/pkg/bind-9.13.4-1-x86_64.pkg.tar.xz

* config and/or log files etc.
working:
named[906]: generating session key for dynamic DNS
named[906]: sizing zone task pool based on 7 zones
failing:
named[906]: unable to set effective uid to 0: Operation not permitted
named[906]: generating session key for dynamic DNS
named[906]: unable to set effective uid to 0: Operation not permitted
named[906]: sizing zone task pool based on 7 zones

Steps to reproduce:
switch between working and failing version
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Sunday, 07 April 2019, 13:42 GMT
Reason for closing:  No response
Comment by Nobody (ch888) - Friday, 18 January 2019, 23:26 GMT
As obviously no one was/is working on the issue, I excluded the newer bind and bind-tools packages when upgrading and everything was ok.
But with the recent updates libidn2/bash/readline I experienced shared library issues, so I updated bind/bind-tools again which allowed them to start - but again name resolution failed.
Playing around with my named.conf file, it turned out that I have to comment out "query-source address * port 53;" to get name resolution working.
The two errors in logfile when starting bind ("unable to set effective uid to 0: Operation not permitted") are still there, but name resolution is working.
Comment by loqs (loqs) - Saturday, 19 January 2019, 10:51 GMT
Have you contacted upstream about the issues? https://lists.isc.org/mailman/listinfo/bind-users / https://gitlab.isc.org/isc-projects/bind9/issues
https://bbs.archlinux.org/viewtopic.php?id=242773 also had 'unable to set effective uid to 0: Operation not permitted' without resolution.

Loading...