Hi Christopher, The text you are suggesting is under the "Python Module Options" section but only since version 1.6.1. If you want to run unbound in chroot and with the Python module enabled you need to make sure Python's library directory structure is bind mounted in the new root environment.
Best regards, -- George On 22/07/17 14:37, Christopher Hearn via Unbound-users wrote: > I managed to get it working, so updating here: > > chroot is enabled on unbound by default, so that's why it couldn't see any of > the python libs in /usr/lib/python2.7. Turning chroot off with chroot: "" > fixed the issue. I also had to make sure the python script was readable by > the unbound user. > > Can I suggest adding to unbound.conf man file that chroot has to be disabled > for it to work? Or, whatever other permutations would allow it to work with > it enabled (I'm not sure). > > >> On Jul 21, 2017, at 2:16 PM, Christopher Hearn <ch...@convorelay.com> wrote: >> >> I've installed unbound from the stable repos on debian jessie 8.8, unbound >> version 1.4.22. Installed via: "apt-get install unbound python-unbound". >> I'm not able to get the python module to load. If I add "module-config: >> "validator python iterator" to the config file, it fails the >> unbound-checkconf & thus fails to restart: >> >> [1500660297] unbound-checkconf[28142:0] fatal error: module conf 'validator >> python iterator' is not known to work >> >> I feel like I'm missing a simple step here but I can't figure out what it >> is. The man page says the above config should work. >
signature.asc
Description: OpenPGP digital signature
