On Fri, 21 May 2010 12:20:13 +0200 hennr <he...@hennr.name> wrote: > It seems that ejabberd does not start on KVM based VMs. > ejabberd starts without any problems on the host (lenny + some > backports packages) and on various other Debian lenny machines I have > access to. > > Killing beam and don't having anything using port 5222 does not solve > the problem. > > Any other ideas?
As I have no idea how to test ejabberd with KVM (never used any hard-core virtualization solutions with Linux), my proposition is as follows. Assuming you have a working setting in which you can reliably reproduce your problem, please do these steps: 1) Ensure the network side is OK, that is, at least nothing listens on tcp/5222 and tcp/5269, and that ejabberd is stopped (no beam or beam.smp processes are running). 2) Delete the contents of /var/log/ejabberd. 3) Start ejabberd. 4) If it fails to start, see if it dropped an Erlang crash dump. If it did, gzip anything found in /var/log/ejabberd after the crash and stash it away. 5) Cleanup after crash, that is, repeat steps 1 and 2. 6) Try starting ejabberd using # /etc/init.d/ejabberd live This will run it in foreground. If ejabberd crashes, scroll its terminal output until you see a crash error message and copy a handful of lines from it. In any case, after reproducing a crash post the collected data here. Then I'll try to analyze the data and possibly request more info about your setup. In other words, let's do a clean start with your problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
