在MacOS X上Erlang和Yaws設置

Question

我想在我的Mac OS X 10.8上運行Yaws 1.94並崩潰。我跑二郎R15B01

我使用的MacPorts與命令安裝此：

sudo port selfupdate 

sudo port install erlang +ssl yaws 

export ERL_LIBS=/opt/local/lib/yaws/ 

sudo mkdir /etc/yaws/ 

sudo cp /opt/local/etc/yaws/yaws.conf.template /etc/yaws/yaws.conf 

當我運行雅司病，它崩潰

$ sudo yaws -i --conf /etc/yaws/yaws.conf 

二郎R15B01（專家評審組-5.9.1 ）[來源] [64位] [SMP：4：4] [異步線程：0] [HIPE] [內核級的投票：TRUE]

Eshell V5.9.1 (abort with ^G) 
1> 
=INFO REPORT==== 25-Jul-2012::16:36:20 === 
Yaws: Using config file /etc/yaws/yaws.conf 

=INFO REPORT==== 25-Jul-2012::16:36:20 === 
yaws debug:Add path "/opt/local/var/yaws/ebin" 

=INFO REPORT==== 25-Jul-2012::16:36:20 === 
yaws debug:Add path "/opt/local/lib/yaws/ebin" 

=INFO REPORT==== 25-Jul-2012::16:36:20 === 
yaws debug:Add path "/opt/local/lib/yaws/examples/ebin" 

=INFO REPORT==== 25-Jul-2012::16:36:20 === 
yaws debug:Running with id="default" (localinstall=false) 
Running with debug checks turned on (slower server) 
to directory "/opt/local/var/log/yaws" 

=INFO REPORT==== 25-Jul-2012::16:36:20 === 
    application: yaws 
    exited: {shutdown,{yaws_app,start,[normal,[]]}} 
    type: permanent 
{"Kernel pid terminated",application_controller,"{application_start_failure,yaws,{shutdown,{yaws_app,start,[normal,[]]}}}"} 

Crash dump was written to: erl_crash.dump 
Kernel pid terminated (application_controller) ({application_start_failure,yaws,{shutdown,{yaws_app,start,[normal,[]]}}}) 

結果

當我檢查是否存在一個雅各布進程（ps -efw | grep雅司）並且沒有

我在這裏錯過了什麼？我很想能夠使用雅司病在Mac OS X感謝

這裏是SASL

$ sudo yaws -i --conf /etc/yaws/yaws.conf --erlarg '-boot start_sasl' 
Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:4:4] [async-threads:0] [hipe] [kernel-poll:true] 


=PROGRESS REPORT==== 26-Jul-2012::15:41:44 === 
     supervisor: {local,sasl_safe_sup} 
     started: [{pid,<0.34.0>}, 
        {name,alarm_handler}, 
        {mfargs,{alarm_handler,start_link,[]}}, 
        {restart_type,permanent}, 
        {shutdown,2000}, 
        {child_type,worker}] 

=PROGRESS REPORT==== 26-Jul-2012::15:41:44 === 
     supervisor: {local,sasl_safe_sup} 
     started: [{pid,<0.35.0>}, 
        {name,overload}, 
        {mfargs,{overload,start_link,[]}}, 
        {restart_type,permanent}, 
        {shutdown,2000}, 
        {child_type,worker}] 

=PROGRESS REPORT==== 26-Jul-2012::15:41:44 === 
     supervisor: {local,sasl_sup} 
     started: [{pid,<0.33.0>}, 
        {name,sasl_safe_sup}, 
        {mfargs, 
         {supervisor,start_link, 
          [{local,sasl_safe_sup},sasl,safe]}}, 
        {restart_type,permanent}, 
        {shutdown,infinity}, 
        {child_type,supervisor}] 

=PROGRESS REPORT==== 26-Jul-2012::15:41:44 === 
     supervisor: {local,sasl_sup} 
     started: [{pid,<0.36.0>}, 
        {name,release_handler}, 
        {mfargs,{release_handler,start_link,[]}}, 
        {restart_type,permanent}, 
        {shutdown,2000}, 
        {child_type,worker}] 

=PROGRESS REPORT==== 26-Jul-2012::15:41:44 === 
    application: sasl 
     started_at: nonode@nohost 

=PROGRESS REPORT==== 26-Jul-2012::15:41:44 === 
     supervisor: {local,yaws_sup} 
     started: [{pid,<0.43.0>}, 
        {name,yaws_log}, 
        {mfargs,{yaws_log,start_link,[]}}, 
        {restart_type,permanent}, 
        {shutdown,5000}, 
        {child_type,worker}] 

=PROGRESS REPORT==== 26-Jul-2012::15:41:44 === 
     supervisor: {local,yaws_sup} 
     started: [{pid,<0.44.0>}, 
        {name,yaws_trace}, 
        {mfargs,{yaws_trace,start_link,[]}}, 
        {restart_type,permanent}, 
        {shutdown,5000}, 
        {child_type,worker}] 
