| 2023-10-30 09:02:17 |
Peter Jose De Sousa |
description |
Hello,
When adding the subnet 10.33.56.0/24 to my maas installation named starts to crash and this in turn breaks commissioning & deployment
Named logs show the following:
tf=no' '--enable-ipv6' '--enable-rrl' '--enable-filter-aaaa' '--disable-native-pkcs11' '--disable-isc-spnego' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/bind9-TyRg0u/bind9-9.16.1=. -fstack-protector-strong
-Wformat -Werror=format-security -fno-strict-aliasing -fno-delete-null-pointer-checks -DNO_VERSION_DATE -DDIG_SIGCHASE' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
26-Oct-2023 16:26:47.364 running as: named -c /var/snap/maas/31022/bind/named.conf -S 524288 -g
26-Oct-2023 16:26:47.364 compiled by GCC 9.4.0
26-Oct-2023 16:26:47.364 compiled with OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
26-Oct-2023 16:26:47.364 linked to OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
26-Oct-2023 16:26:47.364 compiled with libxml2 version: 2.9.10
26-Oct-2023 16:26:47.364 linked to libxml2 version: 20910
26-Oct-2023 16:26:47.364 compiled with json-c version: 0.13.1
26-Oct-2023 16:26:47.364 linked to json-c version: 0.13.1
26-Oct-2023 16:26:47.364 compiled with zlib version: 1.2.11
26-Oct-2023 16:26:47.364 linked to zlib version: 1.2.11
26-Oct-2023 16:26:47.364 ----------------------------------------------------
26-Oct-2023 16:26:47.364 BIND 9 is maintained by Internet Systems Consortium,
26-Oct-2023 16:26:47.364 Inc. (ISC), a non-profit 501(c)(3) public-benefit
26-Oct-2023 16:26:47.364 corporation. Support and training for BIND 9 are
26-Oct-2023 16:26:47.364 available at https://www.isc.org/support
26-Oct-2023 16:26:47.364 ----------------------------------------------------
26-Oct-2023 16:26:47.364 found 40 CPUs, using 40 worker threads
26-Oct-2023 16:26:47.364 using 40 UDP listeners per interface
26-Oct-2023 16:26:47.632 using up to 524288 sockets
26-Oct-2023 16:26:47.636 loading configuration from '/var/snap/maas/31022/bind/named.conf'
26-Oct-2023 16:26:47.640 /var/snap/maas/current/bind/named.conf.maas:348: zone '56.33.10.in-addr.arpa': already exists previous definition: /var/snap/maas/current/bind/named.conf.maas:328
26-Oct-2023 16:26:47.644 loading configuration: failure
26-Oct-2023 16:26:47.644 exiting (due to fatal error)
^C
[Steps to reproduce]
1. Add subnet 10.33.56.0/24 to MAAS
Observe named logs and MAAS status goes unhealthy
[Additional note]
- Deleting resolves the issue, but prevents configuration of nodes
- Readding the subnet causes the issue to arise again
[Workaround]
None at the time of writing
SOS, Subnet info and named.log included here: https://drive.google.com/file/d/1h10ko79IoQfFKEki6pR0eL2tFd6PMevC/view
Thank you,
Peter |
Hello,
When adding the subnet 10.33.56.0/24 to my maas installation named starts to crash and this in turn breaks commissioning & deployment
Named logs show the following:
tf=no' '--enable-ipv6' '--enable-rrl' '--enable-filter-aaaa' '--disable-native-pkcs11' '--disable-isc-spnego' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/bind9-TyRg0u/bind9-9.16.1=. -fstack-protector-strong
-Wformat -Werror=format-security -fno-strict-aliasing -fno-delete-null-pointer-checks -DNO_VERSION_DATE -DDIG_SIGCHASE' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
26-Oct-2023 16:26:47.364 running as: named -c /var/snap/maas/31022/bind/named.conf -S 524288 -g
26-Oct-2023 16:26:47.364 compiled by GCC 9.4.0
26-Oct-2023 16:26:47.364 compiled with OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
26-Oct-2023 16:26:47.364 linked to OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
26-Oct-2023 16:26:47.364 compiled with libxml2 version: 2.9.10
26-Oct-2023 16:26:47.364 linked to libxml2 version: 20910
26-Oct-2023 16:26:47.364 compiled with json-c version: 0.13.1
26-Oct-2023 16:26:47.364 linked to json-c version: 0.13.1
26-Oct-2023 16:26:47.364 compiled with zlib version: 1.2.11
26-Oct-2023 16:26:47.364 linked to zlib version: 1.2.11
26-Oct-2023 16:26:47.364 ----------------------------------------------------
26-Oct-2023 16:26:47.364 BIND 9 is maintained by Internet Systems Consortium,
26-Oct-2023 16:26:47.364 Inc. (ISC), a non-profit 501(c)(3) public-benefit
26-Oct-2023 16:26:47.364 corporation. Support and training for BIND 9 are
26-Oct-2023 16:26:47.364 available at https://www.isc.org/support
26-Oct-2023 16:26:47.364 ----------------------------------------------------
26-Oct-2023 16:26:47.364 found 40 CPUs, using 40 worker threads
26-Oct-2023 16:26:47.364 using 40 UDP listeners per interface
26-Oct-2023 16:26:47.632 using up to 524288 sockets
26-Oct-2023 16:26:47.636 loading configuration from '/var/snap/maas/31022/bind/named.conf'
26-Oct-2023 16:26:47.640 /var/snap/maas/current/bind/named.conf.maas:348: zone '56.33.10.in-addr.arpa': already exists previous definition: /var/snap/maas/current/bind/named.conf.maas:328
26-Oct-2023 16:26:47.644 loading configuration: failure
26-Oct-2023 16:26:47.644 exiting (due to fatal error)
^C
[Steps to reproduce]
1. Add subnet 10.33.56.0/24 to MAAS
Observe named logs and MAAS status goes unhealthy
[Additional note]
- Deleting resolves the issue, but prevents configuration of nodes
- Readding the subnet causes the issue to arise again
[Workaround]
Re-add subnet disabling rdns. e.g. maas bego-root subnets create cidr='10.33.56.0/24' name='prod-net-6' rdns_mode=0.
SOS, Subnet info and named.log included here: https://drive.google.com/file/d/1h10ko79IoQfFKEki6pR0eL2tFd6PMevC/view
Thank you,
Peter |
|
