The test in comment #4 is more thorough, as it checks that sssd can
detect that the network is up again on its own. Can you try that on
bionic please?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I'll mark the sssd task as invalid, since the software is working as
intended.
I added a release notes task to record what we did, and marked it as fix
released since the change is live already.
Thanks again for reporting this bug and helping make ubuntu better!
** Also affects:
** Changed in: postfix (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications
Agreed, and I can still reproduce this in bionic with postfix 3.3.0-1:
ubuntu@bionic-postfix:~$ postconf virtual_alias_map
Segmentation fault (core dumped)
ubuntu@bionic-postfix:~$ dpkg-query -W postfix
postfix 3.3.0-1
ubuntu@bionic-postfix:~$ ll /etc/postfix/valiases.cf
-rw-r- 1 root root
The crash happens in vstream_fileno(fp), because fp is a null pointer:
if ((fp = vstream_fopen(cf_file, O_RDONLY, 0)) == 0
&& errno != EACCES) {
msg_warn("open \"%s\" configuration \"%s\": %m",
dp->db_type, cf_file);
I think not, that's normal for the first kinit if the client doesn't
know that the server requires preauth. It will just adapt and request it
again.
You may have to bump the logging level, although the manpage doesn't
mention this (search for ad_gpo_access_control in
Thanks Scott, I did email postfix-users with subject "NULL pointer deref
in pcf_check_dbms_client() with unreadable map file", but I'm not
subscribed. Checking the archive at https://marc.info/?l=postfix-
users=1=201805=2 doesn't show my message, so I guess I should
subscribe. Or perhaps it's just
I also tried again in bionic, including rebooting the sssd client while
the krb5 server was offline, and it automatically switched back to an
online status after i restored the network on my krb5 server. I then
tried this again on xenial, and there it also worked.
let me try artful now.
--
You
Reading what I wrote in comment #4, seems like I'm contradicting myself.
First I say I can reproduce the problem, but later I say that after I
bring the network back up it starts working again on its own. That's
exactly what I'm seeing now, i.e., no bug. Tried xenial, artful and
bionic. Are you
** Changed in: logwatch (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: logwatch (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
And this is new in 3.3.0. I was also looking for some git/svn/bzr/cvs
repository to check the history of these changes, but couldn't find it.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Confirmed still happening in 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/1644057
Title:
Excessive Disconnect unmatched entries from sshd
To manage notifications about this bug
It should probably also check for 127.0.0.53, not just 127.0.0.1
** Also affects: avahi (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898038
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server, which
With the new packages and in "permissive" mode, you should be getting
log messages about why a certain user would have been denied access.
These might land in /var/log/syslog, or perhaps an sssd specific logfile
in /var/log/sssd/*. Could you please check?
--
You received this bug notification
Leaving ubuntu-server subscribed so it stays in the queue
** Changed in: samba (Ubuntu)
Importance: Undecided => Critical
** Changed in: samba (Ubuntu)
Importance: Critical => Medium
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Is https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1668244
still an issue with this update? The udev rules look different
--
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/1741390
16 matches
Mail list logo