Eshell V5.9.1 (abort with ^G) 
1> 
=INFO REPORT==== 26-Jul-2012::15:41:44 === 
Yaws: Using config file /etc/yaws/yaws.conf 

=INFO REPORT==== 26-Jul-2012::15:41:44 === 
yaws debug:Add path "/opt/local/var/yaws/ebin" 

=INFO REPORT==== 26-Jul-2012::15:41:44 === 
yaws debug:Add path "/opt/local/lib/yaws/ebin" 

=INFO REPORT==== 26-Jul-2012::15:41:44 === 
yaws debug:Add path "/opt/local/lib/yaws/examples/ebin" 

=INFO REPORT==== 26-Jul-2012::15:41:44 === 
yaws debug:Running with id="default" (localinstall=false) 
Running with debug checks turned on (slower server) 
Logging to directory "/opt/local/var/log/yaws" 

=CRASH REPORT==== 26-Jul-2012::15:41:44 === 
crasher: 
initial call: yaws_server:init/1 
pid: <0.45.0> 
registered_name: [] 
exception exit: {{badmatch,{error,enotdir}}, 
       [{yaws_server,setup_dirs,1, 
           [{file,"yaws_server.erl"},{line,525}]}, 
        {yaws_server,init2,5, 
           [{file,"yaws_server.erl"},{line,200}]}, 
        {gen_server,init_it,6, 
           [{file,"gen_server.erl"},{line,304}]}, 
        {proc_lib,init_p_do_apply,3, 
          [{file,"proc_lib.erl"},{line,227}]}]} 
    in function gen_server:init_it/6 (gen_server.erl, line 328) 
ancestors: [yaws_sup,<0.41.0>] 
messages: [] 
links: [<0.42.0>] 
dictionary: [{start_time,{{2012,7,26},{15,41,44}}}, 
       {gc,{gconf,"/opt/local/lib/yaws",false,102, 
         "/opt/local/var/log/yaws", 
         ["/opt/local/var/yaws/ebin", 
          "/opt/local/lib/yaws/ebin", 
          "/opt/local/lib/yaws/examples/ebin"], 
         [],30000,nolimit,400,1000000,8000,nolimit,[], 
         10240,[],1000000,0, 
         ["/opt/local/lib/yaws/include", 
          "/opt/local/lib/yaws/examples/include"], 
         "/usr/bin/php-cgi","Yaws 1.94","default",false, 
         [],yaws_session_server,8}}] 
trap_exit: true 
status: running 
heap_size: 2584 
stack_size: 24 
reductions: 40977 
neighbours: 

=SUPERVISOR REPORT==== 26-Jul-2012::15:41:44 === 
Supervisor: {local,yaws_sup} 
Context: start_error 
Reason:  {{badmatch,{error,enotdir}}, 
       [{yaws_server,setup_dirs,1, 
          [{file,"yaws_server.erl"},{line,525}]}, 
       {yaws_server,init2,5,[{file,"yaws_server.erl"},{line,200}]}, 
       {gen_server,init_it,6,[{file,"gen_server.erl"},{line,304}]}, 
       {proc_lib,init_p_do_apply,3, 
         [{file,"proc_lib.erl"},{line,227}]}]} 
Offender: [{pid,undefined}, 
       {name,yaws_server}, 
       {mfargs, 
        {yaws_server,start_link, 
         [{env,true,false,false, 
          {file,"/etc/yaws/yaws.conf"}, 
          false,false,"default"}]}}, 
       {restart_type,permanent}, 
       {shutdown,120000}, 
       {child_type,worker}] 


=INFO REPORT==== 26-Jul-2012::15:41:44 === 
application: yaws 
exited: {shutdown,{yaws_app,start,[normal,[]]}} 
type: permanent 
{"Kernel pid terminated",application_controller,"{application_start_failure,yaws,{shutdown,{yaws_app,start,[normal,[]]}}}"} 

Crash dump was written to: erl_crash.dump 
Kernel pid terminated (application_controller) ({application_start_failure,yaws,{shutdown,{yaws_app,start,[normal,[]]}}}) 

Answer 1

輸出我不知道起源或生存能力的構建Erlang和雅司病之一可以通過macports檢索，所以我不知道他們是否真的工作。就我個人而言，我不會使用macports，因爲我從那裏獲得的其他軟件存在問題。

，試圖得到什麼與你的雅司病安裝腳麻更多信息，開始雅司病是這樣的：

sudo yaws -i --conf /etc/yaws/yaws.conf --erlarg '-boot start_sasl' 

希望sasl可以給我們介紹一下基本問題的詳細信息。

Answer 2

看着崩潰消息中的錯誤exception exit: {badmatch,{error,enotdir}}。這看起來像雅各希望在某處找到一個目錄，並發現其他的東西。我建議你看文件yaws_server.erl中的525行。你甚至可以把一個io:format/2，看看雅各在這一點上得到什麼。它可能是一個錯誤格式的目錄名稱，可能包含空格。你也可以嘗試檢查它使用的conf文件來啓動並查看服務器想用作docroot的PATHS。此外，請檢查雅可布安裝目錄的權限以及雅可布想要查看的所有Directories。