Published sinan 0.10.0.2. This should solve a couple of problems,
including Tobbe's.
Thanks,
Eric
So this logic works as follows.
Client tries to connect to server. If client cannot connect it tries
to start up server. Then it waits 2 seconds for server to start and
tries reconnecting. If that reconnect fails it will error with the
above connection failure.
There are a couple of possible problems here. Its possible that the
service is taking more then 2 seconds to start up. Its also possible
that the server isn't starting correctly and dieing. Though thats less
probable considering that I check for that outcome.
The server side uses crary and all that code is in sinan_web_api. That
should provide you with a place to look. The client logic is in the
client area in the sinan script.
Try running /usr/local/erlware/bin/sinserv. That should startup and
run in detached mode. If that works take a look at the logs in
~/.sinan/logs/kernel.log to see if something else may be wrong. It
could be that its just taking longer then 2 seconds to start. I may
need to make that smarter.
I don't know what this is off the top of my head. I will take a look
at it tonight.
Everything in _build should be wiped by the clean command.
I will get these problems fixed tonight and get out 0.10.0.3.
You are not being a pain. These are all issues that need to be worked
out. It looks like you are trying to load beam code from a newer
version of erts into an old version of erts. Off the top of my head I
can't imagine why this would happen.
Oh! I know. Do a faxien upgrade-release erl. I think that will solve
your problem.
We really need to think about package gruops in erlware.
sRp
Yes, It does that on non existing command names. Which of
course is not very nice.
/Anders
Thanks,
Eric