On (12/09/16 21:47), Lachlan Musicman wrote:
>SELinux is disabled, updated to 1.14.1 today.
>
>This is the first crash in weeks, so we aren't that phased, although we'd
>love to know it wont happen again
BTW Did it really crashed? Do you have a coredump
We fixed few bad bugs(regressions) in
SELinux is disabled, updated to 1.14.1 today.
This is the first crash in weeks, so we aren't that phased, although we'd
love to know it wont happen again - the servers are part of a cluster that
executes automated tasks as the data comes off genome sequencing machines -
clinical medical analyses
On (12/09/16 11:09), Lachlan Musicman wrote:
>We saw another sssd crash on the weekend (well, Friday night).
>
>Centos 7, sssd 1.14.0 from COPR
>
Please upgrade to 1.14.1 from copr.
>Everything has worked fine for over a month until Friday.
>
>According to the log sssd_nss on the host in
On Mon, Sep 12, 2016 at 11:09:05AM +1000, Lachlan Musicman wrote:
> (Fri Sep 9 20:41:13 2016) [sssd[nss]] [sbus_client_init] (0x0020):
> check_file failed for [/var/lib/sss/pipes/private/
> sbus-dp_unix.petermac.org.au].
It looks like the domain process died and never recovered. What is in
We saw another sssd crash on the weekend (well, Friday night).
Centos 7, sssd 1.14.0 from COPR
Everything has worked fine for over a month until Friday.
According to the log sssd_nss on the host in question:
- at about 16:18, watchdog_handler killed a process for a timer overflow.
- there is
