Results 1 to 3 of 3

Thread: Ejabberd Start Fails on Ubuntu 12.04.1

  1. #1
    Join Date
    Mar 2010
    Location
    Pensacola, FL
    Beans
    11
    Distro
    Ubuntu 10.04 Lucid Lynx

    Exclamation Ejabberd Start Fails on Ubuntu 12.04.1

    I am trying to install ejabberd 2.1.10-2 on my Ubuntu 12.04.1 server. This is a fresh install, and ejabberd is never successfully installed.

    The Install

    Every time, apt-get hangs on this:

    Code:
    Setting up ejabberd (2.1.10-2ubuntu1) ...
    Generating SSL certificate /etc/ejabberd/ejabberd.pem...
    
    Creating config file /etc/ejabberd/ejabberd.cfg with new version
    Starting jabber server: ejabberd............................................................ failed.
    The dots just go until it times out or I 'killall' beam, beam.smp, epmd, and ejabberd processes. I've turned off all firewall restrictions.

    Here's the output of epmd -names while the install is hung:

    Code:
    epmd: up and running on port 4369 with data:
    name ejabberdctl at port 42108
    name ejabberd at port 39621
    And after it fails:

    Code:
    epmd: up and running on port 4369 with data:
    name ejabberd at port 39621
    At the same time (during and after), the output of both netstat -atnp | grep 5222 and netstat -atnp | grep 5280 is empty.


    The Crash File

    A crash dump file is created at /var/log/ejabber/erl_crash.dump. The slogan (i.e. reason for the crash) is:

    Code:
    Slogan: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
    It's alive?

    Whenever I try to relaunch ejabberd with service ejabberd start, the same thing happens - even if I've killed all processes before doing so.

    However, when I killall the processes listed above again, and run su - ejabberd -c /usr/sbin/ejabberd, this is the output I get:

    Code:
    Erlang R14B04 (erts-5.8.5) [source] [64-bit] [rq:1] [async-threads:0] [kernel-poll:false]
    
    Eshell V5.8.5  (abort with ^G)
    (ejabberd@ns1)1> 
    =INFO REPORT==== 15-Oct-2012::12:26:13 ===
    I(<0.478.0>:ejabberd_listener:166) : Reusing listening port for 5222
    
    =INFO REPORT==== 15-Oct-2012::12:26:13 ===
    I(<0.479.0>:ejabberd_listener:166) : Reusing listening port for 5269
    
    =INFO REPORT==== 15-Oct-2012::12:26:13 ===
    I(<0.480.0>:ejabberd_listener:166) : Reusing listening port for 5280
    
    =INFO REPORT==== 15-Oct-2012::12:26:13 ===
    I(<0.40.0>:ejabberd_app:72) : ejabberd 2.1.10 is started in the node ejabberd@ns1
    Then, the server appears to be running. I get a login prompt when I access http://mydomain.com:5280/admin/. Of course I can't login unless I create an account.

    At this time, the output of netstat -atnp | grep 5222 and netstat -atnp | grep 5280 is as follows:

    Code:
    tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      19347/beam      
    tcp        0      0 0.0.0.0:5280            0.0.0.0:*               LISTEN      19347/beam
    ejabberdctl

    Even when it appears ejabberd is running, trying to do anything with ejabberdctl fails. For example: trying to register a user:

    Code:
    root@ns1:~# ejabberdctl register myusername mydomain.com mypassword
    Failed RPC connection to the node ejabberd@ns1: nodedown
    I have no idea what I'm doing wrong. I've attached a gzipped copy of the erl_crash.dump file in case it's helpful. This happens on two different servers I have with identical software installed (really not much of anything). Please help. Thanks.
    Attached Files Attached Files

  2. #2
    Join Date
    Feb 2013
    Beans
    1

    Question Re: Ejabberd Start Fails on Ubuntu 12.04.1

    Did you find any solution on this? Have the same problem and my googling didn't get me any answers
    Could possibly Apache do some conflict?

  3. #3
    Join Date
    Mar 2010
    Location
    Pensacola, FL
    Beans
    11
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Ejabberd Start Fails on Ubuntu 12.04.1

    Yes I did. Sorry for not posting my solution here before. I asked the same question on AskUbuntu.com and found a solution there. The problem was that ejabberd couldn't find my host by name (it uses the node name). I just needed to add this line to my /etc/hosts file:

    Code:
    123.123.123.123   ns1
    Since it was trying to connect to the node 'ejabberd@ns1'.

    Obviously, 123.123.123.123 is not my actual IP, but you get the idea.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •