From owner-freebsd-questions@FreeBSD.ORG Tue Sep 6 14:58:11 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6641F106566B for ; Tue, 6 Sep 2011 14:58:11 +0000 (UTC) (envelope-from vivek@khera.org) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id B97398FC2B for ; Tue, 6 Sep 2011 14:58:10 +0000 (UTC) Received: by fxe4 with SMTP id 4so5775115fxe.13 for ; Tue, 06 Sep 2011 07:58:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=khera.org; s=google11; h=mime-version:date:message-id:subject:from:to:content-type; bh=aFhlTXhC3mIE5gSoP+h2MA7ussHAw3b8COHkb3/EBjY=; b=U+Quv4XiWS/Kdq7HdGztUnOLN+fx2ESe64ZVIjq6mHwE4hZN+ErAjo/Ylja/yKnZWz NWsSQ0zzbLbmsSRyoZ2bsG68mAvwaR20SJ1fMk2MlyEVFbXbJ8mh+CaHbiKzXzwqCDjJ QKo89GCjg0MBgON6Te03Dm+Xbr21ZPiEgbgBg= MIME-Version: 1.0 Received: by 10.223.34.91 with SMTP id k27mr334271fad.133.1315318420893; Tue, 06 Sep 2011 07:13:40 -0700 (PDT) Received: by 10.223.102.79 with HTTP; Tue, 6 Sep 2011 07:13:40 -0700 (PDT) Date: Tue, 6 Sep 2011 10:13:40 -0400 Message-ID: From: Vick Khera To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ejabberd cannot be controlled with ejabberdctl X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 14:58:11 -0000 A while ago I upgraded ejabberd from 2.1.5 to 2.1.8, and also updated erlang to r14b03 (not sure the prior version, but it was an r14 release). Running on FreeBSD 8.2/i386. Ever since the upgrade, I cannot use the ejabberdctl program to control it. It always says "Failed RPC connection to the node ejabberd@lorax: nodedown". The short host name of my server is "lorax". If I log into the web interface, it does show node "ejabberd@lorax" is running as the only node. Up until this upgrade I was able to use ejabberdctl just fine to re-open logs and do clean shutdown. I searched the forums and mailing lists and found basically that I need to ensure that when ejabberd starts, it uses the same node name. I checked the start scripts and it does indeed (and always has) explicitly set the node name to "ejabberd@lorax", so I'm pretty well stumped at this point. The only tricky part of the config is that I bound the web interface to the private IP of this machine, instead of the public (it has two NICs). I'm using the FreeBSD port version of both erlang and ejabberd. Any help would be appreciated.