From: Joshua B. <jd...@jd...> - 2006-07-11 00:18:54
|
I'm trying to set up yaws 1.63 on erlang rb11b-0 on a Linux From Scratch 6.1 system (running on a Pentium 4 from a CF card) for an embedded project that I'm working on. I built erlang and yaws in a chroot environment on a Ubuntu 6.06 workstation, then copied the destination directories (I used /opt/otp_rb11b-0 and /opt/yaws-1.63) to the flash card. I had to modify the /opt/yaws-1.63/bin/yaws script since I don't have the which program (and it was easy enough to just put the path for env in the file). I modified the conf file to get rid of the SSL server instance (while I build erlang with SSL support, I don't need it for at least the first version of my application). Now, when I try to start the server, I get: -bash-3.00# /opt/yaws-1.63/bin/yaws -i Erlang (BEAM) emulator version 5.5 [source] [async-threads:0] [hipe] Eshell V5.5 (abort with ^G) 1> =INFO REPORT==== 11-Jul-2006::00:11:55 === Yaws: Using config file /opt/yaws-1.63/etc/yaws.conf yaws:Add path "/opt/yaws-1.63/lib/yaws/examples/ebin" yaws:Add path "/opt/yaws-1.63/lib/yaws/examples/ebin" yaws:Running with id=default Running with debug checks turned on (slower server) Logging to directory "/opt/yaws-1.63/var/log/yaws" =ERROR REPORT==== 11-Jul-2006::00:11:55 === Cannot listen on ctl socket, fatal: {error,eaddrnotavail} =INFO REPORT==== 11-Jul-2006::00:11:55 === 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,[]]}}}) -bash-3.00# Is anyone familar with what is misconfigured to cause the eaddrnotavail problem? OpenSSH is running on the machine just fine. -- Joshua D. Boyd jd...@jd... http://www.jdboyd.net/ http://www.joshuaboyd.org/ |