The server was offline this morning because of Kernel and MySQL upgrade. It would have happened faster if the server rebooted cleanly after “shutdown -r now” which it didn’t. So we had to send someone there to reset the machine manually.
We also upgraded Spectrum to support JID escaping. If this works after our tests (there seem to be some problems with clients who don’t support the unofficial % character which is used for @) I write more about this here.
To avoid login errors or messages and also to avoid certain problems with server-to-server connections we installed proper certificates for the secondary domains today.
We had to restart the Jabber services several times, sorry. The ejabberd config file isn’t commented very good, also Google didn’t tell us the correct settings in the first place. But everything works fine now.
PS: For old SSL connections to port 5223 there are no dynamic certificates. This just isn’t possible because of how SSL works.
At 2pm CEST today I just upgraded the server to ejabberd 2.1.3, which is a bugfixing release. Finally the Debian package is available. Sorry for the less than one minute short service downtime. ;-)
Finally, Jabber Disk, SMS Gateway and JMC moved to the new server. Jabber Disk and the SMS Gateway are up and running.
Unfortunally JMC still runs very unstable. Please be patient, I’m in contact with the programmer and it looks like he is willing to put some time into the code. We’ll see how this will work out. I hope that we can achieve some improvement because it seems that this feature is a well seen and used feature.
Ok, the server move is almost finished. JMC, jDisk and SMS have still to be moved, that’s gonna happen later the day… ;-)
If you experience any other problems, please contact us!
Due to massive hardware problems we will move the Jabber service to a new machine. This will happen soon, maybe already this evening/night. You won’t be able to reach the services for about an hour. The new IP address will be 184.108.40.206 – if your DNS does not update in time. We apologize for the trouble caused.
On December 22nd, 2008, we switched the ejabberd daemon from Mnesia storage to MySQL storage.