I can see there's many problems with running ejabberd on FBSD.
I use FreeBSD 6.1.
Action1:
/usr/local/etc/rc.d/ejabberd start
Action2:
ps axuw
Result12:
root 6778 0,0 0,2 1312 944 ?? S 11:41 0:00,01 /usr/local/lib/erlang/erts-5.5/bin/epmd -daemon ejabberd 6825 0,0 0,3 2540 1780 ?? Ss 11:47 0:00,03 /usr/local/lib/erlang/lib/ssl-3.0.12/priv/bin/ssl_esock
Action3:
netstat -an
Result3:
tcp4 0 0 127.0.0.1.61240 *.* LISTEN tcp4 0 0 127.0.0.1.4369 127.0.0.1.53348 ESTABLISHED tcp4 0 0 127.0.0.1.53348 127.0.0.1.4369 ESTABLISHED tcp4 0 0 *.60886 *.* LISTEN tcp4 0 0 *.4369 *.* LISTEN tcp4 0 0 *.50102 *.* LISTEN
Running command ejabberd
with an argument(s) causes RPC failed on the node start: nodedown
Running just command ejabberd
without any argument causes
{"init terminating in do_boot",{badarg,[{ets,match_object,[ejabberd_ctl_cmds,'_']},{ets,tab2list,1},{ejabberd_ctl,print_usage,0},{ejabberd_ctl,start,0},{init,start_it,1},{init,start_em,1}]}} Crash dump was written to: erl_crash.dump init terminating in do_boot ()
Should not be something listening on ejabberd_c2s(5222, 5223-ssl) and ejabberd_http(5280)? These ports are used in config file.
Anyone figure this out?
I am in the same boat.
What are you using for your ejabberd script? The ctl script? (I get the same error).
The same for me, using
The same for me, using Fedora Core 5.
Starting manually as root from within /etc/ejabberd using erl -pa /var/lib/ejabberd/ebin -name ejabberd -s ejabberd
makes it working flawlessy. The shipped init-script uses this:
erl -pa /usr/lib/ejabberd-1.1.1/ebin \
-sname ejabberd \
-s ejabberd \
-ejabberd config \"/etc/ejabberd/ejabberd.cfg\" \
log_path \"/var/log/ejabberd/ejabberd.log\" \
-sasl sasl_error_logger \{file,\"/var/log/ejabberd/sasl.log\"\} \
-mnesia dir \"/var/lib/ejabberd/spool\"
...and it doesn't work too...
Roger
not finding ejabberd.cfg?
btw. somehow i have the feeling, as ejabberd won't load the config-file mentionned in -ejabberd config=...but i have no proof for it.
Roger
Beam line missing
What i found out, is that the line calling Beam is missing in all our outputs. Usually i have 3 lines in, on older version, one of those has beam in it...
Rog
Re: ejabberd 1.1.1 and FBSD 6 .1 problems
I can see there's many problems with running ejabberd on FBSD.
I use FreeBSD 6.1.
Action1:
Action2:
Result12:
ejabberd isn't started; you should see a process called beam. Did you add this line to your /etc/rc.conf file?:
After you add this line, you should do:
And you will see something like:
RE: ejabberd 1.1.1 and FBSD 6 .1 problems - SOLVED
OK, i got it working now.
-> i installed Erlang to erlang.i386 R11B-0.1.fc5 (Version R11B)
-> copied Mnesia-Dirs to the taget mentionned in the initscript
-> chowned the new Mnesia-Dir to ejabberd:ejabberd
...works!
HTH
Roger
FreeBSD 6.1 /ejabberd 1.1.1
I've loaded 1.1.1 on FreeBSD several times now, and it's running great. From a fresh install I loaded perl via sysinstall, then gmake, gcc, openssl, expat, xorg-libraries, javavmwrapper...
Got the diablo jdk, loaded the erlang-lite port...
Loaded ejabberd-1.1.1 from source (configure, gmake, gmake install)
start it with this script:
#!/bin/sh
exec /usr/local/bin/erl -pa /var/lib/ejabberd/ebin \
-sname ejabberd \
-s ejabberd \
-ejabberd config \"/etc/ejabberd/ejabberd.cfg\" \
log_path \"/var/log/ejabberd/ejabberd.log\" \
-sasl sasl_error_logger \{file,\"/var/log/ejabberd/sasl.log\"\} \
-mnesia dir \"/var/lib/ejabberd/spool\" -detached
Works beautifully- I'm authenticating against AD, using TLS, and Jwchat for web access.