On Saturday 06 September 2008 20:19:10 you wrote:
> On Sun, Sep 7, 2008 at 12:34 AM, Chris Warburton
>
> <[EMAIL PROTECTED]> wrote:
> > ejabberd and ejabberdctl do not start properly, they seem to hang. This
> > happens when trying to install and remove the package also. Using Ctrl-C
> > brings up the following menu (I assume thanks to Erlang):
> >
> > {error_logger,{{2008,9,6},{20,29,5}},"Protocol: ~p: register error:
> > ~p~n",["inet_tcp",{{badmatch,{error,etimedout}},[{inet_tcp_dist,listen,1}
> >,
>
> This likely means that erlang node cannot connect to epmd (erlang
> portmap daemon) on start. epmd should be started during ejabberd start
> and should listen at port 4369.
>
> So, either epmd haven't started (look at processes list), or there is
> a firewall which doesn't allow ejabberd to connect to port 4369. Or
> there might be a resolver issue where erlang node incorrectly resolves
> its own hostname. Or there mighn be something I still don't know.
>
> Could you check if epmd is running and if there are firewall or
> resolver problems.I think I've found the issue, it was network based and after some investigation it turns out that I hadn't added a loopback interface to /etc/network/interfaces (I installed this system minimally via debootstrap, so it wasn't done automatically). I've added one, done ifup lo and now ejabberd works :-D Thanks for the response and for pointing me in the right direction to fix this. I understand this bug is invalid, but I'm sorry I don't know how to close it myself. Thanks, Chris Warburton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
