C.R. Oldham mentioned that he has noticed nsd eating up CPU while using nsopenssl. I just updated to the latest CVS of nsopenssl and am now noticing the same thing. If I set Trace to true, it seems that nsopenssl is going into an infinite loop:
[25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 104 secs: before/accept initialization [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 800856 secs: before/accept initialization [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 477 secs: SSLv3 read client hello A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 44 secs: SSLv3 write server hello A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 113 secs: SSLv3 write certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 16 secs: SSLv3 write server done A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 51 secs: SSLv3 flush data [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 19 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 13 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 26 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 23 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 75 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 24 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 23 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 23 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 24 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 23 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 23 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 23 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 24 secs: SSLv3 read client certificate A [25/Feb/2004:19:40:19][20116.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x9151c28): 23 secs: SSLv3 read client certificate A This last statement repeats forever, with different time values. Reverting back to the most recent CVS tag (v3_0beta13) fixes the problem: [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 86 secs: before/accept initialization [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 97 secs: before/accept initialization [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 353 secs: SSLv3 read client hello A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 34 secs: SSLv3 write server hello A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 102 secs: SSLv3 write certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 17 secs: SSLv3 write server done A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 40 secs: SSLv3 flush data [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 18 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 13 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 26 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 25 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 38 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 24 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 23 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 24 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 23 secs: SSLv3 read client certificate A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 431380 secs: SSLv3 read client key exchange A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 275 secs: SSLv3 read finished A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 22 secs: SSLv3 write change cipher spec A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 75 secs: SSLv3 write finished A [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 35 secs: SSLv3 flush data [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 67 secs: SSL negotiation finished successfully [25/Feb/2004:20:00:33][21688.49156][-conn:kurup::0] Notice: nsopenssl (kurup): trace (0x822d418): 14 secs: SSL negotiation finished successfully I'm not 100% sure that I've configured nsopenssl correctly, so I'm going to investigate further, but wanted to see if this was the same behavior that others were seeing. Vinod -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
