Is this reproducible on any newer Ubuntu releases?
** Changed in: sssd (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got killed d
Xenial is in ESM state right now, and as such there are no immediate
plans to fix this bug in it.
** Changed in: sssd (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I've just dup'ed another new case onto this, maybe this will revive the
old case.
@KK if you happened to have found a solution/root-cause and thereby
didn't come back here this is the chance to update the case :-)
And while touching the case I just wanted to re-state that various problems in
thi
Thank you so much Rafael. Will try and update you. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got killed due to segfault in ubuntu 16.04
To manage notifications about
Unfortunately looks like the crash file does not contain a valid dump...
(gdb) bt
#0 __GI_raise (sig=7551) at ../sysdeps/unix/sysv/linux/raise.c:37
#1 0x7f63fb16d02a in __GI_abort () at abort.c:87
#2 0x023953f0 in ?? ()
#3 0x0239bd80 in ?? ()
#4 0x0001 in ?? ()
Oops, forgot to ask you to install "valgrind" before running it.. in
comment #11, but I think by now you already got that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got kill
For the record only.. in between 1.13.4 and 1.14.2 (next version after
xenial) we have:
2dcf7b9 NSS: Fix NSS responder to cope with fully-qualified usernames
1510d12 test_ipa_subdom_server: Workaround for slow krb5 + SELinux
c19374b cache_req tests: use leak check in test fixtures
2dd75ea TOOLS: F
** Also affects: sssd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: sssd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Attaching the file generated in /var/crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got killed due to segfault in ubuntu 16.04
To manage notifications about this bug go to
Attached the file generated in /var/crash when the sssd dead.
** Attachment added: "_usr_sbin_sssd.0.crash"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1883614/+attachment/5399605/+files/_usr_sbin_sssd.0.crash
--
You received this bug notification because you are a member of Ubuntu
B
Again the sssd got crashed, not seeing any issue with the machine,System
resources were/are free …less than 30% utilized…
Aug 7 10:06:12 gamma14 sssd: Killing service [myOrg], not responding to pings!
Aug 7 10:06:22 gamma14 systemd[1]: sssd.service: Main process exited,
code=dumped, status=6/AB
Unfortunately we cannot guide you through a fix nor a workaround because
we are not able to reproduce the bug. If by any mean you provide a core
dump as Sergio mentioned (or better: a step by step on how to reproduce
it) you can come back to this bug and we will be happy to investigate
this crash.
HI Sergio,
There is no core dump, nor I am not aware I can do that. Is there any
way you suggest to fix the sssd getting killed multiple times on
multiple servers running this Ubuntu version 16.04(4.4.0-178-generic).
Can you please guide with steps if you are aware to fix this sssd thing
and the f
Thank you, KK.
It is unfortunate that we are not able to reproduce the bug here. Would
you happen to have the coredump file that was generated by the crash?
That would help us a lot. If you don't have the coredump nor steps to
reproduce the bug, could you please make sure to attach a coredump wh
Are you able to identify anything that can trigger the crash?
- Nothing found except the segafult I found, no load, no OOM, no IO, etc. The
machine was really quiet at that time when crashed - most of the activity seems
to be after the event, which is likely the sssd restart.
Is anything else cr
Hi and thanks for this bug report. The segmentation fault is certainly
something that should not happen, but there isn't really enough
information here for a developer to begin working on it.
Are you able to identify anything that can trigger the crash?
Is anything else crashing in a similar way
Is anyone looking into this or I will close this one ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got killed due to segfault in ubuntu 16.04
To manage notifications about th
** Package changed: ubuntu => sssd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got killed due to segfault in ubuntu 16.04
To manage notifications about this bug go t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
19 matches
Mail list logo
