noble sru test:

following test plan

1. i have the files already :)
2. start noble lxc instance
3. pushed files
4. install unbound from `-updates` (1.19.2-1ubuntu3.3)
5. stopped unbound
6. put config and security.zones into proper place
7. started unbound, saw the known failure [0]
8. stopped unbound
9. configured proposed by adding `noble-proposed` to 
`/etc/apt/sources.list.d/ubuntu.sources`
10. apt update
11. apt install unbound=1.19.2-1ubuntu3.4
12. journal does _not_ show the memory exhausted. it does show the mentioned 
resolveconf issue, unrelated to the memory exhaustion issue [1]

[0]
Mar 14 17:32:36 unbound-sru-noble systemd[1]: Starting unbound.service - 
Unbound DNS server...
Mar 14 17:32:36 unbound-sru-noble unbound-helper[2506]: 
/etc/unbound/zones/security.zone:9994: error: memory exhausted
Mar 14 17:32:36 unbound-sru-noble unbound-helper[2506]: read 
/etc/unbound/unbound.conf failed: 1 errors in configuration file
Mar 14 17:32:36 unbound-sru-noble unbound-helper[2509]: 
/etc/unbound/zones/security.zone:9994: error: memory exhausted
Mar 14 17:32:36 unbound-sru-noble unbound-helper[2509]: read 
/etc/unbound/unbound.conf failed: 1 errors in configuration file
Mar 14 17:32:36 unbound-sru-noble (unbound)[2510]: unbound.service: Referenced 
but unset environment variable evaluates to an empty string: DAEMON_OPTS
Mar 14 17:32:36 unbound-sru-noble unbound[2510]: 
/etc/unbound/zones/security.zone:9994: error: memory exhausted
Mar 14 17:32:36 unbound-sru-noble unbound[2510]: read /etc/unbound/unbound.conf 
failed: 1 errors in configuration file
Mar 14 17:32:36 unbound-sru-noble unbound[2510]: [1741973556] unbound[2510: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
Mar 14 17:32:36 unbound-sru-noble systemd[1]: unbound.service: Main process 
exited, code=exited, status=1/FAILURE
Mar 14 17:32:36 unbound-sru-noble unbound-helper[2514]: 
/etc/unbound/zones/security.zone:9994: error: memory exhausted
Mar 14 17:32:36 unbound-sru-noble unbound-helper[2514]: read 
/etc/unbound/unbound.conf failed: 1 errors in configuration file
Mar 14 17:32:36 unbound-sru-noble systemd[1]: unbound.service: Failed with 
result 'exit-code'.
Mar 14 17:32:36 unbound-sru-noble systemd[1]: Failed to start unbound.service - 
Unbound DNS server.

[1]
Mar 14 17:33:26 unbound-sru-noble systemd[1]: Starting unbound.service - 
Unbound DNS server...
Mar 14 17:33:26 unbound-sru-noble (unbound)[2729]: unbound.service: Referenced 
but unset environment variable evaluates to an empty string: DAEMON_OPTS
Mar 14 17:33:27 unbound-sru-noble unbound[2729]: [2729:0] notice: init module 
0: subnetcache
Mar 14 17:33:27 unbound-sru-noble unbound[2729]: [2729:0] notice: init module 
1: validator
Mar 14 17:33:27 unbound-sru-noble unbound[2729]: [2729:0] notice: init module 
2: iterator
Mar 14 17:33:27 unbound-sru-noble unbound[2729]: [2729:0] info: start of 
service (unbound 1.19.2).
Mar 14 17:33:27 unbound-sru-noble systemd[1]: Started unbound.service - Unbound 
DNS server.
Mar 14 17:33:27 unbound-sru-noble systemd[1]: Started 
unbound-resolvconf.service - Unbound asyncronous resolvconf update helper.
Mar 14 17:33:27 unbound-sru-noble systemd[1]: Reloading requested from client 
PID 2737 ('systemctl') (unit session-c2.scope)...
Mar 14 17:33:27 unbound-sru-noble systemd[1]: Reloading...
Mar 14 17:33:27 unbound-sru-noble resolvconf[2753]: Dropped protocol specifier 
'.unbound' from 'lo.unbound'. Using 'lo' (ifindex=1).
Mar 14 17:33:27 unbound-sru-noble systemd[1]: Reloading finished in 118 ms.
Mar 14 17:33:27 unbound-sru-noble resolvconf[2753]: Failed to set DNS 
configuration: Link lo is loopback device.
Mar 14 17:33:27 unbound-sru-noble systemd[1]: unbound-resolvconf.service: Main 
process exited, code=exited, status=1/FAILURE
Mar 14 17:33:27 unbound-sru-noble systemd[1]: unbound-resolvconf.service: 
Failed with result 'exit-code'.


** Tags removed: verification-needed-noble
** Tags added: verification-done-noble

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to