|
|
| Author |
Message |
|
| Guest |
 Posted: Thu Jul 19, 2007 5:52 pm |
 |
|
|
Guest
|
We have been testing a system with several Erlang nodes running yaws
for recovery from various failures. We do such rude things to the
system as rebooting servers while they are running and halting nodes
which are then restarted from /etc/inittab. Yaws is a huge win, BTW -
our toolchain now generates standard status and control pages for all
Erlang apps.
In some 50 or so restarts of this nature, we have seen two instances
where a node refuses to start, exiting with the message
=ERROR REPORT==== 16-Jul-2007::17:40:26 ===
There is already a yaws system running with the same
id <"some_id"> on this computer,
set another id in the yaws conf file
We checked when this happens, and there is no other yaws instance
running. Work-around is to remove the .../var/run/yaws/ctl-<id> file
and restart.
Probably what is happening is that something else is able to start
listening on the previous yaws control port since the ctl- file was
written and the old yaws instance died.
This has a consequence for high-availability systems in that
occasionally unattended restart fails.
This is with Erlang R11B-5 and yaws-1.68.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
