Date: Wed, 17 Nov 2010 14:34:00 +0100 From: "tom@diogunix.com" <tom@diogunix.com> To: Panagiotis Christias <christias@gmail.com>, freebsd-questions@freebsd.org, ashish@freebsd.org Subject: Re: ejabberd won't startup Message-ID: <201011171434.01831.tom@diogunix.com> In-Reply-To: <AANLkTikr_81RkpUXNrTZoMxZ%2B_=OAHmqHQZzNU3Mn7sp@mail.gmail.com> References: <201011170535.46151.tom@diogunix.com> <AANLkTikr_81RkpUXNrTZoMxZ%2B_=OAHmqHQZzNU3Mn7sp@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
update on the issue with Jails and Erlang 14B: > > Hi everybody dealing with ejabberd and/or erlang in a FreeBSD8-Jail ! > >=20 > > I've built the ejabberd port (with ODBC support / the Erlang MySQL > > driver) two days ago but can't get it to run. > >=20 > > # ejabberdctl start > >=20 > > spits out a huge bunch of Erlang error messages (unreadable for most > > humans), obviously saying that it can't connect properly to the > > loopback interface on Port 4369 (respectively connects but then > > immediately stops, causing a crash dump and not able to "register it's > > node"). Tcpdump shows 8 pakets captured when pointing to the lo0 > > interface. > >=20 > > The jail is an ordinary Jail with no special configuration (just 1 IP > > and a proper hostname, running Postfix/Dovecot with MySQL just fine). > > PF or it's ruleset too seems not to be the cause as Erlang's behaviour > > is the same even with a switched off PF. Restarting the Jail and > > triple-checking it's parameters did not help too. > >=20 > > As the error can be reproduced solely with Erlang (without even > > starting ejabberd), the ejabberd.cfg file however does not seem to > > play any role. > >=20 > > I was told, this actually was an Erlang issue and so I first went to > > the Erlang folks (erlang mailing list). At least until now, they > > unfortunately could not help me making a real step. > >=20 > > So, I got stuck and now am in search for people successfully running > > ejabberd in a Jail. I have seen reports from the web on success and > > even I too had a test installation in a Jail running half a year ago > > (unfortunately did not note all details before I wiped that testing > > machine). > >=20 > > My suggestion is, it might have something to do with the file > > /usr/locaal/etc/ejabberd/inetrc > > (responsible for name resolution for Erlang) > >=20 > > So, are there any Jail/ejabberd experts out there ? > > Or just people having it up and running ? >=20 > Hello, >=20 > I believe we are facing the same issue. Our setup is ejabberd-2.1.5 in > a FreeBSD 7.3 amd64 jail and the workaround we found is running an > older version of erlang (erlang-r13b04_3,1). You can find the old > erlang port files in the FreeBSD CVS repository or here: >=20 > http://noc.ntua.gr/~christia/erlang.tgz >=20 > Regards, > Panagiotis I experienced the phenomenon with Erlang 14B: # erl Erlang R14B (erts-5.8.1) [source] [smp:4:4] [rq:4] [async-threads:0] [hipe]= =20 [kernel-poll:false] Eshell V5.8.1 The error message then is: > ejabberd Start: >=20 > # ejabberdctl status > {error_logger,{{2010,11,16},{9,56,20}},"Protocol: ~p: register error:=20 ~p~n", > ["inet_tcp",{{badmatch,{error,epmd_close}},[{inet_tcp_dist,listen,1}, but the same pops up when just starting up an Erlang node without any=20 ejabberd. =46rom the Erlang mailing list I learned: "epmd in R14B was changed to allow some messages (like name registrations) only from 127/8. " So, this might explain why there are those problems with the new Erlang in = a=20 Jail. The most recent report of a working Erlang/ejabberd in a Jail I have found= =20 via Google is from around Janary 2010.=20 So, if there is no newer positiv experience with Erlang 14B in a Jail it=20 might be a good idea to provide a Port for ejabberd with an older Erlang. But still I'm not sure whether or not it is possible to get Erlang 14B to=20 run in a Jail. Any further hints / ideas out there ? Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011171434.01831.tom>