[Bug 1752651] Re: Salt 'debconf' states fail since move to Python 3
** Bug watch added: github.com/saltstack/salt/issues #46299 https://github.com/saltstack/salt/issues/46299 ** Also affects: salt via https://github.com/saltstack/salt/issues/46299 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752651 Title: Salt 'debconf' states fail since move to Python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/salt/+bug/1752651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752651] [NEW] Salt 'debconf' states fail since move to Python 3
Public bug reported: Since the move to salt running under Python 3, salt 'debconf' states fail with: ``` [ERROR ] An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/state.py", line 1851, in call **cdata['kwargs']) File "/usr/lib/python3/dist-packages/salt/loader.py", line 1795, in wrapper return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/states/debconfmod.py", line 197, in set if __salt__['debconf.set'](name, key, args['type'], args['value']): File "/usr/lib/python3/dist-packages/salt/modules/debconfmod.py", line 130, in set_ os.write(fd_, line) TypeError: a bytes-like object is required, not 'str' ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: salt-minion 2017.7.3+dfsg1-1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Thu Mar 1 16:42:41 2018 JournalErrors: -- Logs begin at Mon 2018-01-29 14:53:26 GMT, end at Thu 2018-03-01 16:42:31 GMT. -- Mar 01 16:38:24 hostname kernel: piix4_smbus :00:07.3: SMBus Host Controller not enabled! Mar 01 16:38:24 hostname kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: salt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: salt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752651 Title: Salt 'debconf' states fail since move to Python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1752651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750553] [NEW] Salt error 'Failed to import states pip_state' since move to python 3
Public bug reported: Since the move to salt running under Python 3, salt 'pip' states fail with: ``` 2018-02-20 11:11:29,176 [salt.loader ][ERROR ][13011] Failed to import states pip_state, this is due most likely to a syntax error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/loader.py", line 1405, in _load_module mod = spec.loader.load_module() File "", line 399, in _check_name_wrapper File "", line 823, in load_module File "", line 682, in load_module File "", line 265, in _load_module_shim File "", line 696, in _load File "", line 677, in _load_unlocked File "", line 678, in exec_module File "", line 219, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/salt/states/pip_state.py", line 36, in import pip File "/usr/lib/python3/dist-packages/pip/__init__.py", line 26, in from pip.utils import get_installed_distributions, get_prog File "/usr/lib/python3/dist-packages/pip/utils/__init__.py", line 23, in from pip.locations import ( File "/usr/lib/python3/dist-packages/pip/locations.py", line 103, in bin_user = os.path.join(user_site, 'bin') File "/usr/lib/python3.6/posixpath.py", line 80, in join a = os.fspath(a) TypeError: expected str, bytes or os.PathLike object, not NoneType ``` This has been noted upstream in salt: https://github.com/saltstack/salt/issues/44980 ...which reports that it is an issue with pip: https://github.com/pypa/pip/pull/4442 However no release of pip has been made that contains this fix. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: salt-minion 2017.7.2+dfsg1-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Tue Feb 20 11:29:41 2018 JournalErrors: -- Logs begin at Mon 2018-01-29 17:20:48 GMT, end at Tue 2018-02-20 11:29:14 GMT. -- Feb 20 11:22:14 hostname kernel: piix4_smbus :00:07.3: SMBus Host Controller not enabled! Feb 20 11:22:14 hostname kernel: sd 3:0:0:0: [sda] Assuming drive cache: write through PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: salt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Affects: salt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Also affects: python-pip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750553 Title: Salt error 'Failed to import states pip_state' since move to python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1750553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586381] Re: Pip states report "AttributeError: 'Requirement' object has no attribute 'project_name'" since python-pip (8.1.1-2ubuntu0.1)
*** This bug is a duplicate of bug 1626258 *** https://bugs.launchpad.net/bugs/1626258 I do not believe this is a duplicate of bug #1626258 as I continue to experience the reported issue with salt: ``` python-pip: Installed: 8.1.1-2ubuntu0.4 salt-minion: Installed: 2015.8.8+ds-1 $ salt-call state.highstate [...] Function: pip.installed Result: False Comment: An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/salt/state.py", line 1626, in call **cdata['kwargs']) File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 1492, in wrapper return f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/salt/states/pip_state.py", line 592, in installed out = _check_pkg_version_format(pkg) File "/usr/lib/python2.7/dist-packages/salt/states/pip_state.py", line 176, in _check_pkg_version_format ret['prefix'] = install_req.req.project_name AttributeError: 'Requirement' object has no attribute 'project_name' ``` The patch for bug #1626258 does not return pip to supplying 'project_name', rather it fixes up other parts of pip which expect (as salt does) 'project_name', and it does so by referencing 'name'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586381 Title: Pip states report "AttributeError: 'Requirement' object has no attribute 'project_name'" since python-pip (8.1.1-2ubuntu0.1) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1586381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1601848] [NEW] Fails to start when python-path contains multiple path components separated by a colon
Public bug reported: Given a configuration of: WSGIDaemonProcess X user=user group=group threads=10 python path=/opt/redirect:/opt/landing:/opt/admin apache's error log contains: [Mon Jul 11 15:48:45.005148 2016] [mpm_event:notice] [pid 1654:tid 140660516243328] AH00489: Apache/2.4.18 (Ubuntu) mod_wsgi/4.3.0 Python/3.5.1+ configured -- resuming normal operations [Mon Jul 11 15:48:45.005423 2016] [core:notice] [pid 1654:tid 140660516243328] AH00094: Command line: '/usr/sbin/apache2' [Mon Jul 11 15:48:45.082878 2016] [wsgi:error] [pid 1657:tid 140660516243328] mod_wsgi (pid=1657): Call to 'site.addsitedir()' failed for '(null)', stopping. [Mon Jul 11 15:48:45.083149 2016] [wsgi:error] [pid 1657:tid 140660516243328] mod_wsgi (pid=1657): Call to 'site.addsitedir()' failed for '/opt/landing:/opt/admin'. This is a known issue and has been fixed upstream: https://github.com/GrahamDumpleton/mod_wsgi/commit/1abae882b904a39de6756f18a94363676208c3ff This is a regression from 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libapache2-mod-wsgi-py3 4.3.0-1.1build1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Jul 11 15:50:14 2016 SourcePackage: mod-wsgi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mod-wsgi (Ubuntu) Importance: Undecided Status: New ** Affects: mod-wsgi (Debian) Importance: Unknown Status: Unknown ** Affects: fedora Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug xenial ** Bug watch added: Debian Bug tracker #811077 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811077 ** Also affects: mod-wsgi (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811077 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1345725 https://bugzilla.redhat.com/show_bug.cgi?id=1345725 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1345725 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1601848 Title: Fails to start when python-path contains multiple path components separated by a colon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1601848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586381] Re: Pip states report "AttributeError: 'Requirement' object has no attribute 'project_name'" since python-pip (8.1.1-2ubuntu0.1)
Attached is a debian/patches version of salt pull #33180 (https://github.com/saltstack/salt/pull/33180/files) which corrects this issue ** Patch added: "salt-33180.patch" https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1586381/+attachment/4696851/+files/salt-33180.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586381 Title: Pip states report "AttributeError: 'Requirement' object has no attribute 'project_name'" since python-pip (8.1.1-2ubuntu0.1) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1586381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586381] [NEW] Pip states report "AttributeError: 'Requirement' object has no attribute 'project_name'" since python-pip (8.1.1-2ubuntu0.1)
Public bug reported: Pip changed an internal API, which was then cherry-picked into python- pip (8.1.1-2ubuntu0.1). Salt relies on this API for the 'pip' states, which now report: [ERROR ] An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/salt/state.py", line 1626, in call **cdata['kwargs']) File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 1492, in wrapper return f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/salt/states/pip_state.py", line 592, in installed out = _check_pkg_version_format(pkg) File "/usr/lib/python2.7/dist-packages/salt/states/pip_state.py", line 176, in _check_pkg_version_format ret['prefix'] = install_req.req.project_name AttributeError: 'Requirement' object has no attribute 'project_name' This has been reported (and patched) upstream: https://github.com/saltstack/salt/pull/33180 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: salt-minion 2015.8.8+ds-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri May 27 13:46:42 2016 JournalErrors: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. -- No entries -- PackageArchitecture: all SourcePackage: salt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: salt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586381 Title: Pip states report "AttributeError: 'Requirement' object has no attribute 'project_name'" since python-pip (8.1.1-2ubuntu0.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1586381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584077] [NEW] Backport 'prefetch' fix from 9.10.4
Public bug reported: There is a known performance issue with 'prefetch', which is enabled by default in 9.10: https://kb.isc.org/article/AA-01315/0/prefetch-performance-in- BIND-9.10.html The fix diff appears to be minimal: https://source.isc.org/cgi- bin/gitweb.cgi?p=bind9.git;a=commit;h=0526268c2b2806ceb67032e0bfee708b6e70e004 Would you consider including this as a patch in the 9.10.3 Xenial packages? ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584077 Title: Backport 'prefetch' fix from 9.10.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1584077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583537] [NEW] systemd shutdown writes non-error message to stderr - causes email to be sent despite 'MailOnlyOnError'
Public bug reported: Calling unattended-upgrade from cron with an Unattended-Upgrade ::Automatic-Reboot-Time of "+5". This causes unattended-upgrades to run: '/sbin/shutdown -r +5' Systemd's shutdown writes an acknowledgement message to stderr: Shutdown scheduled for Wed 2016-05-18 04:37:49 BST, use 'shutdown -c' to cancel. Which cron picks up and emails - but I don't really want to know. Is there any scope for unattended-upgrades to gobble shutdown's stderr message? Or, perhaps this should be logged against systemd, since the shutdown message isn't really an obvious candidate for stderr? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 19 11:14:14 2016 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583537 Title: systemd shutdown writes non-error message to stderr - causes email to be sent despite 'MailOnlyOnError' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1583537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555689] [NEW] Consider building bind 9.10 with --enable-fetchlimit
Public bug reported: BIND 9.10.3+ has additional tuning options for recursive servers that can be enabled at build time with --enable-fetchlimit. "These features are intended to optimize recursive server behavior in favor of good client queries, whilst at the same time limiting the impact of bad client queries (e.g. queries which cannot be resolved, or which take too long to resolve) on local recursive server resource use.". Please consider building the bind 9.10 packages with fetchlimit enabled. Further details are available in ISC's knowledge base: https://deepthought.isc.org/article/AA-01304/0/Recursive-Client-Rate- limiting-in-BIND-9.9.8-and-9.10.3.html ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555689 Title: Consider building bind 9.10 with --enable-fetchlimit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1555689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files
The original primary issue (that pid files were not being written at all) was resolved in isc-dhcp 4.3.3-5ubuntu9. However both isc-dhcp- server & isc-dhcp-server6 systemd units continue to use the same RuntimeDirectory, so that when either service is restarted (eg to reconfigure), the pid file of the other service is lost. ** Summary changed: - dhcpd can't write pidfile to /run/dhcp-server (and isc-dhcp-server & isc-dhcp-server6 both use the same RuntimeDirectory) + isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543799 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551855] Re: [xenial] systemctl hangs when stopping isc-dhcp-server
Bug #1549330 ("dhcpd 4.3.3-5ubuntu7 aborts after getting stuck on futex (bind 9.10 library interaction?)"), which has been marked a duplicate of bug #1551351 is reporting the same symptoms - dhcpd doesn't respond to SIGTERM and appears to be stuck on a futex. I think this is related to the switch from bind 9.9 export library to bind 9.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551855 Title: [xenial] systemctl hangs when stopping isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550983] [NEW] Fails to start with "Couldn't open libGL.so.1" (missing dependency?)
Public bug reported: virt-manager fails to start: $ virt-manager --debug --no-fork [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (cli:256) Launched with command line: /usr/share/virt-manager/virt-manager --debug --no-fork [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:143) virt-manager version: 1.3.2 [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:144) virtManager import: Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory $ Installing the 'libgl1-mesa-glx' package resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virt-manager 1:1.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sun Feb 28 19:19:27 2016 InstallationDate: Installed on 2016-02-27 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550983 Title: Fails to start with "Couldn't open libGL.so.1" (missing dependency?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1550983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543794] Re: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append'
isc-dhcp 4.3.3-5ubuntu8 appears to fix bug #1549736, but not this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543794 Title: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549330] [NEW] dhcpd 4.3.3-5ubuntu7 aborts after getting stuck on futex (bind 9.10 library interaction?)
Public bug reported: dhcpd no longer stops when sent a SIGTERM, but appears to lock up on a futex. Final few lines of strace: -- sendto(6, "<182>Feb 24 15:12:38 dhcpd[1414]"..., 58, MSG_NOSIGNAL, NULL, 0) = 58 write(2, "Server starting service.", 24Server starting service.) = 24 write(2, "\n", 1 ) = 1 futex(0x7fe51a9000bc, FUTEX_WAIT_PRIVATE, 1, NULL) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) --- SIGABRT {si_signo=SIGABRT, si_code=SI_USER, si_pid=1421, si_uid=0} --- +++ killed by SIGABRT (core dumped) +++ -- This may be related to the move from bind 9.9 to 9.10 (see, eg http://comments.gmane.org/gmane.network.dhcp.isc.dhcp-server/13689 where Fedora report being unable to build dhcpd against 9.10) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Feb 24 15:16:52 2016 ProcEnviron: LANGUAGE=en_GB: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-24T14:24:53.396201 upstart.isc-dhcp-server.override: manual ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549330 Title: dhcpd 4.3.3-5ubuntu7 aborts after getting stuck on futex (bind 9.10 library interaction?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1549330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543799] [NEW] dhcpd can't write pidfile to /run/dhcp-server (and isc-dhcp-server & isc-dhcp-server6 both use the same RuntimeDirectory)
Public bug reported: dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is found /run/dhcp-server. Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit files specify the RuntimeDirectory 'dhcp-server', which is removed when either unit stops (and thus would wipe out the other unit's pid file, were it being successfully written). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 21:34:08 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056 ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543799 Title: dhcpd can't write pidfile to /run/dhcp-server (and isc-dhcp-server & isc-dhcp-server6 both use the same RuntimeDirectory) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543794] [NEW] isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append'
Public bug reported: During the first start of isc-dhcp-server (using the systemd service unit), a blank dhcpd.leases file is created (presumably owned by root:root). dhcpd starts successfully (and then exits due to no subnet definitions, that's expected). Attempting to start the service again fails with 'Can't open /var/lib/dhcp/dhcpd.leases for append' (the dhcpd.leases file ownership is now dhcpd.dhcpd), and apparmor logs a denial of the dac_override capability. Removing the leases file repeats this process (first start works as expected, future ones do not). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 20:58:12 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543794 Title: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543657] [NEW] settle-dad.sh expects netmask to be provided, but netmask is not marked 'required'
Public bug reported: = Description:Ubuntu Xenial Xerus (development branch) Release:16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = For the inet6 static method, interfaces(5) implies that only 'address' is required (and thus netmask is optional), however settle-dad.sh assumes IF_NETMASK is being set. If only address is supplied, the following message is logged: Waiting for DAD... Error: inet6 prefix is expected rather than "2001:db8:ab:cd::12/" and settle-dad.sh returns immediately, before DAD has settled. 'ip address list' appears to ignore the netmask if it is supplied, so settle-dad could probably just use '[..] to "${IF_ADDRESS}"'. Alternatively, 'netmask' could be documented as 'required'. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543657 Title: settle-dad.sh expects netmask to be provided, but netmask is not marked 'required' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
Adding '-tentative' to the ip call in /lib/ifupdown/wait-for-ll6.sh corrects this issue for me: --- /lib/ifupdown/wait-for-ll6.sh.old 2016-02-08 23:58:02.341820711 + +++ /lib/ifupdown/wait-for-ll6.sh 2016-02-09 00:01:18.128000560 + @@ -4,7 +4,7 @@ delay=${IF_LL_INTERVAL:-0.1} for attempt in $(seq 1 $attempts); do - lladdress=$(ip -6 -o a s dev "$IFACE" scope link) + lladdress=$(ip -6 -o a s dev "$IFACE" scope link -tentative) if [ -n "$lladdress" ]; then attempt=0 break (-tentative is "only list addresses which are not in the process of duplicate address detection currently") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543352] [NEW] inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
Public bug reported: = Description:Ubuntu Xenial Xerus (development branch) Release:16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245604] Re: "killall -u snmp" in a pre-install step kills any running snmpd
** Bug watch added: Debian Bug tracker #781257 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781257 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781257 Importance: Unknown Status: Unknown ** Package changed: debian => net-snmp (Debian) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245604 Title: "killall -u snmp" in a pre-install step kills any running snmpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1245604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1395216] Re: NSEC3 validation fails for some wildcard records, in BIND pre-9.8.2b1 - consider updating 12.04LTS package
*** This bug is a duplicate of bug 1203976 *** https://bugs.launchpad.net/bugs/1203976 ** This bug has been marked a duplicate of bug 1203976 DNS wildcards fail to resolve with DNSsec enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1395216 Title: NSEC3 validation fails for some wildcard records, in BIND pre-9.8.2b1 - consider updating 12.04LTS package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1395216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1395216] [NEW] NSEC3 validation fails for some wildcard records, in BIND pre-9.8.2b1 - consider updating 12.04LTS package
Public bug reported: In some situations (a non-tiny zone size), BIND9.8 pre-9.8.2b1 fails to correctly validate NSEC3 records covering wildcard names. This is recorded in BIND's CHANGES: 3175. [bug] Fix how DNSSEC positive wildcard responses from a NSEC3 signed zone are validated. Stop sending a unnecessary NSEC3 record when generating such responses. [RT #26200] Ubuntu's stock configuration enables DNSSEC validation (this is good), but with 12.04 LTS being likely to be in production use for many more years, it would be helpful if this fix was back-ported. See https://lists.isc.org/pipermail/bind-users/2014-November/094191.html for a recent example of this problem. Note that 14.04LTS uses BIND 9.9 which already contains this fix. This bug report is to request a fix to 12.04LTS. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1395216 Title: NSEC3 validation fails for some wildcard records, in BIND pre-9.8.2b1 - consider updating 12.04LTS package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1395216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073498] Re: PPA version '1.8.5-0ubuntu0.1~precise1' will not start due to merge cruft in /etc/init/sssd.conf
Confirmation - 1.8.5-0ubuntu0.1~precise2 starts correctly. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073498 Title: PPA version '1.8.5-0ubuntu0.1~precise1' will not start due to merge cruft in /etc/init/sssd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1073498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073498] [NEW] PPA version '1.8.5-0ubuntu0.1~precise1' will not start due to merge cruft in /etc/init/sssd.conf
Public bug reported: This is regarding the PPA version given by the source line: deb http://ppa.launchpad.net/sssd/updates/ubuntu precise main # lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 # apt-cache policy sssd sssd: Installed: 1.8.5-0ubuntu0.1~precise1 Candidate: 1.8.5-0ubuntu0.1~precise1 Version table: *** 1.8.5-0ubuntu0.1~precise1 0 500 http://ppa.launchpad.net/sssd/updates/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 1.8.2-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages # After upgrading to version: 1.8.5-0ubuntu0.1~precise1, sssd can no longer be started: # start sssd start: Job failed to start # Syslog says: Oct 31 10:03:46 fa-sysmon kernel: [1625199.891605] init: sssd pre-start process (11031) terminated with status 2 /etc/init/sssd.conf appears to contain some merge cruft: pre-start script <<< HEAD test -f /etc/sssd/sssd.conf || { stop; exit 0; } === test -f /etc/sssd/sssd.conf || { stop; exit 0; } /lib/init/apparmor-profile-load usr.sbin.sssd >>> 580d1ab... sssd.upstart.in: Delete an invisible control character from >>> the pre-start script. (LP: #1003845) end script ** Affects: sssd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073498 Title: PPA version '1.8.5-0ubuntu0.1~precise1' will not start due to merge cruft in /etc/init/sssd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1073498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs