<html><body>
<p><font face="Courier New">To resolve the problem, I am going to uninstall jabber and then reinstall.</font><br>
<br>
<font face="Courier New">When I tried to uninstall ejabberd, rpm complained that ejabberd is needed by xs-pkgs-0.3.0-1.noarch</font><br>
<br>
<font face="Courier New">I am not familiar with xs-pkgs. Should I assume that this is specific to the XS server?</font><br>
<br>
<font face="Courier New">Should I also uninstall xs-pkgs and then install it again? Or should I specify --nodeps?</font><br>
<br>
<font face="Courier New">If I set up jabber to use MySQL rather than the default flat files, will any XS-specific processes discontinue to work? Do any XS-specific process use the files directly? </font><br>
<br>
<font face="Courier New">Thank you.</font><br>
<br>
<font face="Courier New">Andrew Berkowitz</font><br>
<font face="Courier New">DOE</font><br>
<font face="Courier New">2 MetroTech Center, Suite 3900</font><br>
<font face="Courier New">Brooklyn, NY 11201</font><br>
<font face="Courier New">aberkowitz@schools.nyc.gov</font><br>
<font face="Courier New">718-935-5471</font><br>
<font face="Courier New"> </font><br>
<br>
<br>
<br>
<font face="Courier New">-----Original Message-----</font><br>
<font face="Courier New">From: John Watlington [</font><a href="mailto:wad@laptop.org"><u><font color="#0000FF" face="Courier New">mailto:wad@laptop.org</font></u></a><font face="Courier New">] </font><br>
<font face="Courier New">Sent: Thursday, May 08, 2008 12:52 AM</font><br>
<font face="Courier New">To: Martin Langhoff; Berkowitz Andrew (Project Connect)</font><br>
<font face="Courier New">Cc: John Watlington; server-devel; Kim Quirk</font><br>
<font face="Courier New">Subject: Re: Possible Jabber Problem on Server</font><br>
<br>
<br>
<font face="Courier New">On May 7, 2008, at 10:28 PM, Martin Langhoff wrote:</font><br>
<br>
<font face="Courier New">> On Thu, May 8, 2008 at 2:19 AM, Berkowitz Andrew (Project Connect)</font><br>
<font face="Courier New">>> Greetings from New York.</font><br>
<font face="Courier New">></font><br>
<font face="Courier New">> "G'day mate" from New Zealand!</font><br>
<font face="Courier New">></font><br>
<font face="Courier New">>> Although the short hostname, schoolserver, has stayed the same, the </font><br>
<font face="Courier New">>> domain has changed from 00b000.nycboe.org to 00b001.nycboe.org and </font><br>
<font face="Courier New">>> back to 00b000.nycboe.org. When I changed the domain & address, I </font><br>
<font face="Courier New">>> changed the</font><br>
<font face="Courier New">></font><br>
<font face="Courier New">> Hmmmm. That's unsupported at the moment. Wad might have more </font><br>
<font face="Courier New">> experience changing the FQDN...</font><br>
<br>
<font face="Courier New">I've only recovered from that by nuking the ejabberd installation (rpm -e ejabberd; rm -r /var/lib/ejabberd/; yum install ejabberd)</font><br>
<br>
<font face="Courier New">>> Jabber servers are</font><br>
<font face="Courier New">>> notoriously finicky and frequently return the nodedown message if a </font><br>
<font face="Courier New">>> server's hostname changes.</font><br>
<font face="Courier New">></font><br>
<font face="Courier New">> Exactly, and we haven't yet done the legwork to make sure that this </font><br>
<font face="Courier New">> works end-to-end.</font><br>
<br>
<font face="Courier New">We've done enough to know that changing the host/domain name is a big problem with the current presence server.</font><br>
<br>
<font face="Courier New">>> The normal resolution is to export the database, convert it and </font><br>
<font face="Courier New">>> import it. I tried this conversion using the Erlang conversion </font><br>
<font face="Courier New">>> utility.</font><br>
<font face="Courier New">>></font><br>
<font face="Courier New">>> I also reimported the original database. Some people report that just </font><br>
<font face="Courier New">>> exporting and importing, without conversion, fixes the problem.</font><br>
<font face="Courier New">>> This process</font><br>
<font face="Courier New">>> also did not resolve the issue.</font><br>
<br>
<font face="Courier New">I found at least one recipe which claimed to fix this problem a while back, but didn't test it.</font><br>
<br>
<font face="Courier New">> Hm. What happens if you wipe out the mnesia database and start from </font><br>
<font face="Courier New">> scratch.</font><br>
<br>
<font face="Courier New">Fixes the problem.</font><br>
<br>
<font face="Courier New">>> Also, I have another concern. The jabber database is kept in text </font><br>
<font face="Courier New">>> files.</font><br>
<font face="Courier New">>> This configuration is fine for small sites. But with many users, it </font><br>
<font face="Courier New">>> is better to keep the database in MySQL for better performance and </font><br>
<font face="Courier New">>> better reliability.</font><br>
<font face="Courier New">></font><br>
<font face="Courier New">> If I can get mnesia to use PostgreSQL as a backend, I'll do it.</font><br>
<br>
<font face="Courier New">There are configuration file option for ejabberd to use postgreSQL, etc.</font><br>
<font face="Courier New">for the database. Perhaps some volunteers can play with these ?</font><br>
<br>
<font face="Courier New">>> Another question: You've reported a bug where If an XO is reimaged </font><br>
<font face="Courier New">>> and then needs to re-register with the server, it cannot. In this </font><br>
<font face="Courier New">>> case, is it okay to export the database as text, manually delete the </font><br>
<font face="Courier New">>> entry, and then import the database.</font><br>
<br>
<font face="Courier New">> For a quick fix, you can delete the entries in the SQLite db in </font><br>
<font face="Courier New">> /home/idmgr . We'll have a UI for this later.</font><br>
<br>
<font face="Courier New">Wrong database. If that bug is due to a database, it is the ejabberd database.</font><br>
<br>
<font face="Courier New">But if you are referring to #6919, it is harder to replicate than Giannis indicated</font><br>
<font face="Courier New">at first. I do this all the time, when testing builds/servers, and </font><br>
<font face="Courier New">hadn't seen it.</font><br>
<font face="Courier New">It was easier to replicate for a while, when the presence server in the local area was misconfigured.</font><br>
<br>
<font face="Courier New">> All these ad-hoc DBs need to be under some control, and the UI will </font><br>
<font face="Courier New">> probably be handled as an extension of Moodle's user mgmt facilities.</font><br>
<br>
<font face="Courier New">Darn right...</font><br>
<br>
<font face="Courier New">Cheers,</font><br>
<font face="Courier New">wad</font><br>
<br>
<br>
<br>
<br>
</body></html>