focal verification of 1.9.4-2ubuntu1.11 PASSED
1. started lxc container
lxc launch ubuntu-daily:focal
2. updated lxc container
lxc shell focal-unbound
sudo apt update && sudo apt full-upgrade
3. restarted container
4. uploaded files
lxc file push $FILE focal-unbound/root/
5. installed unbound
sudo apt install unbound
6. stopped unbound
sudo service stop unbound
7. copied unbound.conf
cp unbound.conf /etc/unbound/unbound.conf
8. made zones directory
mkdir /etc/unbound/zones
9. copied zones file
cp security.zone /etc/unbound/zones/
10. in a separate terminal, followed the journal to watch for the error
journalctl -f
11. started unbound
sudo service unbound start
12. saw the error [0]
13. stopped unbound
sudo service unbound stop
14. setup proposed by adding the following to sources.list
deb http://archive.ubuntu.com/ubuntu focal-proposed main universe restricted
15. apt update
16. upgraded unbound
sudo apt install unbound=1.9.4-2ubuntu1.11
17. on upgrade, service starts. following journalctl (journalctl -f), shows no
errors in launching[1]
NOTE: yes there is a time gap between install and upgrade. there were
some issues getting the amd64 package built, so i started verification
while requesting a retry on the build, ended up not getting back to it
quickly
[0]
Apr 04 14:19:03 focal-unbound systemd[1]: Starting Unbound DNS server...
Apr 04 14:19:03 focal-unbound package-helper[2433]:
/etc/unbound/zones/security.zone:9994: error: memory exhausted
Apr 04 14:19:03 focal-unbound package-helper[2433]: read
/etc/unbound/unbound.conf failed: 1 errors in configuration file
Apr 04 14:19:03 focal-unbound package-helper[2436]:
/etc/unbound/zones/security.zone:9994: error: memory exhausted
Apr 04 14:19:03 focal-unbound package-helper[2436]: read
/etc/unbound/unbound.conf failed: 1 errors in configuration file
Apr 04 14:19:03 focal-unbound unbound[2437]:
/etc/unbound/zones/security.zone:9994: error: memory exhausted
Apr 04 14:19:03 focal-unbound unbound[2437]: read /etc/unbound/unbound.conf
failed: 1 errors in configuration file
Apr 04 14:19:03 focal-unbound unbound[2437]: [1743776343] unbound[2437:0] fatal
error: Could not read config file: /etc/unbound/unbound.conf. Maybe try unbound
-dd, it stays on the commandline to see more errors, or unbound-checkconf
Apr 04 14:19:03 focal-unbound systemd[1]: unbound.service: Main process exited,
code=exited, status=1/FAILURE
Apr 04 14:19:03 focal-unbound systemd[1]: unbound.service: Failed with result
'exit-code'.
Apr 04 14:19:03 focal-unbound systemd[1]: Failed to start Unbound DNS server.
[1]
Apr 07 10:59:41 focal-unbound systemd[1]: Starting Unbound DNS server...
Apr 07 10:59:47 focal-unbound package-helper[7937]: /var/lib/unbound/root.key
has content
Apr 07 10:59:47 focal-unbound package-helper[7937]: success: the anchor is ok
Apr 07 10:59:47 focal-unbound unbound[7938]: [7938:0] notice: init module 0:
subnet
Apr 07 10:59:47 focal-unbound unbound[7938]: [7938:0] notice: init module 1:
validator
Apr 07 10:59:47 focal-unbound unbound[7938]: [7938:0] notice: init module 2:
iterator
Apr 07 10:59:47 focal-unbound unbound[7938]: [7938:0] info: start of service
(unbound 1.9.4).
Apr 07 10:59:47 focal-unbound systemd[1]: Started Unbound DNS server.
Apr 07 10:59:47 focal-unbound systemd[1]: Condition check resulted in Unbound
DNS server via resolvconf being skipped.
Apr 07 10:59:47 focal-unbound systemd[1]: Reloading.
Apr 07 10:59:47 focal-unbound systemd[1]: Configuration file
/run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible.
This has no effect as configuration data is accessible via APIs without
restrictions. Proceeding anyway.
Apr 07 10:59:47 focal-unbound systemd[1]: Reloading.
Apr 07 10:59:47 focal-unbound systemd[1]: Configuration file
/run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible.
This has no effect as configuration data is accessible via APIs without
restrictions. Proceeding anyway.
Apr 07 10:59:47 focal-unbound unbound[7938]: [7938:0] info: service stopped
(unbound 1.9.4).
Apr 07 10:59:47 focal-unbound systemd[1]: Stopping Unbound DNS server...
Apr 07 10:59:47 focal-unbound unbound[7938]: [7938:0] info: server stats for
thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected
by ip ratelimiting
Apr 07 10:59:47 focal-unbound unbound[7938]: [7938:0] info: server stats for
thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Apr 07 10:59:47 focal-unbound systemd[1]: unbound.service: Succeeded.
Apr 07 10:59:47 focal-unbound systemd[1]: Stopped Unbound DNS server.
Apr 07 10:59:47 focal-unbound systemd[1]: Starting Unbound DNS server...
Apr 07 10:59:53 focal-unbound package-helper[8016]: /var/lib/unbound/root.key
has content
Apr 07 10:59:53 focal-unbound package-helper[8016]: success: the anchor is ok
Apr 07 10:59:54 focal-unbound unbound[8018]: [8018:0] notice: init module 0:
subnet
Apr 07 10:59:54 focal-unbound unbound[8018]: [8018:0] notice: init module 1:
validator
Apr 07 10:59:54 focal-unbound unbound[8018]: [8018:0] notice: init module 2:
iterator
Apr 07 10:59:54 focal-unbound unbound[8018]: [8018:0] info: start of service
(unbound 1.9.4).
Apr 07 10:59:54 focal-unbound systemd[1]: Started Unbound DNS server.
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy
** Tags added: verification-done verification-done-focal verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087526
Title:
unbound cannot start with large zone files > 24.000 lines : memory
exhausted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2087526/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
