Thread: [Erlangweb-users] erlangweb can't start with yaws.
Brought to you by:
etcerlangweb,
paulgray
Menu
▾
▴
erlangweb-users
|
From: Eric L. <eri...@gm...> - 2009-11-03 11:42:43
Attachments:
signature.asc
|
Hi all, I've just tried erlangweb, but unfortunately, the script does't work with yaws. Step by stepy, I followed the erlangweb wiki: http://wiki.erlang-web.org/Install : 1. ./bin/compiler.erl yaws 2. ./bin/start.erl yaws 3. ./bin/start_interactive yaws ---- Crash report occured here While the command ./bin/start_interactive (no yaws argument) can start inets successfully, and I can get the erlangweb-start message from my browser. From the output, I guess this report will be valuable for this problem: =SUPERVISOR REPORT==== 3-Nov-2009::18:19:00 === Supervisor: {local,yaws_sup_restarts} Context: start_error Reason: {'EXIT',{error,could_not_load_driver}} Offender: [{pid,undefined}, {name,yaws_sendfile}, {mfa,{yaws_sendfile_compat,start_link,[]}}, {restart_type,permanent}, {shutdown,5000}, {child_type,worker}] I've tested the yaws_sendfile_compat module by calling: yaws_sendfile_compat:start_link() in the erlang vm, it looks like works. So has anyone here got this problem? or what can I do next? If anymore information required, please let me know. btw, any suggestions will be appreciated. Thanks in advance. Eric ******************************************************************************************************* The following is the whole output: Eshell V5.6.5 (abort with ^G) 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,sasl_safe_sup} started: [{pid,<0.37.0>}, {name,alarm_handler}, {mfa,{alarm_handler,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,sasl_safe_sup} started: [{pid,<0.38.0>}, {name,overload}, {mfa,{overload,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,sasl_sup} started: [{pid,<0.36.0>}, {name,sasl_safe_sup}, {mfa, {supervisor,start_link, [{local,sasl_safe_sup},sasl,safe]}}, {restart_type,permanent}, {shutdown,infinity}, {child_type,supervisor}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,sasl_sup} started: [{pid,<0.39.0>}, {name,release_handler}, {mfa,{release_handler,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === application: sasl started_at: nonode@nohost 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,ssl_sup} started: [{pid,<0.45.0>}, {name,ssl_broker_sup}, {mfa,{ssl_broker_sup,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,supervisor}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,ssl_sup} started: [{pid,<0.46.0>}, {name,ssl_manager}, {mfa,{ssl_manager,start_link,[]}}, {restart_type,permanent}, {shutdown,4000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,ssl_sup} started: [{pid,<0.47.0>}, {name,ssl_connection}, {mfa,{ssl_connection_sup,start_link,[]}}, {restart_type,permanent}, {shutdown,4000}, {child_type,supervisor}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === application: ssl started_at: nonode@nohost 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,crypto_sup} started: [{pid,<0.52.0>}, {name,crypto_server}, {mfa,{crypto_server,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === application: crypto started_at: nonode@nohost 1> =INFO REPORT==== 3-Nov-2009::19:35:46 === e_lang module: error during loading file: "/home/sunny/codes_in_mercurial/erlang-web/config/languages/en.conf", reason:enoent 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,kernel_safe_sup} started: [{pid,<0.62.0>}, {name,timer_server}, {mfa,{timer,start_link,[]}}, {restart_type,permanent}, {shutdown,1000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_sup} started: [{pid,<0.68.0>}, {name,mnesia_event}, {mfa,{mnesia_sup,start_event,[]}}, {restart_type,permanent}, {shutdown,30000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.70.0>}, {name,mnesia_monitor}, {mfa,{mnesia_monitor,start,[]}}, {restart_type,permanent}, {shutdown,3000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.71.0>}, {name,mnesia_subscr}, {mfa,{mnesia_subscr,start,[]}}, {restart_type,permanent}, {shutdown,3000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.72.0>}, {name,mnesia_locker}, {mfa,{mnesia_locker,start,[]}}, {restart_type,permanent}, {shutdown,3000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.73.0>}, {name,mnesia_recover}, {mfa,{mnesia_recover,start,[]}}, {restart_type,permanent}, {shutdown,180000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.74.0>}, {name,mnesia_tm}, {mfa,{mnesia_tm,start,[]}}, {restart_type,permanent}, {shutdown,30000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.75.0>}, {name,mnesia_checkpoint_sup}, {mfa,{mnesia_checkpoint_sup,start,[]}}, {restart_type,permanent}, {shutdown,infinity}, {child_type,supervisor}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.76.0>}, {name,mnesia_snmp_sup}, {mfa,{mnesia_snmp_sup,start,[]}}, {restart_type,permanent}, {shutdown,infinity}, {child_type,supervisor}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.77.0>}, {name,mnesia_controller}, {mfa,{mnesia_controller,start,[]}}, {restart_type,permanent}, {shutdown,3000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_kernel_sup} started: [{pid,<0.78.0>}, {name,mnesia_late_loader}, {mfa,{mnesia_late_loader,start,[]}}, {restart_type,permanent}, {shutdown,3000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,mnesia_sup} started: [{pid,<0.69.0>}, {name,mnesia_kernel_sup}, {mfa,{mnesia_kernel_sup,start,[]}}, {restart_type,permanent}, {shutdown,infinity}, {child_type,supervisor}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === application: mnesia started_at: nonode@nohost 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,eptic} started: [{pid,<0.81.0>}, {name,e_hook}, {mfa,{e_hook,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,eptic} started: [{pid,<0.82.0>}, {name,e_dict}, {mfa,{e_dict,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,eptic} started: [{pid,<0.83.0>}, {name,e_session}, {mfa,{e_session,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,eptic} started: [{pid,<0.84.0>}, {name,e_component}, {mfa,{e_component,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,eptic} started: [{pid,<0.85.0>}, {name,e_logger}, {mfa,{e_logger,start_link,[]}}, {restart_type,permanent}, {shutdown,2000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === application: eptic started_at: nonode@nohost 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === application: wpart started_at: nonode@nohost 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === application: wparts started_at: nonode@nohost 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,yaws_sup} started: [{pid,<0.97.0>}, {name,yaws_log}, {mfa,{yaws_log,start_link,[]}}, {restart_type,permanent}, {shutdown,5000}, {child_type,worker}] 1> =INFO REPORT==== 3-Nov-2009::19:35:46 === Yaws: Using config file /home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf 1> =INFO REPORT==== 3-Nov-2009::19:35:46 === Ctlfile : /home/sunny/.yaws/yaws/erlangweb_test/CTL 1> =INFO REPORT==== 3-Nov-2009::19:35:46 === Yaws: Listening to 0.0.0.0:8000 for <1> virtual servers: - http://localhost:8000 under /home/sunny/codes_in_mercurial/erlang-web/docroot 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,yaws_sup} started: [{pid,<0.98.0>}, {name,yaws_server}, {mfa, {yaws_server,start_link, [{env,false,false,false, {file, "/home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf"}, false,false,"default"}]}}, {restart_type,permanent}, {shutdown,5000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,yaws_sup_restarts} started: [{pid,<0.108.0>}, {name,yaws_session_server}, {mfa,{yaws_session_server,start_link,[]}}, {restart_type,permanent}, {shutdown,5000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,yaws_sup_restarts} started: [{pid,<0.110.0>}, {name,yaws_rss}, {mfa,{yaws_rss,start_link,[]}}, {restart_type,permanent}, {shutdown,5000}, {child_type,worker}] 1> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === supervisor: {local,yaws_sup_restarts} started: [{pid,<0.111.0>}, {name,yaws_event_manager}, {mfa, {gen_event,start_link, [{local,yaws_event_manager}]}}, {restart_type,permanent}, {shutdown,5000}, {child_type,worker}] 1> =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 === Supervisor: {local,yaws_sup_restarts} Context: start_error Reason: {'EXIT',{error,could_not_load_driver}} Offender: [{pid,undefined}, {name,yaws_sendfile}, {mfa,{yaws_sendfile_compat,start_link,[]}}, {restart_type,permanent}, {shutdown,5000}, {child_type,worker}] 1> =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 === Supervisor: {local,yaws_sup} Context: start_error Reason: shutdown Offender: [{pid,undefined}, {name,yaws_sup_restarts}, {mfa,{yaws_sup_restarts,start_link,[]}}, {restart_type,transient}, {shutdown,infinity}, {child_type,supervisor}] 1> =CRASH REPORT==== 3-Nov-2009::19:35:46 === crasher: pid: <0.94.0> registered_name: [] exception exit: {shutdown,{yaws_app,start,[normal,[]]}} in function application_master:init/4 initial call: application_master:init/4 ancestors: [<0.93.0>] messages: [{'EXIT',<0.95.0>,normal}] links: [<0.93.0>,<0.5.0>] dictionary: [] trap_exit: true status: running heap_size: 233 stack_size: 23 reductions: 101 neighbours: 1> =INFO REPORT==== 3-Nov-2009::19:35:46 === application: yaws exited: {shutdown,{yaws_app,start,[normal,[]]}} type: temporary 1> |
|
From: Michal P. <mic...@er...> - 2009-11-03 11:50:07
|
Hello Eric, Yaws is using some shared libraries, such as sendfile or setuid. Those included in the tarball have been compiled under 64bit architecture: $ file setuid_drv.so setuid_drv.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped The problem is when you try to use them on different architecture. The easiest solution is to compile Yaws on your own and just replace lib/yaws-1.85 directory with your one. ----- "Eric Liang" <eri...@gm...> wrote: > Hi all, > I've just tried erlangweb, but unfortunately, the script does't work > with yaws. > > Step by stepy, I followed the erlangweb wiki: > http://wiki.erlang-web.org/Install : > > 1. ./bin/compiler.erl yaws > 2. ./bin/start.erl yaws > 3. ./bin/start_interactive yaws ---- Crash report occured here > > While the command ./bin/start_interactive (no yaws argument) can > start > inets successfully, and I can get the erlangweb-start message from my > browser. > > From the output, I guess this report will be valuable for this > problem: > > =SUPERVISOR REPORT==== 3-Nov-2009::18:19:00 === > Supervisor: {local,yaws_sup_restarts} > Context: start_error > Reason: {'EXIT',{error,could_not_load_driver}} > Offender: [{pid,undefined}, > {name,yaws_sendfile}, > {mfa,{yaws_sendfile_compat,start_link,[]}}, > {restart_type,permanent}, > {shutdown,5000}, > {child_type,worker}] > > I've tested the yaws_sendfile_compat module by calling: > yaws_sendfile_compat:start_link() in the erlang vm, it looks like > works. > > So has anyone here got this problem? or what can I do next? > If anymore information required, please let me know. btw, any > suggestions will be appreciated. > > Thanks in advance. > Eric > > ******************************************************************************************************* > The following is the whole output: > > Eshell V5.6.5 (abort with ^G) > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,sasl_safe_sup} > started: [{pid,<0.37.0>}, > {name,alarm_handler}, > {mfa,{alarm_handler,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,sasl_safe_sup} > started: [{pid,<0.38.0>}, > {name,overload}, > {mfa,{overload,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,sasl_sup} > started: [{pid,<0.36.0>}, > {name,sasl_safe_sup}, > {mfa, > {supervisor,start_link, > > [{local,sasl_safe_sup},sasl,safe]}}, > {restart_type,permanent}, > {shutdown,infinity}, > {child_type,supervisor}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,sasl_sup} > started: [{pid,<0.39.0>}, > {name,release_handler}, > {mfa,{release_handler,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > application: sasl > started_at: nonode@nohost > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,ssl_sup} > started: [{pid,<0.45.0>}, > {name,ssl_broker_sup}, > {mfa,{ssl_broker_sup,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,supervisor}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,ssl_sup} > started: [{pid,<0.46.0>}, > {name,ssl_manager}, > {mfa,{ssl_manager,start_link,[]}}, > {restart_type,permanent}, > {shutdown,4000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,ssl_sup} > started: [{pid,<0.47.0>}, > {name,ssl_connection}, > {mfa,{ssl_connection_sup,start_link,[]}}, > {restart_type,permanent}, > {shutdown,4000}, > {child_type,supervisor}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > application: ssl > started_at: nonode@nohost > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,crypto_sup} > started: [{pid,<0.52.0>}, > {name,crypto_server}, > {mfa,{crypto_server,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > application: crypto > started_at: nonode@nohost > 1> > =INFO REPORT==== 3-Nov-2009::19:35:46 === > e_lang module: error during loading file: > > "/home/sunny/codes_in_mercurial/erlang-web/config/languages/en.conf", > reason:enoent > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,kernel_safe_sup} > started: [{pid,<0.62.0>}, > {name,timer_server}, > {mfa,{timer,start_link,[]}}, > {restart_type,permanent}, > {shutdown,1000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_sup} > started: [{pid,<0.68.0>}, > {name,mnesia_event}, > {mfa,{mnesia_sup,start_event,[]}}, > {restart_type,permanent}, > {shutdown,30000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.70.0>}, > {name,mnesia_monitor}, > {mfa,{mnesia_monitor,start,[]}}, > {restart_type,permanent}, > {shutdown,3000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.71.0>}, > {name,mnesia_subscr}, > {mfa,{mnesia_subscr,start,[]}}, > {restart_type,permanent}, > {shutdown,3000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.72.0>}, > {name,mnesia_locker}, > {mfa,{mnesia_locker,start,[]}}, > {restart_type,permanent}, > {shutdown,3000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.73.0>}, > {name,mnesia_recover}, > {mfa,{mnesia_recover,start,[]}}, > {restart_type,permanent}, > {shutdown,180000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.74.0>}, > {name,mnesia_tm}, > {mfa,{mnesia_tm,start,[]}}, > {restart_type,permanent}, > {shutdown,30000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.75.0>}, > {name,mnesia_checkpoint_sup}, > {mfa,{mnesia_checkpoint_sup,start,[]}}, > {restart_type,permanent}, > {shutdown,infinity}, > {child_type,supervisor}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.76.0>}, > {name,mnesia_snmp_sup}, > {mfa,{mnesia_snmp_sup,start,[]}}, > {restart_type,permanent}, > {shutdown,infinity}, > {child_type,supervisor}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.77.0>}, > {name,mnesia_controller}, > {mfa,{mnesia_controller,start,[]}}, > {restart_type,permanent}, > {shutdown,3000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_kernel_sup} > started: [{pid,<0.78.0>}, > {name,mnesia_late_loader}, > {mfa,{mnesia_late_loader,start,[]}}, > {restart_type,permanent}, > {shutdown,3000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,mnesia_sup} > started: [{pid,<0.69.0>}, > {name,mnesia_kernel_sup}, > {mfa,{mnesia_kernel_sup,start,[]}}, > {restart_type,permanent}, > {shutdown,infinity}, > {child_type,supervisor}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > application: mnesia > started_at: nonode@nohost > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,eptic} > started: [{pid,<0.81.0>}, > {name,e_hook}, > {mfa,{e_hook,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,eptic} > started: [{pid,<0.82.0>}, > {name,e_dict}, > {mfa,{e_dict,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,eptic} > started: [{pid,<0.83.0>}, > {name,e_session}, > {mfa,{e_session,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,eptic} > started: [{pid,<0.84.0>}, > {name,e_component}, > {mfa,{e_component,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,eptic} > started: [{pid,<0.85.0>}, > {name,e_logger}, > {mfa,{e_logger,start_link,[]}}, > {restart_type,permanent}, > {shutdown,2000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > application: eptic > started_at: nonode@nohost > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > application: wpart > started_at: nonode@nohost > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > application: wparts > started_at: nonode@nohost > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,yaws_sup} > started: [{pid,<0.97.0>}, > {name,yaws_log}, > {mfa,{yaws_log,start_link,[]}}, > {restart_type,permanent}, > {shutdown,5000}, > {child_type,worker}] > 1> > =INFO REPORT==== 3-Nov-2009::19:35:46 === > Yaws: Using config file > /home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf > 1> > =INFO REPORT==== 3-Nov-2009::19:35:46 === > Ctlfile : /home/sunny/.yaws/yaws/erlangweb_test/CTL > 1> > =INFO REPORT==== 3-Nov-2009::19:35:46 === > Yaws: Listening to 0.0.0.0:8000 for <1> virtual servers: > - http://localhost:8000 under > /home/sunny/codes_in_mercurial/erlang-web/docroot > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,yaws_sup} > started: [{pid,<0.98.0>}, > {name,yaws_server}, > {mfa, > {yaws_server,start_link, > [{env,false,false,false, > {file, > > "/home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf"}, > false,false,"default"}]}}, > {restart_type,permanent}, > {shutdown,5000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,yaws_sup_restarts} > started: [{pid,<0.108.0>}, > {name,yaws_session_server}, > {mfa,{yaws_session_server,start_link,[]}}, > {restart_type,permanent}, > {shutdown,5000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,yaws_sup_restarts} > started: [{pid,<0.110.0>}, > {name,yaws_rss}, > {mfa,{yaws_rss,start_link,[]}}, > {restart_type,permanent}, > {shutdown,5000}, > {child_type,worker}] > 1> > =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === > supervisor: {local,yaws_sup_restarts} > started: [{pid,<0.111.0>}, > {name,yaws_event_manager}, > {mfa, > {gen_event,start_link, > [{local,yaws_event_manager}]}}, > {restart_type,permanent}, > {shutdown,5000}, > {child_type,worker}] > 1> > =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 === > Supervisor: {local,yaws_sup_restarts} > Context: start_error > Reason: {'EXIT',{error,could_not_load_driver}} > Offender: [{pid,undefined}, > {name,yaws_sendfile}, > {mfa,{yaws_sendfile_compat,start_link,[]}}, > {restart_type,permanent}, > {shutdown,5000}, > {child_type,worker}] > > 1> > =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 === > Supervisor: {local,yaws_sup} > Context: start_error > Reason: shutdown > Offender: [{pid,undefined}, > {name,yaws_sup_restarts}, > {mfa,{yaws_sup_restarts,start_link,[]}}, > {restart_type,transient}, > {shutdown,infinity}, > {child_type,supervisor}] > > 1> > =CRASH REPORT==== 3-Nov-2009::19:35:46 === > crasher: > pid: <0.94.0> > registered_name: [] > exception exit: {shutdown,{yaws_app,start,[normal,[]]}} > in function application_master:init/4 > initial call: application_master:init/4 > ancestors: [<0.93.0>] > messages: [{'EXIT',<0.95.0>,normal}] > links: [<0.93.0>,<0.5.0>] > dictionary: [] > trap_exit: true > status: running > heap_size: 233 > stack_size: 23 > reductions: 101 > neighbours: > 1> > =INFO REPORT==== 3-Nov-2009::19:35:46 === > application: yaws > exited: {shutdown,{yaws_app,start,[normal,[]]}} > type: temporary > 1> Best regards, -- Michal Ptaszek www.erlang-consulting.com |
|
From: Eric L. <eri...@gm...> - 2009-11-03 12:25:44
Attachments:
signature.asc
|
Michal Ptaszek wrote:
> Hello Eric,
>
> Yaws is using some shared libraries, such as sendfile or
> setuid. Those included in the tarball have been compiled
> under 64bit architecture:
> $ file setuid_drv.so
> setuid_drv.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
> dynamically linked, not stripped
>
> The problem is when you try to use them on different architecture.
> The easiest solution is to compile Yaws on your own and just replace
> lib/yaws-1.85 directory with your one.
>
>
Thanks Michal for your prompt reply.
I've checked the library file ,it is as you said. But I've already
installed yaws in my machine.
$yaws -v
yaws 1.80
$ file /usr/lib/erlang/lib/yaws-1.80/priv/lib/setuid_drv.so
/usr/lib/erlang/lib/yaws-1.80/priv/lib/setuid_drv.so: ELF 32-bit LSB
shared object, Intel 80386, version 1 (SYSV), dynamically linked,
stripped
I've tried to copy the setuid_drv.so to
ERLANG_WEB_ROOT_DIRECTORY/lib/yaws-1.85/priv/lib/ , it doesn't work.
And I've checked the yaws.conf, it looks like no configuration about how
to set the ROOT_DIRECTORY to use the yaws already installed. Do you know
how to set this? or I have to get the latest yaws-1.85? TIA.
> ----- "Eric Liang" <eri...@gm...> wrote:
>
>
>> Hi all,
>> I've just tried erlangweb, but unfortunately, the script does't work
>> with yaws.
>>
>> Step by stepy, I followed the erlangweb wiki:
>> http://wiki.erlang-web.org/Install :
>>
>> 1. ./bin/compiler.erl yaws
>> 2. ./bin/start.erl yaws
>> 3. ./bin/start_interactive yaws ---- Crash report occured here
>>
>> While the command ./bin/start_interactive (no yaws argument) can
>> start
>> inets successfully, and I can get the erlangweb-start message from my
>> browser.
>>
>> From the output, I guess this report will be valuable for this
>> problem:
>>
>> =SUPERVISOR REPORT==== 3-Nov-2009::18:19:00 ===
>> Supervisor: {local,yaws_sup_restarts}
>> Context: start_error
>> Reason: {'EXIT',{error,could_not_load_driver}}
>> Offender: [{pid,undefined},
>> {name,yaws_sendfile},
>> {mfa,{yaws_sendfile_compat,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,5000},
>> {child_type,worker}]
>>
>> I've tested the yaws_sendfile_compat module by calling:
>> yaws_sendfile_compat:start_link() in the erlang vm, it looks like
>> works.
>>
>> So has anyone here got this problem? or what can I do next?
>> If anymore information required, please let me know. btw, any
>> suggestions will be appreciated.
>>
>> Thanks in advance.
>> Eric
>>
>> *******************************************************************************************************
>> The following is the whole output:
>>
>> Eshell V5.6.5 (abort with ^G)
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,sasl_safe_sup}
>> started: [{pid,<0.37.0>},
>> {name,alarm_handler},
>> {mfa,{alarm_handler,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,sasl_safe_sup}
>> started: [{pid,<0.38.0>},
>> {name,overload},
>> {mfa,{overload,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,sasl_sup}
>> started: [{pid,<0.36.0>},
>> {name,sasl_safe_sup},
>> {mfa,
>> {supervisor,start_link,
>>
>> [{local,sasl_safe_sup},sasl,safe]}},
>> {restart_type,permanent},
>> {shutdown,infinity},
>> {child_type,supervisor}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,sasl_sup}
>> started: [{pid,<0.39.0>},
>> {name,release_handler},
>> {mfa,{release_handler,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> application: sasl
>> started_at: nonode@nohost
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,ssl_sup}
>> started: [{pid,<0.45.0>},
>> {name,ssl_broker_sup},
>> {mfa,{ssl_broker_sup,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,supervisor}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,ssl_sup}
>> started: [{pid,<0.46.0>},
>> {name,ssl_manager},
>> {mfa,{ssl_manager,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,4000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,ssl_sup}
>> started: [{pid,<0.47.0>},
>> {name,ssl_connection},
>> {mfa,{ssl_connection_sup,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,4000},
>> {child_type,supervisor}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> application: ssl
>> started_at: nonode@nohost
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,crypto_sup}
>> started: [{pid,<0.52.0>},
>> {name,crypto_server},
>> {mfa,{crypto_server,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> application: crypto
>> started_at: nonode@nohost
>> 1>
>> =INFO REPORT==== 3-Nov-2009::19:35:46 ===
>> e_lang module: error during loading file:
>>
>> "/home/sunny/codes_in_mercurial/erlang-web/config/languages/en.conf",
>> reason:enoent
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,kernel_safe_sup}
>> started: [{pid,<0.62.0>},
>> {name,timer_server},
>> {mfa,{timer,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,1000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_sup}
>> started: [{pid,<0.68.0>},
>> {name,mnesia_event},
>> {mfa,{mnesia_sup,start_event,[]}},
>> {restart_type,permanent},
>> {shutdown,30000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.70.0>},
>> {name,mnesia_monitor},
>> {mfa,{mnesia_monitor,start,[]}},
>> {restart_type,permanent},
>> {shutdown,3000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.71.0>},
>> {name,mnesia_subscr},
>> {mfa,{mnesia_subscr,start,[]}},
>> {restart_type,permanent},
>> {shutdown,3000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.72.0>},
>> {name,mnesia_locker},
>> {mfa,{mnesia_locker,start,[]}},
>> {restart_type,permanent},
>> {shutdown,3000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.73.0>},
>> {name,mnesia_recover},
>> {mfa,{mnesia_recover,start,[]}},
>> {restart_type,permanent},
>> {shutdown,180000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.74.0>},
>> {name,mnesia_tm},
>> {mfa,{mnesia_tm,start,[]}},
>> {restart_type,permanent},
>> {shutdown,30000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.75.0>},
>> {name,mnesia_checkpoint_sup},
>> {mfa,{mnesia_checkpoint_sup,start,[]}},
>> {restart_type,permanent},
>> {shutdown,infinity},
>> {child_type,supervisor}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.76.0>},
>> {name,mnesia_snmp_sup},
>> {mfa,{mnesia_snmp_sup,start,[]}},
>> {restart_type,permanent},
>> {shutdown,infinity},
>> {child_type,supervisor}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.77.0>},
>> {name,mnesia_controller},
>> {mfa,{mnesia_controller,start,[]}},
>> {restart_type,permanent},
>> {shutdown,3000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_kernel_sup}
>> started: [{pid,<0.78.0>},
>> {name,mnesia_late_loader},
>> {mfa,{mnesia_late_loader,start,[]}},
>> {restart_type,permanent},
>> {shutdown,3000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,mnesia_sup}
>> started: [{pid,<0.69.0>},
>> {name,mnesia_kernel_sup},
>> {mfa,{mnesia_kernel_sup,start,[]}},
>> {restart_type,permanent},
>> {shutdown,infinity},
>> {child_type,supervisor}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> application: mnesia
>> started_at: nonode@nohost
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,eptic}
>> started: [{pid,<0.81.0>},
>> {name,e_hook},
>> {mfa,{e_hook,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,eptic}
>> started: [{pid,<0.82.0>},
>> {name,e_dict},
>> {mfa,{e_dict,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,eptic}
>> started: [{pid,<0.83.0>},
>> {name,e_session},
>> {mfa,{e_session,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,eptic}
>> started: [{pid,<0.84.0>},
>> {name,e_component},
>> {mfa,{e_component,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,eptic}
>> started: [{pid,<0.85.0>},
>> {name,e_logger},
>> {mfa,{e_logger,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,2000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> application: eptic
>> started_at: nonode@nohost
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> application: wpart
>> started_at: nonode@nohost
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> application: wparts
>> started_at: nonode@nohost
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,yaws_sup}
>> started: [{pid,<0.97.0>},
>> {name,yaws_log},
>> {mfa,{yaws_log,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,5000},
>> {child_type,worker}]
>> 1>
>> =INFO REPORT==== 3-Nov-2009::19:35:46 ===
>> Yaws: Using config file
>> /home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf
>> 1>
>> =INFO REPORT==== 3-Nov-2009::19:35:46 ===
>> Ctlfile : /home/sunny/.yaws/yaws/erlangweb_test/CTL
>> 1>
>> =INFO REPORT==== 3-Nov-2009::19:35:46 ===
>> Yaws: Listening to 0.0.0.0:8000 for <1> virtual servers:
>> - http://localhost:8000 under
>> /home/sunny/codes_in_mercurial/erlang-web/docroot
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,yaws_sup}
>> started: [{pid,<0.98.0>},
>> {name,yaws_server},
>> {mfa,
>> {yaws_server,start_link,
>> [{env,false,false,false,
>> {file,
>>
>> "/home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf"},
>> false,false,"default"}]}},
>> {restart_type,permanent},
>> {shutdown,5000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,yaws_sup_restarts}
>> started: [{pid,<0.108.0>},
>> {name,yaws_session_server},
>> {mfa,{yaws_session_server,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,5000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,yaws_sup_restarts}
>> started: [{pid,<0.110.0>},
>> {name,yaws_rss},
>> {mfa,{yaws_rss,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,5000},
>> {child_type,worker}]
>> 1>
>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 ===
>> supervisor: {local,yaws_sup_restarts}
>> started: [{pid,<0.111.0>},
>> {name,yaws_event_manager},
>> {mfa,
>> {gen_event,start_link,
>> [{local,yaws_event_manager}]}},
>> {restart_type,permanent},
>> {shutdown,5000},
>> {child_type,worker}]
>> 1>
>> =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 ===
>> Supervisor: {local,yaws_sup_restarts}
>> Context: start_error
>> Reason: {'EXIT',{error,could_not_load_driver}}
>> Offender: [{pid,undefined},
>> {name,yaws_sendfile},
>> {mfa,{yaws_sendfile_compat,start_link,[]}},
>> {restart_type,permanent},
>> {shutdown,5000},
>> {child_type,worker}]
>>
>> 1>
>> =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 ===
>> Supervisor: {local,yaws_sup}
>> Context: start_error
>> Reason: shutdown
>> Offender: [{pid,undefined},
>> {name,yaws_sup_restarts},
>> {mfa,{yaws_sup_restarts,start_link,[]}},
>> {restart_type,transient},
>> {shutdown,infinity},
>> {child_type,supervisor}]
>>
>> 1>
>> =CRASH REPORT==== 3-Nov-2009::19:35:46 ===
>> crasher:
>> pid: <0.94.0>
>> registered_name: []
>> exception exit: {shutdown,{yaws_app,start,[normal,[]]}}
>> in function application_master:init/4
>> initial call: application_master:init/4
>> ancestors: [<0.93.0>]
>> messages: [{'EXIT',<0.95.0>,normal}]
>> links: [<0.93.0>,<0.5.0>]
>> dictionary: []
>> trap_exit: true
>> status: running
>> heap_size: 233
>> stack_size: 23
>> reductions: 101
>> neighbours:
>> 1>
>> =INFO REPORT==== 3-Nov-2009::19:35:46 ===
>> application: yaws
>> exited: {shutdown,{yaws_app,start,[normal,[]]}}
>> type: temporary
>> 1>
>>
>
> Best regards,
>
|
|
From: Ludovic K. <ma...@ku...> - 2009-11-03 13:14:36
|
Hi, I had the exact same problem and compiling it for my architecture just worked. Here is what I did: $ wget http://yaws.hyber.org/download/yaws-1.85.tar.gz $ tar xfz yaws-1.85.tar.gz $ cd yaws $ ./configure $ make $ ls ../erlangweb-1.4/lib/yaws-1.85/ $ cd .. $ cd erlangweb-1.4 $ cd lib/ $ cd yaws-1.85/ $ rm -rf ebin/ $ rm -rf include/ $ rm -rf priv/ $ cp -r ../../../yaws/ebin/ . $ cp -r ../../../yaws/include . $ cp -r ../../../yaws/priv . $ cd .. $ cd .. $ bin/start.erl yaws (EXTRA STEP. MAYBE NOT NECESSARY) $ bin/start_interactive yaws Eric, I didn't have a previous Yaws installation but compiled it from scratch. Maybe that made a difference compared to your setup. Hope that helps. On 3 Nov 2009, at 13:19, Eric Liang wrote: > Michal Ptaszek wrote: >> >> Hello Eric, >> >> Yaws is using some shared libraries, such as sendfile or >> setuid. Those included in the tarball have been compiled >> under 64bit architecture: >> $ file setuid_drv.so >> setuid_drv.so: ELF 64-bit LSB shared object, x86-64, version 1 >> (SYSV), >> dynamically linked, not stripped >> >> The problem is when you try to use them on different architecture. >> The easiest solution is to compile Yaws on your own and just replace >> lib/yaws-1.85 directory with your one. >> >> > Thanks Michal for your prompt reply. > > I've checked the library file ,it is as you said. But I've already > installed yaws in my machine. > > $yaws -v > yaws 1.80 > > $ file /usr/lib/erlang/lib/yaws-1.80/priv/lib/setuid_drv.so > /usr/lib/erlang/lib/yaws-1.80/priv/lib/setuid_drv.so: ELF 32-bit LSB > shared object, Intel 80386, version 1 (SYSV), dynamically linked, > stripped > I've tried to copy the setuid_drv.so to ERLANG_WEB_ROOT_DIRECTORY/ > lib/yaws-1.85/priv/lib/ , it doesn't work. > And I've checked the yaws.conf, it looks like no configuration about > how to set the ROOT_DIRECTORY to use the yaws already installed. Do > you know how to set this? or I have to get the latest yaws-1.85? TIA. > >> ----- "Eric Liang" <eri...@gm...> wrote: >> >> >>> Hi all, >>> I've just tried erlangweb, but unfortunately, the script does't work >>> with yaws. >>> >>> Step by stepy, I followed the erlangweb wiki: >>> http://wiki.erlang-web.org/Install : >>> >>> 1. ./bin/compiler.erl yaws >>> 2. ./bin/start.erl yaws >>> 3. ./bin/start_interactive yaws ---- Crash report occured here >>> >>> While the command ./bin/start_interactive (no yaws argument) can >>> start >>> inets successfully, and I can get the erlangweb-start message from >>> my >>> browser. >>> >>> From the output, I guess this report will be valuable for this >>> problem: >>> >>> =SUPERVISOR REPORT==== 3-Nov-2009::18:19:00 === >>> Supervisor: {local,yaws_sup_restarts} >>> Context: start_error >>> Reason: {'EXIT',{error,could_not_load_driver}} >>> Offender: [{pid,undefined}, >>> {name,yaws_sendfile}, >>> {mfa,{yaws_sendfile_compat,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >>> >>> I've tested the yaws_sendfile_compat module by calling: >>> yaws_sendfile_compat:start_link() in the erlang vm, it looks like >>> works. >>> >>> So has anyone here got this problem? or what can I do next? >>> If anymore information required, please let me know. btw, any >>> suggestions will be appreciated. >>> >>> Thanks in advance. >>> Eric >>> >>> ******************************************************************************************************* >>> The following is the whole output: >>> >>> Eshell V5.6.5 (abort with ^G) >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,sasl_safe_sup} >>> started: [{pid,<0.37.0>}, >>> {name,alarm_handler}, >>> {mfa,{alarm_handler,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,sasl_safe_sup} >>> started: [{pid,<0.38.0>}, >>> {name,overload}, >>> {mfa,{overload,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,sasl_sup} >>> started: [{pid,<0.36.0>}, >>> {name,sasl_safe_sup}, >>> {mfa, >>> {supervisor,start_link, >>> >>> [{local,sasl_safe_sup},sasl,safe]}}, >>> {restart_type,permanent}, >>> {shutdown,infinity}, >>> {child_type,supervisor}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,sasl_sup} >>> started: [{pid,<0.39.0>}, >>> {name,release_handler}, >>> {mfa,{release_handler,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> application: sasl >>> started_at: nonode@nohost >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,ssl_sup} >>> started: [{pid,<0.45.0>}, >>> {name,ssl_broker_sup}, >>> {mfa,{ssl_broker_sup,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,supervisor}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,ssl_sup} >>> started: [{pid,<0.46.0>}, >>> {name,ssl_manager}, >>> {mfa,{ssl_manager,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,4000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,ssl_sup} >>> started: [{pid,<0.47.0>}, >>> {name,ssl_connection}, >>> {mfa,{ssl_connection_sup,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,4000}, >>> {child_type,supervisor}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> application: ssl >>> started_at: nonode@nohost >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,crypto_sup} >>> started: [{pid,<0.52.0>}, >>> {name,crypto_server}, >>> {mfa,{crypto_server,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> application: crypto >>> started_at: nonode@nohost >>> 1> >>> =INFO REPORT==== 3-Nov-2009::19:35:46 === >>> e_lang module: error during loading file: >>> >>> "/home/sunny/codes_in_mercurial/erlang-web/config/languages/ >>> en.conf", >>> reason:enoent >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,kernel_safe_sup} >>> started: [{pid,<0.62.0>}, >>> {name,timer_server}, >>> {mfa,{timer,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,1000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_sup} >>> started: [{pid,<0.68.0>}, >>> {name,mnesia_event}, >>> {mfa,{mnesia_sup,start_event,[]}}, >>> {restart_type,permanent}, >>> {shutdown,30000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.70.0>}, >>> {name,mnesia_monitor}, >>> {mfa,{mnesia_monitor,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,3000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.71.0>}, >>> {name,mnesia_subscr}, >>> {mfa,{mnesia_subscr,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,3000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.72.0>}, >>> {name,mnesia_locker}, >>> {mfa,{mnesia_locker,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,3000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.73.0>}, >>> {name,mnesia_recover}, >>> {mfa,{mnesia_recover,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,180000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.74.0>}, >>> {name,mnesia_tm}, >>> {mfa,{mnesia_tm,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,30000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.75.0>}, >>> {name,mnesia_checkpoint_sup}, >>> {mfa,{mnesia_checkpoint_sup,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,infinity}, >>> {child_type,supervisor}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.76.0>}, >>> {name,mnesia_snmp_sup}, >>> {mfa,{mnesia_snmp_sup,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,infinity}, >>> {child_type,supervisor}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.77.0>}, >>> {name,mnesia_controller}, >>> {mfa,{mnesia_controller,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,3000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_kernel_sup} >>> started: [{pid,<0.78.0>}, >>> {name,mnesia_late_loader}, >>> {mfa,{mnesia_late_loader,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,3000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,mnesia_sup} >>> started: [{pid,<0.69.0>}, >>> {name,mnesia_kernel_sup}, >>> {mfa,{mnesia_kernel_sup,start,[]}}, >>> {restart_type,permanent}, >>> {shutdown,infinity}, >>> {child_type,supervisor}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> application: mnesia >>> started_at: nonode@nohost >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,eptic} >>> started: [{pid,<0.81.0>}, >>> {name,e_hook}, >>> {mfa,{e_hook,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,eptic} >>> started: [{pid,<0.82.0>}, >>> {name,e_dict}, >>> {mfa,{e_dict,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,eptic} >>> started: [{pid,<0.83.0>}, >>> {name,e_session}, >>> {mfa,{e_session,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,eptic} >>> started: [{pid,<0.84.0>}, >>> {name,e_component}, >>> {mfa,{e_component,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,eptic} >>> started: [{pid,<0.85.0>}, >>> {name,e_logger}, >>> {mfa,{e_logger,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,2000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> application: eptic >>> started_at: nonode@nohost >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> application: wpart >>> started_at: nonode@nohost >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> application: wparts >>> started_at: nonode@nohost >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,yaws_sup} >>> started: [{pid,<0.97.0>}, >>> {name,yaws_log}, >>> {mfa,{yaws_log,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >>> 1> >>> =INFO REPORT==== 3-Nov-2009::19:35:46 === >>> Yaws: Using config file >>> /home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf >>> 1> >>> =INFO REPORT==== 3-Nov-2009::19:35:46 === >>> Ctlfile : /home/sunny/.yaws/yaws/erlangweb_test/CTL >>> 1> >>> =INFO REPORT==== 3-Nov-2009::19:35:46 === >>> Yaws: Listening to 0.0.0.0:8000 for <1> virtual servers: >>> - http://localhost:8000 under >>> /home/sunny/codes_in_mercurial/erlang-web/docroot >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,yaws_sup} >>> started: [{pid,<0.98.0>}, >>> {name,yaws_server}, >>> {mfa, >>> {yaws_server,start_link, >>> [{env,false,false,false, >>> {file, >>> >>> "/home/sunny/codes_in_mercurial/erlang-web/config/yaws.conf"}, >>> false,false,"default"}]}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,yaws_sup_restarts} >>> started: [{pid,<0.108.0>}, >>> {name,yaws_session_server}, >>> {mfa,{yaws_session_server,start_link, >>> []}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,yaws_sup_restarts} >>> started: [{pid,<0.110.0>}, >>> {name,yaws_rss}, >>> {mfa,{yaws_rss,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >>> 1> >>> =PROGRESS REPORT==== 3-Nov-2009::19:35:46 === >>> supervisor: {local,yaws_sup_restarts} >>> started: [{pid,<0.111.0>}, >>> {name,yaws_event_manager}, >>> {mfa, >>> {gen_event,start_link, >>> [{local,yaws_event_manager}]}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >>> 1> >>> =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 === >>> Supervisor: {local,yaws_sup_restarts} >>> Context: start_error >>> Reason: {'EXIT',{error,could_not_load_driver}} >>> Offender: [{pid,undefined}, >>> {name,yaws_sendfile}, >>> {mfa,{yaws_sendfile_compat,start_link,[]}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >>> >>> 1> >>> =SUPERVISOR REPORT==== 3-Nov-2009::19:35:46 === >>> Supervisor: {local,yaws_sup} >>> Context: start_error >>> Reason: shutdown >>> Offender: [{pid,undefined}, >>> {name,yaws_sup_restarts}, >>> {mfa,{yaws_sup_restarts,start_link,[]}}, >>> {restart_type,transient}, >>> {shutdown,infinity}, >>> {child_type,supervisor}] >>> >>> 1> >>> =CRASH REPORT==== 3-Nov-2009::19:35:46 === >>> crasher: >>> pid: <0.94.0> >>> registered_name: [] >>> exception exit: {shutdown,{yaws_app,start,[normal,[]]}} >>> in function application_master:init/4 >>> initial call: application_master:init/4 >>> ancestors: [<0.93.0>] >>> messages: [{'EXIT',<0.95.0>,normal}] >>> links: [<0.93.0>,<0.5.0>] >>> dictionary: [] >>> trap_exit: true >>> status: running >>> heap_size: 233 >>> stack_size: 23 >>> reductions: 101 >>> neighbours: >>> 1> >>> =INFO REPORT==== 3-Nov-2009::19:35:46 === >>> application: yaws >>> exited: {shutdown,{yaws_app,start,[normal,[]]}} >>> type: temporary >>> 1> >>> >> >> Best regards, >> > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference_______________________________________________ > Erlangweb-users mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlangweb-users > http://www.erlang-web.org/ |
|
From: Eric L. <eri...@gm...> - 2009-11-04 07:29:24
Attachments:
signature.asc
|
Ludovic Kuty wrote: > Hi, > > I had the exact same problem and compiling it for my architecture just > worked. > > Here is what I did: > > $ wget http://yaws.hyber.org/download/yaws-1.85.tar.gz > $ tar xfz yaws-1.85.tar.gz > $ cd yaws > $ ./configure > $ make > $ ls ../erlangweb-1.4/lib/yaws-1.85/ > $ cd .. > $ cd erlangweb-1.4 > $ cd lib/ > $ cd yaws-1.85/ > $ rm -rf ebin/ > $ rm -rf include/ > $ rm -rf priv/ > $ cp -r ../../../yaws/ebin/ . > $ cp -r ../../../yaws/include . > $ cp -r ../../../yaws/priv . > $ cd .. > $ cd .. > $ bin/start.erl yaws (EXTRA STEP. MAYBE NOT NECESSARY) > $ bin/start_interactive yaws > > Eric, I didn't have a previous Yaws installation but compiled it from > scratch. Maybe that made a difference compared to your setup. > > Hope that helps. Thanks, Ludovic, it enlightens me. So I checked the private libraries Michal said before, and found that simply copy all of them looks solved this: $cp /usr/lib/erlang/lib/yaws-1.80/priv/lib/*.so ERLANG_WEB_SOURCE_ROOT/lib/yaws-1.85/priv/lib This is because all the private libraries in priv directory are architecture specified. As indicated in the command, the yaws in my machine is not version 1.85 but 1.80. Since from the source codes of yaws, related yaws_sendfile.erl have changed several times after tag 1.80, and yaws would look up the priv directory by -- ebin/../priv --, I prefer using totally 1.80(the pre-installed version), so I : 1 modify the script: ./bin/start_interactive, change the last line to: erl -pa lib/*/ebin -pa /usr/lib/erlang/lib/yaws-1.80/ebin -s e_start start $NODE_TYPE $SERVER $@ 2 modify the config file: ./config/yaws.conf, change the ebin_dir and include_dir configration(for sanity): ebin_dir = /usr/lib/erlang/lib/yaws-1.80/ebin include_dir = /usr/lib/erlang/lib/yaws-1.80/include I works very well now. :D Thanks for both of you again. Eric > > On 3 Nov 2009, at 13:19, Eric Liang wrote: > >> Michal Ptaszek wrote: >>> Hello Eric, >>> >>> Yaws is using some shared libraries, such as sendfile or >>> setuid. Those included in the tarball have been compiled >>> under 64bit architecture: >>> $ file setuid_drv.so >>> setuid_drv.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), >>> dynamically linked, not stripped >>> >>> The problem is when you try to use them on different architecture. >>> The easiest solution is to compile Yaws on your own and just replace >>> lib/yaws-1.85 directory with your one. >>> >>> >> Thanks Michal for your prompt reply. >> >> I've checked the library file ,it is as you said. But I've already >> installed yaws in my machine. >> >> $yaws -v >> yaws 1.80 >> >> $ file /usr/lib/erlang/lib/yaws-1.80/priv/lib/setuid_drv.so >> /usr/lib/erlang/lib/yaws-1.80/priv/lib/setuid_drv.so: ELF 32-bit >> LSB shared object, Intel 80386, version 1 (SYSV), dynamically >> linked, stripped >> >> I've tried to copy the setuid_drv.so to >> ERLANG_WEB_ROOT_DIRECTORY/lib/yaws-1.85/priv/lib/ , it doesn't work. >> And I've checked the yaws.conf, it looks like no configuration about >> how to set the ROOT_DIRECTORY to use the yaws already installed. Do >> you know how to set this? or I have to get the latest yaws-1.85? TIA. >> >>> ----- "Eric Liang" <eri...@gm...> wrote: >>> >>> >>>> Hi all, >>>> I've just tried erlangweb, but unfortunately, the script does't work >>>> with yaws. >>>> >>>> Step by stepy, I followed the erlangweb wiki: >>>> http://wiki.erlang-web.org/Install : >>>> >>>> 1. ./bin/compiler.erl yaws >>>> 2. ./bin/start.erl yaws >>>> 3. ./bin/start_interactive yaws ---- Crash report occured here >>>> >>>> While the command ./bin/start_interactive (no yaws argument) can >>>> start >>>> inets successfully, and I can get the erlangweb-start message from my >>>> browser. >>>> >>>> From the output, I guess this report will be valuable for this >>>> problem: >>>> >>>> =SUPERVISOR REPORT==== 3-Nov-2009::18:19:00 === >>>> Supervisor: {local,yaws_sup_restarts} >>>> Context: start_error >>>> Reason: {'EXIT',{error,could_not_load_driver}} >>>> Offender: [{pid,undefined}, >>>> {name,yaws_sendfile}, >>>> {mfa,{yaws_sendfile_compat,start_link,[]}}, >>>> {restart_type,permanent}, >>>> {shutdown,5000}, >>>> {child_type,worker}] >>>> >>>> I've tested the yaws_sendfile_compat module by calling: >>>> yaws_sendfile_compat:start_link() in the erlang vm, it looks like >>>> works. >>>> >>>> So has anyone here got this problem? or what can I do next? >>>> If anymore information required, please let me know. btw, any >>>> suggestions will be appreciated. >>>> >>>> Thanks in advance. >>>> Eric >>>> >>> >>> Best regards, >>> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and >> stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference_______________________________________________ >> Erlangweb-users mailing list >> Erl...@li... >> https://lists.sourceforge.net/lists/listinfo/erlangweb-users >> http://www.erlang-web.org/ > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > ------------------------------------------------------------------------ > > _______________________________________________ > Erlangweb-users mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlangweb-users > http://www.erlang-web.org/ |
Thanks for helping keep SourceForge clean.
X