ejabberd - Comments for "erlang freezes our server"

Several comments, I hope

mfoss — Sat, 28 Apr 2007 21:20:02 +0000

Several comments, I hope some of them help you.

'-heart' is not required to run ejabberd. Try to remove it from your script.
Check the disk has enought free space. Check the log files are not of big size (larger than 1 gig, for example).
ejabberd logs indicate users login/logout. Maybe comparing the last messages of several crashed logs will hint you a direction to look for.
logs should be stored on /var/log/ejabberd/ejabberd.log and /var/log/ejabberd/sasl.log

You want to know what action triggers the server crash. It may be one or several of those ones:

After 20-24 hours of being started, even if nobody logins at all
After several hundreds of users login and logout
When the server is overloaded by other processes and ejabberd also wants CPU
When a specific user logins to his account, regardless of the client he uses
When a specific client and client options is used to login
When a user makes a specific action

A way to isolate the problem, you should determine if crash is triggered only by time, or by a specific action.
Start ejabberd on a friday night, configure it to listen on strange ports (9991 instead of 5222...) so NOBODY logins on it. Wait 24 hours to see if it crashes.

Another test: start ejabberd, let people login. Put the server to compress files, so CPU is overloaded.

If the crash is user-triggered, and it's always the same user, you can ask him which client does he use, and what options.

Good luck :)

gcc-3.3

kakuz — Fri, 27 Apr 2007 08:50:38 +0000

what for you install gcc-3.3 ? etch using gcc-4.1

if you want install ejabberd on etch you can install from apt, apt-get install ejabberd. apt will install all dependencies.

I am looking for Erlang

alook — Tue, 24 Apr 2007 06:18:31 +0000

I am looking for Erlang logs... don't know where they are ..

Do you know ?

thanks
luc

don't know if it help but

alook — Tue, 24 Apr 2007 05:53:15 +0000

don't know if it help but here is the script with which I lunch ejabberd

#!/bin/sh
ERL=erl
NAME=ejabberd
case "$1" in
start)
echo "Starting $NAME."
cd /usr/src/ejabberd/src/
$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\" \
-heart \
-detached \
;;
stop)
echo "Stopping $NAME."
echo "rpc:call('ejabberd@`hostname -s`', init, stop, [])." | $ERL -sname ejabberdstop
;;
status)
echo "Not implemented yet."
;;
restart|reload)
$0 stop
sleep 3
$0 start
;;
*)
echo "Usage: $0 {start|stop|status}"
exit 1
esac

bad luck... the Erlang

alook — Mon, 23 Apr 2007 16:47:05 +0000

bad luck... the Erlang installation by sources didn't solve the problem...
our server freezed again. Erlang/ejabberd must be the reason but how to debug without any log (server freezed so doesn't write anything else in logs) ?
everything seems ok once we kill "beam" process...

any help, solution or just idea of some test to make, is very wellcome!!!

thanks
luc

this problem is maybe

alook — Thu, 12 Apr 2007 19:24:44 +0000

this problem is maybe solved...
I have uninstall erlang/ejabberd and reinstall erlang via sources...
Now, I have to wait 1 or 2 days to confirm that it is ok or not.

luc