Hi, FYI, I also met this problem. Granted, in my case it was my slip-up while setting a too restrictive iptables ruleset that didn't allow loopback connections, but at any rate this is kind of hard to debug for people with no erlang background.
Perhaps it could be interesting to avoid this bug popping up again by adding some suggestions to an error message in the init script, for instance warning about the need for a certain connectivity on start-up time? Cheers -- Leo "costela" Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
