ejabberd - Comments for "Migrating jabberd 1.4 Accounts" https://www.ejabberd.im/node/77 en Import jabberd spool : Debian https://www.ejabberd.im/node/77#comment-136 <p>Just a quick note as it it took me a little while to make this work. To get this to work you must do the following:</p> <p>1) Make sure the user running ejabberd has read (&amp; execute?) permissions for all the files in your jabberd spool directory. On Debian woody I did this with:<br /> <code>chown -R ejabberd\:ejabberd /var/lib/jabber</code></p> <p>2) You have to use the lowest level directory in the spool (the one with all the .xml files in it). e.g.<br /> <code>/var/lib/jabber/mysite.co.uk</code></p> <p>3) Restart the server.<br /> <code>ejabberdctl restart</code></p> <p>Note that the migration process does not report any errors or progress.</p> Thu, 03 Feb 2005 13:36:10 +0000 swythan@amessage.info comment 136 at https://www.ejabberd.im Never mind https://www.ejabberd.im/node/77#comment-124 <p>The contact lists all migrated. It was a user error.</p> <p>I appreciate this very much. We are shutting down access to the major IM servers through our firewall for security reasons. We will be putting everyone on jabber and ejabberd looks very good for us to use.</p> Thu, 27 Jan 2005 18:12:37 +0000 sbrenneis comment 124 at https://www.ejabberd.im Works. Sort of... https://www.ejabberd.im/node/77#comment-123 <p>Thanks very much. I used tkabber and it migrated the accounts. It seems to have left the contact lists behind. Is this correct?</p> <p>Once again, thanks very much.</p> Thu, 27 Jan 2005 17:02:00 +0000 sbrenneis comment 123 at https://www.ejabberd.im import jabberd spool: two methods https://www.ejabberd.im/node/77#comment-122 <p>I've added a working mirror of the guide until JabberStudio fully recovers. The link is on the front page. However, it doesn't explain how to make the migration.</p> <p>Currently there are two methods to access such functionality: <ul> <li>Discovery (it works on Tkabber). You must login on Tkabber with an account with admin privileges on your server. Open Tkabber Discovery, go to 'running nodes', 'import users from jabberd1.4 spool', 'import directory', 'configure service' and enter the full path to the spool directory. </li><li>Raw XML. Login to an account with admin privileges with a client that allows sending raw XML (Psi, Exodus, Tkabber...) and send a message similar to: <pre>&lt;iq id='14' to='JSERVER' type='set'> &lt;query xmlns='ejabberd:config' node='running nodes/NODENAME/import/dir'> &lt;x xmlns='jabber:x:data' type='submit'> &lt;field var='path'> &lt;value>SPOOLDIR&lt;/value> &lt;/field> &lt;/x> &lt;/query> &lt;/iq></pre> replacing: <ul> <li>JSERVER: the Jabber server. Example: jabber.company.com </li><li>NODENAME: the Erlang node name. You can find that name in your ejabberd logs. When ejabberd starts, it shows a lot of messages and something like this: <pre>=PROGRESS REPORT==== 27-Jan-2005::16:56:40 === application: ejabberd started_at: myejab@machine3</pre> So your NODENAME is myejab@machine3. </li><li>SPOOLDIR: full path to the jabberd1.4 spool directory. Example: /home/jabberd/spool </li></ul> </li></ul> </p> Thu, 27 Jan 2005 16:02:53 +0000 mfoss comment 122 at https://www.ejabberd.im