Sergei Golovan wrote: > For unknown reason ejabberd was run as uid 118. In init.d script > there's su - ejabberd call. I don't know where the bug is. Probably in > postinstall script, probably in adduser, which is used for ejabberd > user creation... We'll try to find it. > > Firewall and config look good. > > I think that if you kill this mysterious beam, running by uid 118, and > do dpkg-reconfigure ejabberd (or may be dpkg-reconfigure --force), > you'll get working ejabberd. >
Great, it works now: delli:/home/smo# ps -A | grep beam 8042 ? 00:00:03 beam delli:/home/smo# kill 8042 delli:/home/smo# dpkg-reconfigure ejabberd Stopping jabber server: ejabberd already stopped. You already have /etc/ejabberd/ejabberd.pem Starting jabber server: ejabberd. Waiting for ejabberd to register admin user... Admin user "[EMAIL PROTECTED]" is registered successfully. Thanks, Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
