| Author |
Message |
|
| Guest |
 Posted: Sat Apr 24, 2010 9:11 pm |
 |
|
|
Guest
|
erlyaws-list,
I have an erlang application which uses yaws in ``embedded'' mode,
currently using yaws-1.84. In testing the update to yaws-1.88, I
consistently get the following type of error:
crasher:
initial call: ssl_connection:init/1
pid: <0.99.0>
registered_name: []
exception exit: {badarg,[{erlang,port_control,
[crypto_drv04,19,[<<0,0,0,28,0,0>>]]},
{crypto,control,2},
{ssl_record,random,0},
{ssl_record,empty_security_params,1},
{ssl_record,init_connection_states,1},
{ssl_connection,initial_state,7},
{ssl_connection,init,1},
{gen_fsm,init_it,6}]}
in function gen_fsm:init_it/6
ancestors: [ssl_connection_sup,ssl_sup,<0.60.0>]
messages: []
links: [<0.64.0>]
dictionary: []
trap_exit: false
status: running
heap_size: 377
stack_size: 24
reductions: 157
neighbours:
I have found that using the old ssl implementation (instead of
new_ssl) fixes the problem and I see no other regressions in my
application.
GC2 = ?gc_set_use_old_ssl(GC1, true)
I am interested testing new_ssl if it is possible, but I am not sure
how to diagnose this problem. Any help will be appreciated. I will be
happy to supply more info on request.
Brady
------------------------------------------------------------------------------
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sat Apr 24, 2010 9:31 pm |
|
|
|
Guest
|
Brady McCary wrote:
> erlyaws-list,
>
> I have an erlang application which uses yaws in ``embedded'' mode,
> currently using yaws-1.84. In testing the update to yaws-1.88, I
> consistently get the following type of error:
>
> crasher:
> initial call: ssl_connection:init/1
> pid: <0.99.0>
> registered_name: []
> exception exit: {badarg,[{erlang,port_control,
> [crypto_drv04,19,[<<0,0,0,28,0,0>>]]},
> {crypto,control,2},
> {ssl_record,random,0},
> {ssl_record,empty_security_params,1},
> {ssl_record,init_connection_states,1},
> {ssl_connection,initial_state,7},
> {ssl_connection,init,1},
> {gen_fsm,init_it,6}]}
I've never seen this error. It seems to be related to the crypto driver, which
is linked to lib_crypto.so.
Which OS and which version of OS do you have.
/klacke
------------------------------------------------------------------------------
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sat Apr 24, 2010 9:53 pm |
|
|
|
Guest
|
Claes Wikstrom wrote:
> Brady McCary wrote:
>> erlyaws-list,
>>
>> I have an erlang application which uses yaws in ``embedded'' mode,
>> currently using yaws-1.84. In testing the update to yaws-1.88, I
>> consistently get the following type of error:
>>
>> crasher:
>> initial call: ssl_connection:init/1
>> pid: <0.99.0>
>> registered_name: []
>> exception exit: {badarg,[{erlang,port_control,
>> [crypto_drv04,19,[<<0,0,0,28,0,0>>]]},
>> {crypto,control,2},
>> {ssl_record,random,0},
>> {ssl_record,empty_security_params,1},
>> {ssl_record,init_connection_states,1},
>> {ssl_connection,initial_state,7},
>> {ssl_connection,init,1},
>> {gen_fsm,init_it,6}]}
>
> I've never seen this error. It seems to be related to the crypto driver, which
> is linked to lib_crypto.so.
> Which OS and which version of OS do you have.
>
Also, try:
2> crypto:start().
ok
3> crypto:info_lib().
[{<<"OpenSSL">>,9470079,<<"OpenSSL 0.9.8g 19 Oct 2007">>}]
4> crypto:sha("abc").
<<169,153,62,54,71,6,129,106,186,62,37,113,120,80,194,108,
156,208,216,157>>
5> crypto:rand_bytes(1 .
<<176,195,159,236,78,120,200,123,105,54,15,7,108,140,184,
109,239,212>>
/klacke
------------------------------------------------------------------------------
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Apr 25, 2010 6:14 pm |
|
|
|
Guest
|
Brady McCary wrote:
> The OS is Ubuntu Jaunty.
>
> $ uname -a
> Linux LMTLinux2 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:49:34
> UTC 2009 i686 GNU/Linux
>
> The erlang emulator I am using is compiled from source.
>
....
> Eshell V5.7.5 (abort with ^G)
> 1> crypto:start().
> ok
> 2> crypto:info_lib().
> [{<<"OpenSSL">>,9470079,<<"OpenSSL 0.9.8g 19 Oct 2007">>}]
> 3> crypto:sha("abc").
> <<169,153,62,54,71,6,129,106,186,62,37,113,120,80,194,108,
> 156,208,216,157>>
> 4> crypto:rand_bytes(1.
> <<207,42,205,232,132,66,246,59,135,13,41,189,204,104,37,
> 47,158,64>>
> 5>
All looks good, normal stuff.
So, to get any further with this it needs debugging.
I'm sure the SSL developers in the OTP group would be interested
in finding and clearing this.
Your first step - if you choose to pursue this - is to allow other
people than you to reproduce it. I certainly can't.
/klacke
------------------------------------------------------------------------------
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post received from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
