On Fri, Nov 15, 2013 at 6:14 PM, Chris Pine <chris@pine.fm> wrote:
> What version of Yaws are you running?

I don't even know how to find this out... I set all of this up 5 years
ago, and don't use Erlang very much anymore, so I'm having to relearn
a lot of this. [blush]

You should be able to run

yaws --version

from your command line to obtain the version. 

> This error message results from not being able to run the yaws_ctl subsystem. Are the various files under your $HOME/.yaws directory writeable and are the directories under there navigable/traversable?

They all look fine to me.


> Have you tried running yaws with the -i option to start up an interactive instance? It might show you more error output.

$ erl -mnesia dir '"../db"' -pa /opt/local/lib/yaws/ebin -yaws -run
yaws -yaws conf '"../yaws.conf"' -i
Erlang R15B01 (erts-5.9.1) [source] [smp:8:8] [async-threads:0]
[kernel-poll:false] [dtrace]

Eshell V5.9.1  (abort with ^G)
1>
=INFO REPORT==== 15-Nov-2013::23:09:07 ===
Yaws: Using config file ../yaws.conf

=ERROR REPORT==== 15-Nov-2013::23:09:07 ===
'auth_log' global variable is deprecated and ignored. it is now a
per-server variable
=ERROR REPORT==== 15-Nov-2013::23:09:07 ===
ERROR: "Failed to start: ~s~n" - [{case_clause,
                                                            {ok,[]}}]


Under your $HOME/.yaws directory do you have a file named CTL, and if so, is it 0-length? If so, try deleting that file and then restarting Yaws.

Also, I have another question: are you aware of anything that changed recently on your host to cause your installation to stop working?

--steve