From owner-freebsd-ports@FreeBSD.ORG Wed Jun 4 17:03:32 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DC78AF61 for ; Wed, 4 Jun 2014 17:03:32 +0000 (UTC) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by mx1.freebsd.org (Postfix) with ESMTP id 9AAAF2829 for ; Wed, 4 Jun 2014 17:03:32 +0000 (UTC) Received: from yggdrasil.alkumuna.eu (unknown [IPv6:2a01:e35:8a74:6e70:232:36ff:fe5c:3a87]) by smtp1-g21.free.fr (Postfix) with ESMTP id 56DFA9401C0; Wed, 4 Jun 2014 19:01:25 +0200 (CEST) Received: from freedom.alkumuna.eu ([192.168.10.100]) (authenticated bits=0) by yggdrasil.alkumuna.eu (8.14.7/8.14.7) with ESMTP id s54H3Enj013573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 4 Jun 2014 19:03:23 +0200 (CEST) (envelope-from mazhe@alkumuna.eu) Date: Wed, 4 Jun 2014 19:03:10 +0200 From: Matthieu Volat To: Neal Nelson Subject: Re: ejabberd update to 14.05 no longer runs Message-ID: <20140604190310.044834a6@freedom.alkumuna.eu> In-Reply-To: <538F2852.5030106@nicandneal.net> References: <538F2852.5030106@nicandneal.net> X-Mailer: Claws Mail 3.10.0 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/lw_KmUiAoUeKqYUc+dW3P+x"; protocol="application/pgp-signature" 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: Wed, 04 Jun 2014 17:03:32 -0000 --Sig_/lw_KmUiAoUeKqYUc+dW3P+x Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 04 Jun 2014 16:08:18 +0200 Neal Nelson wrote: > Hi. >=20 > 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. >=20 > 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. >=20 > 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... --=20 Matthieu Volat --Sig_/lw_KmUiAoUeKqYUc+dW3P+x Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlOPUVIACgkQ+ENDeYKZi36MZwCdFfdt3BmEInyZaoJ++vMf8DHL ORMAoIhUyD6wpwEKRdXgzfY7BUpqVOhI =go3I -----END PGP SIGNATURE----- --Sig_/lw_KmUiAoUeKqYUc+dW3P+x--