We are now moving the service to a new server based on Gentoo and upgraded version of Ejabberd to version 2.1.8. There will be a bit of downtime but no more than a couple of hours max. Estimated finish aprox 14:00 CET.
Archive for the 'Jabber.no' Category
Hello all, we are very sorry about the instability lately. We are by now on an unsupported Ubuntu version and we will need to migrate onto a new server install to remedy the problems. Currently we are looking for a solution to this and are asking for your patience while we sort this out. Very sorry about this!
We have now migrated the databases over to MySQL databases from Ejabberds mnesia due to size issues causing instability. We have seen some few collation issues on the roster but that should be ok, just set the name again to mitigate. Let us hope this means more stable services 
We have found the root cause of the instability issues with Ejabberd, basically our database is too big for the internal databases and we need to export to SQL based database.
Currently we are trying to do this migration but not without issues. Will update status later.
I have now removed the Python based transports and enabled the Spectrum ones again since it did not have any effect disabling them. Lets see what happens in a few days of running this way.
I have now stopped the Spectrum transports to see if that improves stability. At the same time I have also adjusted the logging to capture more details if we encounter more problems.
We have upgraded to last version of Spectrum due to stability problems on the version we have been running (pulling down the ejabberd server). Hope things are (more) stable now.
Now we have upgraded to the new version of Ejabberd that hopefully will fix the problems we have had with the transports taking down the service a few times every day. We will see over the next few days if all has been fixed.
You can read more about this new version of Ejabberd here: http://www.ejabberd.im/ejabberd-2.1.4
New patch applied now that hopefully fixes the issue. We think the problems is with Spectrum transport and the way ejabberd handles some error messages from Spectrum.
More information: https://support.process-one.net/browse/EJAB-930
We have now applied the patch to the running stable version, it will be fixed in Ejabberd 2.1.4 so next upgrade is safe. Let us just hope this now works! (Thanks a million for the help Asbjørn!)
We are having some stability issues with the Jabber service these days, I am looking into the problem and will try to fix it as soon as possible. Very sorry about this.