Re: ejabberd update to 14.05 no longer runs
On 2014-06-04 19:03, Matthieu Volat wrote: On Wed, 04 Jun 2014 16:08:18 +0200 Neal Nelson nea...@nicandneal.net 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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
ejabberd update to 14.05 no longer runs
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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ejabberd update to 14.05 no longer runs
On Wed, 04 Jun 2014 16:08:18 +0200 Neal Nelson nea...@nicandneal.net 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... -- Matthieu Volat ma...@alkumuna.eu signature.asc Description: PGP signature
