ejabberd - Comments for "Upgrade 1.1.3 to 2.0.1" https://www.ejabberd.im/node/3094 en Copy database files. You can keep config or use new one. https://www.ejabberd.im/node/3094#comment-53296 <div class="quote-msg"> <div class="quote-author"><em>yskwong</em> wrote:</div> <p>1) The 2.0.1 manual (Section 2.6) said that ejabbard will automatically updates the Mnesia table definitions at startup when needed. DOES THIS MEAN THAT I HAVE TO DELETE THE NEW DATABASE DIRECTORY AND ALL ITS FILES, AND REPLACE IT WITH THE ONE DATABASE SPOOL DIRECTORY (AND ITS CONTENT) FROM 1.1.3?? IS IT SAFE TO DO SO?? Or what is the proper way to do it?? </p></div> <p>Yes, it's the best way. </p> <p>Summarizing: stop ejabberd; then delete the database files that were created during installation (and are almost empty); copy the files from your old database; then start ejabberd. When ejabberd 2.0.1 detects that some tables in the database are with an old format, it will update them and store in the files.</p> <div class="quote-msg"> <div class="quote-author"><em>yskwong</em> wrote:</div> <p>2) Can I replace the new ejabberd.cfg file in the ejabberd-2.0.1\bin, with the old ejabberd.cfg from 1.1.3?? Or I should try to edit the new ejabberd.cfg from scratch? </p></div> <p>If you compare your old config file and the default new one, you will notice they appear to be very different. But in reality the same syntax and same options are used, so you can continue using your old config file.</p> <p>There were a few minor option changes (welcome message and a few more). If your old config didn't include many changes and have spare time, you can modify the new default config file to suit your needs (with options copied from your old config file).</p> <div class="quote-msg"> <div class="quote-author"><em>yskwong</em> wrote:</div> <p>3) Observation: I looked at the registry and find that the info for 2.0.1 are stored under the key Ericsson\Erlang\ErlSer\1.1. Why 2.0.1 info are being stored under 1.1 registry key?? </p></div> <p>ejabberd runs in many operating systems: Windows, MacOsX, *nix, *BSD... So, ejabberd itself does not use the windows registry. The binary installer installs a service in case you want to start ejabberd automatically. That key you found in the windows registry is related to that system service. The tool that provides that feature is ErlSer. It is a program included in <noindex><a href="http://www.erlang.org/" rel="nofollow" >Erlang/OTP</a></noindex>, and probably that 1.1 refers to the ErlSer version, not ejabberd.</p> Sun, 15 Jun 2008 20:46:27 +0000 mfoss comment 53296 at https://www.ejabberd.im