yaws built with crypto fails to start












1















I need to use hashed passwords for authentication in Yaws.



I've rebuilt it from source (https://github.com/klacke/yaws), with this sequence of commands:



./configure --enable-crypto --prefix=/some/local/path
make install


When I run yaws (/some/local/path/bin/yaws -i -erlarg "-boot start_sasl"), I get this error:



{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}


The crypto library is present:



checking for Erlang/OTP 'crypto' library subdirectory... /usr/local/Cellar/erlang/19.2/lib/erlang/lib/crypto-3.7.2
checking for Erlang/OTP 'crypto' library version... 3.7.2


What is this problem caused by? Do I need to pass some specific options to run the newly built Yaws server?



When I run make test, all tests pass.



EDIT



Starting yaws with bin/yaws -i -erlarg "-init_debug" yields this output:



{progress,preloaded}
{progress,kernel_load_completed}
{progress,modules_loaded}
{start,heart}
{start,error_logger}
{start,application_controller}
{progress,init_kernel_started}
{apply,{application,load,[{application,stdlib,[{description,"ERTS CXC 138 10"},{vsn,"3.2"},{id,},{modules,[array,base64,beam_lib,binary,c,calendar,dets,dets_server,dets_sup,dets_utils,dets_v8,dets_v9,dict,digraph,digraph_utils,edlin,edlin_expand,epp,eval_bits,erl_anno,erl_bits,erl_compile,erl_eval,erl_expand_records,erl_internal,erl_lint,erl_parse,erl_posix_msg,erl_pp,erl_scan,erl_tar,error_logger_file_h,error_logger_tty_h,escript,ets,file_sorter,filelib,filename,gb_trees,gb_sets,gen,gen_event,gen_fsm,gen_server,gen_statem,io,io_lib,io_lib_format,io_lib_fread,io_lib_pretty,lib,lists,log_mf_h,maps,math,ms_transform,orddict,ordsets,otp_internal,pool,proc_lib,proplists,qlc,qlc_pt,queue,rand,random,re,sets,shell,shell_default,slave,sofs,string,supervisor,supervisor_bridge,sys,timer,unicode,win32reg,zip]},{registered,[timer_server,rsh_starter,take_over_monitor,pool_master,dets]},{applications,[kernel]},{included_applications,},{env,},{maxT,infinity},{maxP,infinity}]}]}}
{progress,applications_loaded}
{apply,{application,start_boot,[kernel,permanent]}}
Erlang/OTP 19 [erts-8.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:true] [dtrace]

