** Description changed:
- i've just upgraded to 15.10, and have now found that the
- /etc/defaults/bind9 file appears to be ignored. yet another package
- broken by the adoption of systemd, it would seem.
+ [Impact]
- >cat /etc/default/bind9
- # run resolvconf?
- RESOLVCONF=yes
+ Server
** Changed in: bind9 (Ubuntu Zesty)
Importance: Undecided => Low
** Changed in: bind9 (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: bind9 (Ubuntu Zesty)
Importance: Low => Medium
** Changed in: bind9 (Ubuntu Xenial)
Importance: Low => Medium
--
You received this bug
** Changed in: bind9 (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: bind9 (Ubuntu Zesty)
Status: New => In Progress
** Changed in: bind9 (Ubuntu Xenial)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: bind9 (Ubuntu Zesty)
Assignee:
Confirmed also for zesty. Artful and higher are fixed.
Yakkety is end of life.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1565060
Title:
defaults file is ignored
To manage
** Changed in: bind9 (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1565060
Title:
defaults file is ignored
To manage
@pam-s, as soon as you can confirm this patch fixes your problem (feel
free to use my PPA packages), please let us know so we can proceed with
the SRU.
My test case reproduces the segfault, but I would like to be sure it
also fixes it in your environment before continuing.
Thanks again
**
** Description changed:
[Impact]
+ In this particular configuration, when ldap_rfc2307_fallback_to_local_users
is set to true in /etc/sss/sssd.conf and a local user is a member of an ldap
group and does not exist in the directory (other scenarios are possible), the
sssd_be process segfaults
It's only xenial that is affected, that is, version 1.13.4 and perhaps
earlier. Trusty, zesty and higher are OK.
** Description changed:
- This is Ubuntu 16.04.2 LTS
+ [Impact]
- sssd is configured to connect to two domains, our TPAD directory and
- Active Directory. sssd starts up at boot
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
This PPA has my test packages:
https://launchpad.net/~ahasenack/+archive/ubuntu/sssd-bad-initgroups-
results-1684295/
--
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/1684295
Title:
I got a small reproducer case. With a simple "id " command I get
sssd_be to segfault, and with the above patch applied it no longer
segfaults and also produces the correct result. I'll use that for the
SRU test plan.
--
You received this bug notification because you are a member of Ubuntu
Server
Thanks for filing this bug in Ubuntu.
Unfortunately the attached logs only show that the smbd service indeed
failed to start, but do not tell us why.
Your config file looks fine.
Could you please attach all files from /var/log/samba/ that start with
"log"? That would be /var/log/samba/log*.
** Bug watch added: github.com/CanonicalLtd/ubuntu-advantage-script/issues #85
https://github.com/CanonicalLtd/ubuntu-advantage-script/issues/85
** Also affects: ubuntu-advantage-script via
https://github.com/CanonicalLtd/ubuntu-advantage-script/issues/85
Importance: Unknown
13 matches
Mail list logo
