[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)
I tried the vagrant file a try, and this is the last bit of output: (...) default: Created symlink /etc/systemd/system/multi-user.target.wants/bind9.service → /lib/systemd/system/bind9.service. default: bind9-pkcs11.service is a disabled or a static unit, not starting it. default: bind9-resolvconf.service is a disabled or a static unit, not starting it. default: Processing triggers for ureadahead (0.100.0-20) ... default: Processing triggers for systemd (237-3ubuntu10.3) ... default: Processing triggers for ufw (0.35-5) ... default: Fails to look up host with dnssec-validation auto default: Server:192.168.0.130 default: Address: 192.168.0.130#53 default: default: Non-authoritative answer: default: Name: ubuntu.com default: Address: 91.189.94.40 default: Fails to get entire entry with dnssec-validation false default: Server:192.168.0.130 default: Address: 192.168.0.130#53 default: default: Non-authoritative answer: default: Name: ubuntu.com default: Address: 91.189.94.40 I don't see errors from nslookup. I tried this on a cosmic laptop, with vagrant and virtualbox as shipped in cosmic, but the VM was bionic as specified. It only has a wifi connection, so I gave it the wifi nic name when vagrant asked me which interface it should bridge with (if that matters). Perhaps you should do a network packet capture, see if packets are being truncated somehow. If using tcpdump, be sure to specify a large size with -s, or just "-s 0" which means the whole packet iirc. And then compare it with another packet capture with the previous version of bind to see what's the difference. A tcpdump command line to start with could be: tcpdump -i any -s 0 -w dns.pcap port 53 You could perhaps restrict the interface a bit, instead of "any". -- 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/1787739 Title: postfix name lookup failed after dist-upgrade (Aug-2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1787739/+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 1796142] Re: browsing samba share got NT_STATUS_IO_TIMEOUT only on specific subfolder inside share
Sorry, a better url for the samba users mailing list is https://lists.samba.org/mailman/listinfo/samba -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1796142 Title: browsing samba share got NT_STATUS_IO_TIMEOUT only on specific subfolder inside share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1796142/+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 1796142] Re: browsing samba share got NT_STATUS_IO_TIMEOUT only on specific subfolder inside share
Thanks for filing this bug in Ubuntu. You seem to be hitting a performance issue, on a non-trivial setup. This is too broad for a bug report. I suggest you seek help in the samba mailing list at https://lists.samba.org/archive/samba/. In the meantime, I'll mark this bug as incomplete. ** Changed in: samba (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1796142 Title: browsing samba share got NT_STATUS_IO_TIMEOUT only on specific subfolder inside share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1796142/+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 1718350] Re: package postgresql-common 173 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Thanks for filing this bug in Ubuntu. You seem to have a non-ubuntu package installed that is causing problems: insserv: There is a loop between service OpManagerServer and udev if started In particular: insserv: warning: script 'S98OpManagerServer' missing LSB tags and overrides insserv: warning: script 'OpManagerServer' missing LSB tags and overrides You should contact whoever provided OpManagerServer and have them fix the LSB headers of its SysV initscript. Alternatively, you could temporarily remove it from your system, proceed with the removal of postgresql as you intended, and then reinstall it. ** Changed in: postgresql-common (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1718350 Title: package postgresql-common 173 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1718350/+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 1797933] Re: psql requires '-h localhost' to run basic commands
Where did you get this postgresql package from? 10.5-1.pgdg14.04+1 doesn't look like it's something released by ubuntu. Is this a trusty machine? ** Changed in: postgresql-common (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1797933 Title: psql requires '-h localhost' to run basic commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1797933/+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 1797979] Re: [ppc64el] multipath install fails with bad UUID root= setting
Is this reproduceable in a ppc64el vm by using the mini.iso to perform an installation? Can you detail what type of installation, disk layout, etc? When does multipath come into play? -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1797979 Title: [ppc64el] multipath install fails with bad UUID root= setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1797979/+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 1797836] Re: logwatch reports false kernel error warning
Thanks for filing this bug in Ubuntu. I've seen this warning too. ** Changed in: logwatch (Ubuntu) Status: New => Triaged ** Changed in: logwatch (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1797836 Title: logwatch reports false kernel error warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1797836/+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