{apply,{application,start_boot,[stdlib,permanent]}}
{apply,{application,start_boot,[sasl,permanent]}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.60.0>},
{id,alarm_handler},
{mfargs,{alarm_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.59.0>},
{id,sasl_safe_sup},
{mfargs,
{supervisor,start_link,
[{local,sasl_safe_sup},sasl,safe]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.61.0>},
{id,release_handler},
{mfargs,{release_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
{apply,{c,erlangrc,}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
application: sasl
started_at: nonode@nohost
{progress,started}
{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}
init terminating in do_boot ()


It appears that the crypto service is not started.










share|improve this question




















  • 1





    Are you building yaws from master? What version of Erlang/OTP are you using (looks like 19.2 but I just want to be sure)? Is crypto listed in the yaws.app file?

    – Steve Vinoski
    Nov 16 '18 at 16:19











  • I'm using version 19.2, and building from master (a4eec94b) At the end of yaws.app file, I have {applications,[kernel,stdlib,crypto]}]}.

    – btk
    Nov 16 '18 at 20:24








  • 1





    So far I've been unable to reproduce this issue. Please check the output to the terminal during startup to see if crypto is getting started prior to any yaws processes starting. You might also consider adding -erlarg -init_debug to your command line to try to get more information

    – Steve Vinoski
    Nov 17 '18 at 2:42











  • It seems that crypto application is not getting started -- how can I make sure it starts as part of yaws boot?

    – btk
    Nov 20 '18 at 18:53













  • In the second comment here, you said that yaws.app contains crypto, but as you can see from the init_debug output, the kernel and stdlib applications both start but crypto is never mentioned anywhere. You need to make sure the right yaws.app file specifies the crypto application; that file should be located in the ebin directory of wherever the yaws application you're running is installed.

    – Steve Vinoski
    Nov 21 '18 at 3:25
















1















I need to use hashed passwords for authentication in Yaws.



I've rebuilt it from source (https://github.com/klacke/yaws), with this sequence of commands:



./configure --enable-crypto --prefix=/some/local/path
make install


When I run yaws (/some/local/path/bin/yaws -i -erlarg "-boot start_sasl"), I get this error:



{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}


The crypto library is present:



checking for Erlang/OTP 'crypto' library subdirectory... /usr/local/Cellar/erlang/19.2/lib/erlang/lib/crypto-3.7.2
checking for Erlang/OTP 'crypto' library version... 3.7.2


What is this problem caused by? Do I need to pass some specific options to run the newly built Yaws server?



When I run make test, all tests pass.



EDIT



Starting yaws with bin/yaws -i -erlarg "-init_debug" yields this output:



{progress,preloaded}
{progress,kernel_load_completed}
{progress,modules_loaded}
{start,heart}
{start,error_logger}
{start,application_controller}
{progress,init_kernel_started}
{apply,{application,load,[{application,stdlib,[{description,"ERTS CXC 138 10"},{vsn,"3.2"},{id,},{modules,[array,base64,beam_lib,binary,c,calendar,dets,dets_server,dets_sup,dets_utils,dets_v8,dets_v9,dict,digraph,digraph_utils,edlin,edlin_expand,epp,eval_bits,erl_anno,erl_bits,erl_compile,erl_eval,erl_expand_records,erl_internal,erl_lint,erl_parse,erl_posix_msg,erl_pp,erl_scan,erl_tar,error_logger_file_h,error_logger_tty_h,escript,ets,file_sorter,filelib,filename,gb_trees,gb_sets,gen,gen_event,gen_fsm,gen_server,gen_statem,io,io_lib,io_lib_format,io_lib_fread,io_lib_pretty,lib,lists,log_mf_h,maps,math,ms_transform,orddict,ordsets,otp_internal,pool,proc_lib,proplists,qlc,qlc_pt,queue,rand,random,re,sets,shell,shell_default,slave,sofs,string,supervisor,supervisor_bridge,sys,timer,unicode,win32reg,zip]},{registered,[timer_server,rsh_starter,take_over_monitor,pool_master,dets]},{applications,[kernel]},{included_applications,},{env,},{maxT,infinity},{maxP,infinity}]}]}}
{progress,applications_loaded}
{apply,{application,start_boot,[kernel,permanent]}}
Erlang/OTP 19 [erts-8.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:true] [dtrace]

{apply,{application,start_boot,[stdlib,permanent]}}
{apply,{application,start_boot,[sasl,permanent]}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.60.0>},
{id,alarm_handler},
{mfargs,{alarm_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.59.0>},
{id,sasl_safe_sup},
{mfargs,
{supervisor,start_link,
[{local,sasl_safe_sup},sasl,safe]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.61.0>},
{id,release_handler},
{mfargs,{release_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
{apply,{c,erlangrc,}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
application: sasl
started_at: nonode@nohost
{progress,started}
{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}
init terminating in do_boot ()


It appears that the crypto service is not started.










share|improve this question




















  • 1





    Are you building yaws from master? What version of Erlang/OTP are you using (looks like 19.2 but I just want to be sure)? Is crypto listed in the yaws.app file?

    – Steve Vinoski
    Nov 16 '18 at 16:19











  • I'm using version 19.2, and building from master (a4eec94b) At the end of yaws.app file, I have {applications,[kernel,stdlib,crypto]}]}.

    – btk
    Nov 16 '18 at 20:24








  • 1





    So far I've been unable to reproduce this issue. Please check the output to the terminal during startup to see if crypto is getting started prior to any yaws processes starting. You might also consider adding -erlarg -init_debug to your command line to try to get more information

    – Steve Vinoski
    Nov 17 '18 at 2:42











  • It seems that crypto application is not getting started -- how can I make sure it starts as part of yaws boot?

    – btk
    Nov 20 '18 at 18:53













  • In the second comment here, you said that yaws.app contains crypto, but as you can see from the init_debug output, the kernel and stdlib applications both start but crypto is never mentioned anywhere. You need to make sure the right yaws.app file specifies the crypto application; that file should be located in the ebin directory of wherever the yaws application you're running is installed.

    – Steve Vinoski
    Nov 21 '18 at 3:25














1












1








1








I need to use hashed passwords for authentication in Yaws.



I've rebuilt it from source (https://github.com/klacke/yaws), with this sequence of commands:



./configure --enable-crypto --prefix=/some/local/path
make install


When I run yaws (/some/local/path/bin/yaws -i -erlarg "-boot start_sasl"), I get this error:



{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}


The crypto library is present:



checking for Erlang/OTP 'crypto' library subdirectory... /usr/local/Cellar/erlang/19.2/lib/erlang/lib/crypto-3.7.2
checking for Erlang/OTP 'crypto' library version... 3.7.2


What is this problem caused by? Do I need to pass some specific options to run the newly built Yaws server?



When I run make test, all tests pass.



EDIT



Starting yaws with bin/yaws -i -erlarg "-init_debug" yields this output:



{progress,preloaded}
{progress,kernel_load_completed}
{progress,modules_loaded}
{start,heart}
{start,error_logger}
{start,application_controller}
{progress,init_kernel_started}
{apply,{application,load,[{application,stdlib,[{description,"ERTS CXC 138 10"},{vsn,"3.2"},{id,},{modules,[array,base64,beam_lib,binary,c,calendar,dets,dets_server,dets_sup,dets_utils,dets_v8,dets_v9,dict,digraph,digraph_utils,edlin,edlin_expand,epp,eval_bits,erl_anno,erl_bits,erl_compile,erl_eval,erl_expand_records,erl_internal,erl_lint,erl_parse,erl_posix_msg,erl_pp,erl_scan,erl_tar,error_logger_file_h,error_logger_tty_h,escript,ets,file_sorter,filelib,filename,gb_trees,gb_sets,gen,gen_event,gen_fsm,gen_server,gen_statem,io,io_lib,io_lib_format,io_lib_fread,io_lib_pretty,lib,lists,log_mf_h,maps,math,ms_transform,orddict,ordsets,otp_internal,pool,proc_lib,proplists,qlc,qlc_pt,queue,rand,random,re,sets,shell,shell_default,slave,sofs,string,supervisor,supervisor_bridge,sys,timer,unicode,win32reg,zip]},{registered,[timer_server,rsh_starter,take_over_monitor,pool_master,dets]},{applications,[kernel]},{included_applications,},{env,},{maxT,infinity},{maxP,infinity}]}]}}
{progress,applications_loaded}
{apply,{application,start_boot,[kernel,permanent]}}
Erlang/OTP 19 [erts-8.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:true] [dtrace]

{apply,{application,start_boot,[stdlib,permanent]}}
{apply,{application,start_boot,[sasl,permanent]}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.60.0>},
{id,alarm_handler},
{mfargs,{alarm_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.59.0>},
{id,sasl_safe_sup},
{mfargs,
{supervisor,start_link,
[{local,sasl_safe_sup},sasl,safe]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.61.0>},
{id,release_handler},
{mfargs,{release_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
{apply,{c,erlangrc,}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
application: sasl
started_at: nonode@nohost
{progress,started}
{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}
init terminating in do_boot ()


It appears that the crypto service is not started.










share|improve this question
















I need to use hashed passwords for authentication in Yaws.



I've rebuilt it from source (https://github.com/klacke/yaws), with this sequence of commands:



./configure --enable-crypto --prefix=/some/local/path
make install


When I run yaws (/some/local/path/bin/yaws -i -erlarg "-boot start_sasl"), I get this error:



{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}


The crypto library is present:



checking for Erlang/OTP 'crypto' library subdirectory... /usr/local/Cellar/erlang/19.2/lib/erlang/lib/crypto-3.7.2
checking for Erlang/OTP 'crypto' library version... 3.7.2


What is this problem caused by? Do I need to pass some specific options to run the newly built Yaws server?



When I run make test, all tests pass.



EDIT



Starting yaws with bin/yaws -i -erlarg "-init_debug" yields this output:



{progress,preloaded}
{progress,kernel_load_completed}
{progress,modules_loaded}
{start,heart}
{start,error_logger}
{start,application_controller}
{progress,init_kernel_started}
{apply,{application,load,[{application,stdlib,[{description,"ERTS CXC 138 10"},{vsn,"3.2"},{id,},{modules,[array,base64,beam_lib,binary,c,calendar,dets,dets_server,dets_sup,dets_utils,dets_v8,dets_v9,dict,digraph,digraph_utils,edlin,edlin_expand,epp,eval_bits,erl_anno,erl_bits,erl_compile,erl_eval,erl_expand_records,erl_internal,erl_lint,erl_parse,erl_posix_msg,erl_pp,erl_scan,erl_tar,error_logger_file_h,error_logger_tty_h,escript,ets,file_sorter,filelib,filename,gb_trees,gb_sets,gen,gen_event,gen_fsm,gen_server,gen_statem,io,io_lib,io_lib_format,io_lib_fread,io_lib_pretty,lib,lists,log_mf_h,maps,math,ms_transform,orddict,ordsets,otp_internal,pool,proc_lib,proplists,qlc,qlc_pt,queue,rand,random,re,sets,shell,shell_default,slave,sofs,string,supervisor,supervisor_bridge,sys,timer,unicode,win32reg,zip]},{registered,[timer_server,rsh_starter,take_over_monitor,pool_master,dets]},{applications,[kernel]},{included_applications,},{env,},{maxT,infinity},{maxP,infinity}]}]}}
{progress,applications_loaded}
{apply,{application,start_boot,[kernel,permanent]}}
Erlang/OTP 19 [erts-8.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:true] [dtrace]

{apply,{application,start_boot,[stdlib,permanent]}}
{apply,{application,start_boot,[sasl,permanent]}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.60.0>},
{id,alarm_handler},
{mfargs,{alarm_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.59.0>},
{id,sasl_safe_sup},
{mfargs,
{supervisor,start_link,
[{local,sasl_safe_sup},sasl,safe]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.61.0>},
{id,release_handler},
{mfargs,{release_handler,start_link,}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
{apply,{c,erlangrc,}}

=PROGRESS REPORT==== 20-Nov-2018::14:09:57 ===
application: sasl
started_at: nonode@nohost
{progress,started}
{"init terminating in do_boot",{{badmatch,{'EXIT',{badarg,[{erlang,list_to_existing_atom,["crypto"],},{yaws,'-start_app_deps/0-fun-0-',2,[{file,"yaws.erl"},{line,264}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{yaws,start_app_deps,0,[{file,"yaws.erl"},{line,263}]},{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}},[{yaws,start,0,[{file,"yaws.erl"},{line,209}]},{init,start_em,1,},{init,do_boot,3,}]}}
init terminating in do_boot ()


It appears that the crypto service is not started.







cryptography erlang yaws






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 19:11







btk

















asked Nov 15 '18 at 21:44









btkbtk

1,98122124




1,98122124








  • 1





    Are you building yaws from master? What version of Erlang/OTP are you using (looks like 19.2 but I just want to be sure)? Is crypto listed in the yaws.app file?

    – Steve Vinoski
    Nov 16 '18 at 16:19











  • I'm using version 19.2, and building from master (a4eec94b) At the end of yaws.app file, I have {applications,[kernel,stdlib,crypto]}]}.

    – btk
    Nov 16 '18 at 20:24








  • 1





    So far I've been unable to reproduce this issue. Please check the output to the terminal during startup to see if crypto is getting started prior to any yaws processes starting. You might also consider adding -erlarg -init_debug to your command line to try to get more information

    – Steve Vinoski
    Nov 17 '18 at 2:42











  • It seems that crypto application is not getting started -- how can I make sure it starts as part of yaws boot?

    – btk
    Nov 20 '18 at 18:53













  • In the second comment here, you said that yaws.app contains crypto, but as you can see from the init_debug output, the kernel and stdlib applications both start but crypto is never mentioned anywhere. You need to make sure the right yaws.app file specifies the crypto application; that file should be located in the ebin directory of wherever the yaws application you're running is installed.

    – Steve Vinoski
    Nov 21 '18 at 3:25














  • 1





    Are you building yaws from master? What version of Erlang/OTP are you using (looks like 19.2 but I just want to be sure)? Is crypto listed in the yaws.app file?

    – Steve Vinoski
    Nov 16 '18 at 16:19











  • I'm using version 19.2, and building from master (a4eec94b) At the end of yaws.app file, I have {applications,[kernel,stdlib,crypto]}]}.

    – btk
    Nov 16 '18 at 20:24








  • 1





    So far I've been unable to reproduce this issue. Please check the output to the terminal during startup to see if crypto is getting started prior to any yaws processes starting. You might also consider adding -erlarg -init_debug to your command line to try to get more information

    – Steve Vinoski
    Nov 17 '18 at 2:42











  • It seems that crypto application is not getting started -- how can I make sure it starts as part of yaws boot?

    – btk
    Nov 20 '18 at 18:53













  • In the second comment here, you said that yaws.app contains crypto, but as you can see from the init_debug output, the kernel and stdlib applications both start but crypto is never mentioned anywhere. You need to make sure the right yaws.app file specifies the crypto application; that file should be located in the ebin directory of wherever the yaws application you're running is installed.

    – Steve Vinoski
    Nov 21 '18 at 3:25








1




1





Are you building yaws from master? What version of Erlang/OTP are you using (looks like 19.2 but I just want to be sure)? Is crypto listed in the yaws.app file?

– Steve Vinoski
Nov 16 '18 at 16:19





Are you building yaws from master? What version of Erlang/OTP are you using (looks like 19.2 but I just want to be sure)? Is crypto listed in the yaws.app file?

– Steve Vinoski
Nov 16 '18 at 16:19













I'm using version 19.2, and building from master (a4eec94b) At the end of yaws.app file, I have {applications,[kernel,stdlib,crypto]}]}.

– btk
Nov 16 '18 at 20:24







I'm using version 19.2, and building from master (a4eec94b) At the end of yaws.app file, I have {applications,[kernel,stdlib,crypto]}]}.

– btk
Nov 16 '18 at 20:24






1




1





So far I've been unable to reproduce this issue. Please check the output to the terminal during startup to see if crypto is getting started prior to any yaws processes starting. You might also consider adding -erlarg -init_debug to your command line to try to get more information

– Steve Vinoski
Nov 17 '18 at 2:42





So far I've been unable to reproduce this issue. Please check the output to the terminal during startup to see if crypto is getting started prior to any yaws processes starting. You might also consider adding -erlarg -init_debug to your command line to try to get more information

– Steve Vinoski
Nov 17 '18 at 2:42













It seems that crypto application is not getting started -- how can I make sure it starts as part of yaws boot?

– btk
Nov 20 '18 at 18:53







It seems that crypto application is not getting started -- how can I make sure it starts as part of yaws boot?

– btk
Nov 20 '18 at 18:53















In the second comment here, you said that yaws.app contains crypto, but as you can see from the init_debug output, the kernel and stdlib applications both start but crypto is never mentioned anywhere. You need to make sure the right yaws.app file specifies the crypto application; that file should be located in the ebin directory of wherever the yaws application you're running is installed.

– Steve Vinoski
Nov 21 '18 at 3:25





In the second comment here, you said that yaws.app contains crypto, but as you can see from the init_debug output, the kernel and stdlib applications both start but crypto is never mentioned anywhere. You need to make sure the right yaws.app file specifies the crypto application; that file should be located in the ebin directory of wherever the yaws application you're running is installed.

– Steve Vinoski
Nov 21 '18 at 3:25












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53328322%2fyaws-built-with-crypto-fails-to-start%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53328322%2fyaws-built-with-crypto-fails-to-start%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

List item for chat from Array inside array React Native

Thiostrepton

Caerphilly