** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Changed in: sssd (Ubuntu Eoan)
Importance: Undecided => High
--
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/1723350
Title:
sssd offline on boot, stays offline forever
To manage
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
+ [Impact]
+ sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
+
+ In ubuntu that file is a
** Changed in: sssd (Ubuntu Eoan)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu Eoan)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Just tested and eoan is affected, focal is clear.
** Also affects: sssd (Ubuntu Eoan)
Importance: Undecided
Status: New
--
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/1723350
Ok, I have a simple way to reproduce this, and was able to test the
upstream patch. I'll polish it up and put it up for review, then prepare
the SRU paperwork.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Changed in: sssd (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
This is still on my list, I'm just very busy with focal fossa right now,
but the feature freeze is past, and now I can concentrate on only fixing
bugs.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I'll get to it. Being able to test the fix would help a lot, since I
never got it reproduced locally.
--
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/1723350
Title:
sssd offline on boot,
** Tags added: server-next
--
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/1723350
Title:
sssd offline on boot, stays offline forever
To manage notifications about this bug go to:
I agree. Do you have a way to reproduce this somewhat reliably?
** Changed in: sssd (Ubuntu Bionic)
Importance: Undecided => High
--
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/1723350
A PR which might address this was posted to the sssd mailing list:
https://github.com/SSSD/sssd/pull/864
--
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/1723350
Title:
sssd offline on boot,
Sorry, "fix released" is for the current development of Ubuntu which is
18.10. I'll add a task for bionic, and remove the artful one.
** Also affects: sssd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You
Interesting, I setup a watch on a directory to see what happens when a
symlink is changed:
https://pastebin.ubuntu.com/p/wKpMVY4dVz/
The watch on the "old" symlink definitely is lost via that operation, as
far as I can see.
--
You received this bug notification because you are a member of
The sssd.conf manpage from sssd 1.13.4 and 1.16.1 (xenial and bionic)
says that without inotify sssd will fall back to polling resolv.conf
every 5s:
try_inotify (boolean)
SSSD monitors the state of resolv.conf to identify when it needs to update
its internal DNS resolver. By default, we will
The inotify callback would log this:
DEBUG(SSSDBG_TRACE_INTERNAL,
"Received inotify notification for %s\n", filename);
That is level 8 debugging:
./src/util/debug.h:#define SSSDBG_TRACE_INTERNAL 0x2000 /* level 8 */
--
You received this bug notification because you are a
Maybe start with 6. From
https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html:
"""
To enable debugging persistently across SSSD service restarts, put the
directive debug_level=N, where N typically stands for a number between 1 and 10
into the particular section. Levels up to 3 should
The workaround you speak of, is that the sssd option to cache
credentials, or the systemd unit file change to require network-
online.target?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
@renbag could you please:
- add debug_level = 4 to [sssd] and your [domain/] sections
- reboot
- post the output of these commands right after:
systemd-analyze blame
systemd-analyze critical-chain
- login as a kerberos/ldap user, which has been failing
- check the new logs in /var/log/sssd/*
I'll mark this as fix released for bionic then, and open up an artful
task.
** Also affects: sssd (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu)
Status: Incomplete => Fix Released
** Summary changed:
- sssd offline on boot, stays offline forever
@renbag, can you share your network configuration on this artful
machine? These files:
/etc/network/interfaces
/etc/network/interfaces.d/*
/etc/netplan/*.yaml
And is this a desktop or a server?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed
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
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
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.
** Changed in: sssd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1723350
I can confirm this is happening after a reboot, and that a simple USR2
signal fixes it, but I wonder why sssd doesn't get itself back into
online mode on its own in this case.
For example, I tried the following:
- login via kerberos using pam_sss while it was online
- got my ticket
- kdestroy,
33 matches
Mail list logo
