[389-users] Re: Crash logs

2016-01-28 Thread William Brown
> > > With "export NSS_DISABLE_HW_AES=1" there are no crashes. > > > > >  > Hello, > > the certificate is there (in the "-BEGIN CERTIFICATE-") > section, I just edited it. Here is the certificate without some > internal information like the DN: > Ahhh okay. I see what happened now.  >

[389-users] Re: Crash logs

2016-01-28 Thread Todor Petkov
On Thu, Jan 28, 2016 at 11:02 AM, William Brown wrote: > >> >> with "export NSS_DISABLE_HW_GCM=1", there are no crashes, with and >> without the cipher option. Moreover, with the cipher option it says: >> >> CONNECTED(0003) >> 139960478934944:error:14077410:SSL >> routines:SSL23_GET_SERVER_HEL

[389-users] Re: Crash logs

2016-01-28 Thread William Brown
> > with "export NSS_DISABLE_HW_GCM=1", there are no crashes, with and > without the cipher option. Moreover, with the cipher option it says: > > CONNECTED(0003) > 139960478934944:error:14077410:SSL > routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake > failure:s23_clnt.c:744: > --- > no

[389-users] Re: Crash logs

2016-01-28 Thread Todor Petkov
> It looks like it just a client connection that is using AES GCM, it > hasn't got to process the ldap request yet. I think that the following > should work: > > openssl s_client -connect LDAPHOSTNAME:636 -cipher ECDHE-RSA-AES256- > GCM-SHA384 > > Should be able to reproduce it. Else, you can wait

[389-users] Re: Crash logs

2016-01-27 Thread William Brown
On Wed, 2016-01-27 at 23:29 +0200, Todor Petkov wrote: > > > > > You might have hit a nss-softokn - processor mismatch issue.  Could > > you > > please try this workaround? > > > > We would like to know setting the following environment variable(s) > > changes the behavior. > > 1) > > Open /etc/s

[389-users] Re: Crash logs

2016-01-27 Thread Todor Petkov
>> > You might have hit a nss-softokn - processor mismatch issue. Could you > please try this workaround? > > We would like to know setting the following environment variable(s) > changes the behavior. > 1) > Open /etc/sysconfig/dirsrv and add the following line: > export NSS_DISABLE_HW_GCM=1 >

[389-users] Re: Crash logs

2016-01-27 Thread Noriko Hosoi
On 01/27/2016 12:33 PM, Todor Petkov wrote: On 1/27/2016 10:20 PM, Mark Reynolds wrote: The server is crashing in the NSS library: Program terminated with signal 4, Illegal instruction. #0 0x7f82f5bdad60 in ?? () from /usr/lib64/libfreeblpriv3.so Thread 1 (Thread 0x7f82d7fff700 (LWP 2500

[389-users] Re: Crash logs

2016-01-27 Thread Todor Petkov
On 1/27/2016 10:20 PM, Mark Reynolds wrote: > The server is crashing in the NSS library: > > Program terminated with signal 4, Illegal instruction. > #0 0x7f82f5bdad60 in ?? () from /usr/lib64/libfreeblpriv3.so > > Thread 1 (Thread 0x7f82d7fff700 (LWP 25001)): > #0 0x7f82f5bdad60 in ?

[389-users] Re: Crash logs

2016-01-27 Thread Todor Petkov
On 1/27/2016 9:35 PM, Mark Reynolds wrote: > A single stack trace is not that large, you could paste it in the email. Actually it's around 100k (2000 lines). I put it on pastebin, http://pastebin.com/5AePWyRm Thanks -- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.

[389-users] Re: Crash logs

2016-01-27 Thread Mark Reynolds
On 01/27/2016 02:31 PM, Todor Petkov wrote: On 1/27/2016 9:18 PM, Mark Reynolds wrote: No problem. I tried to send the stack trace as attachment, and the mailing list software informed me that the message is currently pending approval. Thanks again for the fast answers. A single stack trac

[389-users] Re: Crash logs

2016-01-27 Thread Todor Petkov
On 1/27/2016 9:18 PM, Mark Reynolds wrote: > No problem. I tried to send the stack trace as attachment, and the mailing list software informed me that the message is currently pending approval. Thanks again for the fast answers. Regards, -- 389 users mailing list 389-users@%(host_name)s http:/

[389-users] Re: Crash logs

2016-01-27 Thread Mark Reynolds
On 01/27/2016 02:09 PM, Todor Petkov wrote: On 1/27/2016 4:00 PM, Mark Reynolds wrote: On 01/27/2016 02:44 AM, Todor Petkov wrote: Hello, few weeks ago I posted that I am experiencing crashes of the ldap server and I was advised how to collect the logs. I have managed to collect them, the

[389-users] Re: Crash logs

2016-01-27 Thread Todor Petkov
On 1/27/2016 4:00 PM, Mark Reynolds wrote: > > > On 01/27/2016 02:44 AM, Todor Petkov wrote: >> Hello, >> >> few weeks ago I posted that I am experiencing crashes of the ldap >> server and I was advised how to collect the logs. I have managed to >> collect them, the file is around 120k, where d

[389-users] Re: Crash logs

2016-01-27 Thread Mark Reynolds
On 01/27/2016 02:44 AM, Todor Petkov wrote: Hello, few weeks ago I posted that I am experiencing crashes of the ldap server and I was advised how to collect the logs. I have managed to collect them, the file is around 120k, where do I have to post it? Do you mean stack traces? If you have sta