From owner-freebsd-ports@FreeBSD.ORG Thu Jun 5 13:32:38 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DEB859B8 for ; Thu, 5 Jun 2014 13:32:38 +0000 (UTC) Received: from nicandneal.net (nicandneal.net [194.231.42.198]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 486CD2E26 for ; Thu, 5 Jun 2014 13:32:37 +0000 (UTC) Received: from lappy.home ([194.231.42.198]) (AUTH: LOGIN nealie, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by nicandneal.net with ESMTPSA; Thu, 05 Jun 2014 15:32:33 +0200 id 00005C1F.0000000053907171.00010E19 Message-ID: <53907172.7070208@nicandneal.net> Date: Thu, 05 Jun 2014 15:32:34 +0200 From: Neal Nelson User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Matthieu Volat Subject: Re: ejabberd update to 14.05 no longer runs References: <538F2852.5030106@nicandneal.net> <20140604190310.044834a6@freedom.alkumuna.eu> In-Reply-To: <20140604190310.044834a6@freedom.alkumuna.eu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 13:32:38 -0000 On 2014-06-04 19:03, Matthieu Volat wrote: > On Wed, 04 Jun 2014 16:08:18 +0200 > Neal Nelson wrote: > >> Hi. >> >> I've just updated ejabberd to the latest 14.05 version, but alas it no >> long runs. Normally I would do some debugging, but this is erlang, so >> all bets are off as I have no idea what to look at, hence the vague >> problem description. >> >> I'd be very grateful is anyone has any idea why a perfectly functional >> ejabber installation no longer works after the upgrade and how I might >> go about fixing it. >> >> Thanks. >> _______________________________________________ > > Did you converted your configuration to yaml, or provided a fresh new one, before restarting the service? Ejabberd no longer use the erlang-based conf files... > Thanks. That was indeed the problem. This should really be an entry in UPDATING though, as I had no idea and the result was catastrophic for the operation of the server. We also seem to be missing to convert_to_yaml command for ejabberdctl, but luckily it was not too difficult to convert manually.