** 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
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
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
*** 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
$
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
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
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
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-
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
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
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
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
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
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
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
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1543794
Title:
isc-dhcp-server fails to start on second &
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
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",
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
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
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
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}
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
** 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
** 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
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
*** 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
Server Team, which is
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
*** 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
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
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
30 matches
Mail list logo
