I disabled LDAP paging in sssd.conf and let the setup run for a while.
No crashes since.
It does worry me though, that some other application could crash the
server by using result paging.
On 18. 11. 2013 17:05, Rich Megginson wrote:
On 11/18/2013 07:01 AM, Mitja Mihelič wrote:
On 15. 11.
On 11/21/2013 02:23 AM, Mitja Mihelič wrote:
I disabled LDAP paging in sssd.conf and let the setup run for a while.
No crashes since.
It does worry me though, that some other application could crash the
server by using result paging.
I am worried too. Please file a ticket.
On 18. 11. 2013
On 11/18/2013 07:01 AM, Mitja Mihelič wrote:
On 15. 11. 2013 21:46, Rich Megginson wrote:
On 11/15/2013 02:58 AM, Mitja Mihelič wrote:
On 14. 11. 2013 22:08, Rich Megginson wrote:
On 11/14/2013 08:50 AM, Mitja Mihelič wrote:
One of the consumers has crashed again and I have attached the
On 15. 11. 2013 21:46, Rich Megginson wrote:
On 11/15/2013 02:58 AM, Mitja Mihelič wrote:
On 14. 11. 2013 22:08, Rich Megginson wrote:
On 11/14/2013 08:50 AM, Mitja Mihelič wrote:
One of the consumers has crashed again and I have attached the
stacktrace.
Four hous later it crashed again.
On 11/15/2013 02:58 AM, Mitja Mihelič wrote:
On 14. 11. 2013 22:08, Rich Megginson wrote:
On 11/14/2013 08:50 AM, Mitja Mihelič wrote:
One of the consumers has crashed again and I have attached the
stacktrace.
Four hous later it crashed again.
I do hope there is something in the
On 11/14/2013 08:50 AM, Mitja Mihelič wrote:
One of the consumers has crashed again and I have attached the stacktrace.
Four hous later it crashed again.
I do hope there is something in the stacktraces, so that something can
be done to prevent future crashes.
Unfortunately, not enough.
On 07/16/2013 04:49 PM, Rich Megginson wrote:
On 07/16/2013 01:23 AM, Mitja Mihelič wrote:
On 07/15/2013 05:28 PM, Rich Megginson wrote:
On 07/15/2013 02:57 AM, Mitja Mihelič wrote:
On 07/12/2013 05:55 PM, Rich Megginson wrote:
On 07/12/2013 08:22 AM, Mitja Mihelič wrote:
On 07/09/2013
On 07/17/2013 01:52 AM, Mitja Mihelič wrote:
On 07/16/2013 04:49 PM, Rich Megginson wrote:
On 07/16/2013 01:23 AM, Mitja Mihelič wrote:
On 07/15/2013 05:28 PM, Rich Megginson wrote:
On 07/15/2013 02:57 AM, Mitja Mihelič wrote:
On 07/12/2013 05:55 PM, Rich Megginson wrote:
On 07/12/2013
On 07/16/2013 01:23 AM, Mitja Mihelič wrote:
On 07/15/2013 05:28 PM, Rich Megginson wrote:
On 07/15/2013 02:57 AM, Mitja Mihelič wrote:
On 07/12/2013 05:55 PM, Rich Megginson wrote:
On 07/12/2013 08:22 AM, Mitja Mihelič wrote:
On 07/09/2013 03:34 PM, Rich Megginson wrote:
On 07/09/2013
On 07/12/2013 05:55 PM, Rich Megginson wrote:
On 07/12/2013 08:22 AM, Mitja Mihelič wrote:
On 07/09/2013 03:34 PM, Rich Megginson wrote:
On 07/09/2013 06:43 AM, Mitja Mihelič wrote:
Hi!
We are having problems with some our 389-DS instances. They crash
after receiving an update from the
On 07/15/2013 02:57 AM, Mitja Mihelič wrote:
On 07/12/2013 05:55 PM, Rich Megginson wrote:
On 07/12/2013 08:22 AM, Mitja Mihelič wrote:
On 07/09/2013 03:34 PM, Rich Megginson wrote:
On 07/09/2013 06:43 AM, Mitja Mihelič wrote:
Hi!
We are having problems with some our 389-DS instances. They
On 07/12/2013 08:22 AM, Mitja Mihelič wrote:
On 07/09/2013 03:34 PM, Rich Megginson wrote:
On 07/09/2013 06:43 AM, Mitja Mihelič wrote:
Hi!
We are having problems with some our 389-DS instances. They crash
after receiving an update from the provider.
After looking at the stack trace, I
On 07/09/2013 06:43 AM, Mitja Mihelič wrote:
Hi!
We are having problems with some our 389-DS instances. They crash
after receiving an update from the provider.
After looking at the stack trace, I think this is
https://fedorahosted.org/389/ticket/47391
The crash happened twice after about
13 matches
Mail list logo
