[Expired for sssd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: sssd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889196
Hi Nathan,
Thanks for commenting here then.
Could you provide more details on the issue? What Ubuntu series are you
installing it in? Are those clean installations? Does that happen with
specific configuration in place?
** Changed in: sssd (Ubuntu)
Status: Expired => Incomplete
--
You
I have been able to reproduce this issue twice by installing fuse (sudo
apt install fuse) and then rebooting. The system is then permanently
stuck in an unbootable state with the aforementioned errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[Expired for sssd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: sssd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889196
Hi,
I think that part of the comments here are actually related to LP:
#1900642, which is now fixed in groovy-updates and hirsute. However
initial bug description from Ian Collier specifies that this bug report
is about the case where a valid sssd.conf exists, but sssd fails to
start due to a
I experience the infinite loop on boot about half the time. The OP
speaks of "misconfiguration because of user error", yet I'm not the type
to twittle with the system when it's not broken, so I'm not sure how
this misconfiguration happened.
Does anyone know of a workaround?
When the machine does
Same here with Groovy Gorilla (20.10), with all the latest
bells'n'whistles. On boot-up, I get multiple failures on SSSD services,
'sudo systemctl restart sssd' doesn't help either, 'journalctl -xe'
says:
-
░░ A start job for unit sssd-nss.socket has finished with a
Wow at least I wasn't doing anything on a production machine. Been a
while since something as catastrophic as not being able to login has
affected one of my machines. In fact all I think I did was "realm leave"
which produced no errors. I rebooted to a borked machine. Awesome.
--
You received
I can confirm this bug for me on 20.04 and confirm an infinite loop.
Even if sssd service is not working it should be skipped and at least
local users should be able to login!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is it really an "infinite" loop? Afaik this is caused by "Restart=on-
failure" in the [Service] section of sssd.service, and systemd will
eventually backoff and give up on the restarts.
Alternatively, I wonder if it's an effect of the socket activation. nss
calls on the system keep waking up the
Ian, can you try disabling the sockets? Something like "systemctl
disable sssd-nss.socket sssd-pam.socket" and so on for all *.socket
services, leave just "sssd.service" (note .service) enabled, and add
"services = nss,pam" to /etc/sssd/sssd.conf in the global section? That
will tell sssd to start
I have the same problem in Groovy Gorrillaa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889196
Title:
infinite loop on start if misconfigured
To manage notifications about this bug go to:
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix
** Also affects: sssd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Focal)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
** Changed in: sssd
14 matches
Mail list logo
