
The name of an Erlang node includes the hostname of the computer. Being distributed, Mnesia enforces consistency of its file, so it stores the name of the Erlang node in it (see section Erlang Node Name ).


I have been running the above commands as root, since my local user doesn't have access to launch them. ejabberd uses the distributed Mnesia database. I've been racking my brain for a week now and am getting nowhere. when am trying to stop ejabberd its not stopping, its stopping only after killing beam. I guess it get stuck at node setup/mnesia table replication. Erlang R15B01 (erts-5.9.1) Įshell V5.9.1 (abort with Data may be missing, Corrupt logfile deleted: "/var/lib/ejabberd/LATEST.LOG", ) It should restart ejabberd server, it stops it, then setup cluster and tries to estabilish connection to other nodes, and if that success it starts server again. I actually get some output! Here's what I got. I have an (old) ejabberd instance that still uses internal as authentication method. I have ejabberd set up, and if I run ejabberd via command line, it executes fine, I can connect, chat with other people, etc.Įverything executes properly, but the service does not launch.Įjabberd says the node is down and doesn't supply any more information. Ejabberd: Migrating Mnesia 'passwd' table to MySQL 'user' table.
