ejabberd - Comments for "FreeBSD 5.4 + ejabberd 1.1.1 -> can't start"

Here are the notes from my FreeBSD 6.1 install

dotdash — Thu, 17 Aug 2006 20:08:30 +0000

http://www.ejabberd.im/node/894#comment-1958
I have some notes on setting up jwchat, etc if you get stuck...

I used gmake instead of make. It worked now.

breakevilaxis — Thu, 17 Aug 2006 18:21:24 +0000

Also in the starter script, if I do not put -detached, it won't work. Then I put -detached, it works now.

I can http://:5280/admin, but I can never make a connect using Exodus.

I am making JWChat. I wish jwchat will solve some connection problem for me.

Re: Can you tell me how to compile ejabberd1.1.1 on freebsd?

sander — Thu, 17 Aug 2006 08:06:09 +0000

breakevilaxis wrote:

I cannot compile ejabberd 1.1.1 on FreeBSD 6.1.

It works great here with the FreeBSD ports. Try to install erlang-lite instead of the erlang port, this compiles much more smoothly and you don't need the bloat of the erlang port.

Can you tell me how to compile ejabberd1.1.1 on freebsd?

breakevilaxis — Thu, 17 Aug 2006 03:29:56 +0000

I cannot compile ejabberd 1.1.1 on FreeBSD 6.1.

Freebsd + ejabberd 1.1.1 cant' start - solution :)

mkowalik — Thu, 18 May 2006 13:48:17 +0000

Hello.

Perhaps someone will have similiar problem - solution was extremaly easy.. Actually, so easy, that it's a shame to say it...

The problem was, that lo0, the loopback network device wasn't configured. That's all :)

--
Best Regards,
Michal.

thanks for help, but it's

mkowalik — Wed, 17 May 2006 12:27:52 +0000

thanks for help, but it's not the problem

I'm quite sure it's a problem with epmd.

trying "epmd -names" finishes with "cannot connect to local epmd server"

epmd is of course up and running on defaul port (4369). The only firewall rule on this box says "allow ip from any to any", so firewall can't be the issue

look at this:

zool# erl -name mk@zool
{error_logger,{{2006,5,17},{13,59,26}},'Protocol: ~p: register error: ~p~n',[inet_tcp,{{badmatch,{error,etimedout}},
..
cut
..
Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})

while on my linux box I get the expected result:

[kowalikm]% erl -name mk@kowalikm
Erlang (BEAM) emulator version 5.4.12 [source] [hipe] [threads:0]

Eshell V5.4.12 (abort with ^G)
(mk@kowalikm)1> node().
mk@kowalikm

I hope, that at least I have the problem pointed. now the only thing I have to do is to solve it :)

--
Best Regards,
Michal

Try "killall epmd" and then

sander — Wed, 17 May 2006 11:38:23 +0000

Try "killall epmd" and then start ejabberd with the init script; maybe you closed ejabberd not in the right way.

--
sander

empd?

mkowalik — Wed, 17 May 2006 09:54:48 +0000

Hello.

strange enough:

zool% ps ax | grep epmd
44879 p3 S 0:00.00 /usr/local/lib/erlang/erts-5.4.13/bin/epmd -daemon

zool% sockstat | grep epmd

root epmd 44879 3 tcp4 *:4369 *:*

but:

zool% /usr/local/lib/erlang/erts-5.4.13/bin/epmd -names
epmd: Cannot connect to local epmd

can it be the problem with my ejabberd instalation? But why?