[Bug 1796164] Re: After interface/IP changes, bind9 can fail to respond to queries on the new interface
Is MAAS using netplan to add the new interface? I was trying to reproduce this without MAAS, but it worked just fine. I fear that maybe netplan is triggering something else that MAAS by itself isn't, and that made it work. Here is what I did. New VM, with just one nick, configured via netplan to have a static ip. Install and configure bind9. Query a machine outside the local zones (this is the first change from what you did). I have a forwarder configured to another dns server in my local network, and I queried the local vm bind9 server for a name managed by the external dns. This worked. Then I added a new NIC to the VM (via virt-manager). Added this snipped to the netplan yaml: ens9: dhcp4: false addresses: - 10.0.7.10/24 Ran netplan generate. No errors. Ran netplan apply. No errors. This shows up in the syslog logs: Oct 8 18:36:39 cosmic-bind9-add-nic systemd[1]: Stopping Network Service... Oct 8 18:36:39 cosmic-bind9-add-nic systemd[1]: Stopped Network Service. Oct 8 18:36:39 cosmic-bind9-add-nic systemd[1]: Starting Network Service... Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: ens9: Gained IPv6LL Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: ens3: Gained IPv6LL Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: Enumeration completed Oct 8 18:36:39 cosmic-bind9-add-nic systemd[1]: Started Network Service. Oct 8 18:36:39 cosmic-bind9-add-nic named[1145]: no longer listening on 10.0.7.10#53 Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: ens3: Link is not managed by us Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: lo: Link is not managed by us Oct 8 18:36:39 cosmic-bind9-add-nic named[1145]: listening on IPv4 interface ens9, 10.0.7.10#53 Oct 8 18:36:39 cosmic-bind9-add-nic named[1145]: no longer listening on 192.168.122.12#53 Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: lo: Link is not managed by us Oct 8 18:36:39 cosmic-bind9-add-nic named[1145]: listening on IPv4 interface ens3, 192.168.122.12#53 Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: ens9: Configured Oct 8 18:36:39 cosmic-bind9-add-nic systemd-networkd[1295]: ens3: Configured We can see that named reacts to the interface changes. I *think* there was no bind9 restart/reload involved. "journalctl -u bind9 --follow" for the same "netplan apply" event shows just this: Oct 08 18:40:36 cosmic-bind9-add-nic named[1145]: no longer listening on 10.0.7.10#53 Oct 08 18:40:36 cosmic-bind9-add-nic named[1145]: listening on IPv4 interface ens9, 10.0.7.10#53 Oct 08 18:40:36 cosmic-bind9-add-nic named[1145]: no longer listening on 192.168.122.12#53 Oct 08 18:40:36 cosmic-bind9-add-nic named[1145]: listening on IPv4 interface ens3, 192.168.122.12#53 A query on the new 10.0.7.10 IP for the name I queried before adding the hew nic works, using "dig @10.0.7.10 ds216.lowtech". This was on cosmic, using bind9 1:9.11.4+dfsg-3ubuntu5. I'll retry on bionic, which is one minor behind, and then with actual maas. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1796164 Title: After interface/IP changes, bind9 can fail to respond to queries on the new interface To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1796164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1796164] Re: After interface/IP changes, bind9 can fail to respond to queries on the new interface
Taking a look. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1796164 Title: After interface/IP changes, bind9 can fail to respond to queries on the new interface To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1796164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1689833] Re: OpenVPN server does not start properly on boot
@jnx, the 192.168.11.254 address you are trying to bind to, is that the normal nic of that machine? Or something else, like a wifi interface, or something that would only come up after the user logs in, assuming this is a desktop? -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1689833 Title: OpenVPN server does not start properly on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1689833/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1796569] Re: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
Thanks for filing this bug in Ubuntu. The mysql user is created by the mysql-server-5.7 package in its preinst script. The logs you attached unfortunately don't contain the details about what happened at that time, only that the user wasn't available when the postinst script came along (the failed chown call). Could you please try these commands, and paste their output here in the bug: sudo apt update sudo apt install --reinstall mysql-server-5.7 sudo apt -f install THanks ** Changed in: mysql-5.7 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-5.7 in Ubuntu. Matching subscriptions: main https://bugs.launchpad.net/bugs/1796569 Title: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1796569/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1786250] Re: strongswan (charon) is rejected by apparmor to read /proc//fd
@yicwang, did you update the apparmor profile as per this bug for your tests? The diff can be seen at https://code.launchpad.net/~ahasenack/ubuntu/+source/strongswan/+git/strongswan/+merge/356135. Make that change, then run this command: sudo apparmor_parser -r -T -W /etc/apparmor.d/usr.lib.ipsec.charon If that fixes the problem for you, and the apparmor DENIED messages about this disappear from the logs, then we can start an SRU for bionic. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1786250 Title: strongswan (charon) is rejected by apparmor to read /proc//fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1786250/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1794553] Re: assertion error when rotating logs
Upstream PR got some activity: https://github.com/squid- cache/squid/pull/257 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1794553 Title: assertion error when rotating logs To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1794553/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1794553] Re: squid crashed with SIGABRT in xassert()
Disabling the pinger also works around the problem: In /etc/squid/squid.conf: pinger_enable off ** Summary changed: - squid crashed with SIGABRT in xassert() + assertion error when rotating logs -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1794553 Title: assertion error when rotating logs To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1794553/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1793882] Re: sssd: Add DEP8 tests
For reference: https://salsa.debian.org/sssd-team/sssd/merge_requests/2 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to sssd in Ubuntu. https://bugs.launchpad.net/bugs/1793882 Title: sssd: Add DEP8 tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1793882/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
