Ejabberd, erl_crash.dump, "Kernel pid terminated" and a WINK ;) approach

Ejabberd : Because everyone seem to use this as a Jabber server
Erlang : Because Ejabberd chose this as language to code

erl_crash.dump - Every time I tried to start the server, it crashed and wrote the crash dump to this file. grrrrrrrrrrr. Who in the world will understand the crash dump.

Googled everywhere, and found a document mentioning the possible reasons for the crash dump. http://www.erlang.org/doc/apps/erts/crash_dump.html

As per the document, the most common reason for Kernel PID terminated  seems to be "The application controller may have shut down for a number of reasons, the most usual being that the node name of the distributed Erlang node is already in use"


Hmmm... Then I checked into the folder "/var/lib/ejabberd/". It had two files only.

1. .erlang.cookie
2. erl_crash.dump

The .erlang.cookie file seemed to be empty. Wrote something inside it. And restarted the server again. Luckily, there was no error. But ejabberdctl still gave some errors. Restarted again, and surprisingly (conditions apply. because computers don't do surprises) , everything went fine.



Finally,
A request to someone who is more into ejabberd and erlang. Could you please explain the reason. ??

Thanks.


:P aich. ;) . This is a called a WINK approach.