[BACK]Return to upgrade.html CVS log [TXT] [DIR] Up to [LON-CAPA] / doc / build

Diff for /doc/build/Attic/upgrade.html between versions 1.6 and 1.14

version 1.6, 2001/04/18 15:55:19 version 1.14, 2002/05/02 02:00:00
Line 1 Line 1
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   <!-- $Id$ -->
 <html>  <html>
 <head>  <head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8"></meta>
 <title>LON-CAPA Upgrade</title>  <title>LON-CAPA Upgrade</title>
   <!-- pdfahref upgrade.pdf -->
   <!-- button UPGRADE -->
 </head>  </head>
 <body>  <body>
 <h1>LON-CAPA Upgrade</h1>  <!-- preamble start -->
 <h3>Current Upgrade Procedure</h3>  <br />&nbsp;
 <p>  <p>
 Scott Harrison  There are three steps for upgrading the software on your LON-CAPA server.
 </p>  </p>
   <ul>
   <li><a href="#upgrade">
   Upgrading LON-CAPA files</a></li>
   <li><a href="#checkrpms">
   Checking your Linux RPMs</a></li>
   <li><a href="#testing">
   Testing to see if the LON-CAPA server is operational</a></li>
   </ul>
   <br />&nbsp;<br />
   <!-- preamble end -->
   <!-- maintext start -->
   <a name="upgrade" />
   <h3>Upgrading LON-CAPA files</h3>
 <p>  <p>
 Last updated: 4/18/2001  Download the most current
   <a href="http://install.lon-capa.org/versions/current/loncapa.tar.gz">
   loncapa.tar.gz</a>.
 </p>  </p>
 <p>  <p>
 LON-CAPA system releases currently are not released under version  The <strong>UPDATE</strong> command will refresh your filesystem with all
 numbers given the fast pace of system development.  To upgrade your  the latest LON-CAPA software.
 system, you need to   </p>
 <ol>  <table bgcolor="#aaaaaa" border="1">
 <li>Make sure your software packages are up-to-date  <tr><td><tt>./UPDATE</tt></td></tr>
 (based on install.lon-capa.org).</li>  </table>
 <ul>  <a name="checkrpms" />
 <li>As root, run the script <tt>/usr/sbin/loncapaverifypackages</tt>.    <h3>Checking your Linux RPMs</h3>
 If packages are out-of-date, this script will output  <p>
 the out-of-date packages.  Packages that this script identifies as  The <strong>CHECKRPMS</strong> command will check the RPMs on your machine
 "should not be here", are packages that you may wish to remove to  against an FTP repository.
 improve system security.  (These packages may represent important  </p>
 modifications of your institution, so do with care.  Removing  <table bgcolor="#aaaaaa" border="1">
 packages is done with the command: <tt>rpm -e --nodeps PACKAGE_NAME</tt>.</li>  <tr><td><tt>./CHECKRPMS</tt></td></tr>
 </ul>  </table>
 <li>Upgrade old software packages.</li>  <a name="testing" />
 <ul>  <h3>Testing to see if the LON-CAPA server is operational</h3>
 <li>Upgrade software packages by either</li>  <p>
 <ul>  The <strong>TEST</strong> command will check the installation software,
 <li>Running <tt>/usr/sbin/loncapaupgradepackages</tt>.</li>  the perl libraries on your system, the MySQL database, and
 <li>Or, going to <a href="http://install.lon-capa.org/3.1/SupplementalRPMS/">http://install.lon-capa.org/3.1/SupplementalRPMS/</a>,  will also automatically test the real-time operation of the 
 you can individually download each package from the world-wide web.  You   LON-CAPA Apache web server.
 then need to enter the command:  </p>
 <tt>rpm -Uvh --force PACKAGE_RPM_FILE_NAME</tt> to upgrade your system  <table bgcolor="#aaaaaa" border="1">
 for each package.</li>  <tr><td><tt>./TEST</tt></td></tr>
 </ul>  </table>
 </ul>  <p>
 <li>Make the LON-CAPA base files up to date (based on  Using the <strong>TEST</strong> command will likely
 install.lon-capa.org).</li>  be an iterative process.
 <ul>  It is normal to expect that the <strong>TEST</strong> command
 <li><B>[optional]</B> Run the script  will recommend you perform various steps to ensure optimal
 <tt>/usr/sbin/loncapaverifybasepackage</tt>.  Then view  performance of your LON-CAPA server.
 /home/httpd/html/dev/index.html for the verification report.  
 If there are no real changes, then you do not need to make your files  
 up-to-date.</li>  
 <li>Download the most recent LON-CAPA rpm (<a href="http://install.lon-capa.org/3.1/loncapafiles/LON-CAPA-base-3.1-1.i386.rpm">  
 LON-CAPA-base-3.1-1.i386.rpm</a>).  <tt>rpm -Uvh --force LON-CAPA-base-3.1-1.i386.rpm</tt> will upgrade your software package files.</li>  
 </ul>  
 <li>Restore configuration files.</li>  
 <ul>  
 <li>As you run /usr/sbin/loncapaupgradepackages or enter in  
 <tt>rpm -Uvh --force</tt> commands, you may  
 see messages appear on your screen such as:  
 <br /><tt>warning: /etc/httpd/conf/access.conf saved as  
 /etc/httpd/conf/access.conf.rpmsave</tt>  
 <br />You can probably just type in commands like:  
 <br /><tt>cp /etc/httpd/conf/access.conf.rpmsave  
 /etc/httpd/conf/access.conf</tt>  
 <br />to restore your configurations.  However, it is worthwhile to use the  
 'diff' command to make sure that you are not accidentally losing important  
 updates to the configuration files.    
 <li>Alternatively, you can run <tt>/usr/sbin/loncaparestoreconfigurations</tt>  
 to "smartly" run through the system and restore LON-CAPA configuration  
 values.</li>  
 </ul>  
 <li>Restart the LON-CAPA networking processes  
 <ul>  
 <li><tt>/etc/rc.d/init.d/loncontrol restart</tt></li>  
 </ul>  
 <li>Should you wish to automate the updating of your LON-CAPA base files, you can (at your own risk) run a script which will  
 do all of this automatically.  You can run this script by entering the command:  
 <TT>/usr/sbin/loncapaautoupgrade</TT></li>  
 </ol>  
 </p>  
 <h3>Future Upgrade Procedure (not yet implemented)</h3>  
 <p>  
 In the future, LON-CAPA will be a versioned system that is released via CD.  
 The upgrade procedure will be to insert the CD and follow instructions.  The CD  
 upgrade procedure is already defined and somewhat implemented, but awaits  
 completion.  
 </p>  </p>
   <!-- maintext end -->
   <!-- validated -->
 </body>  </body>
 </html>  </html>
Removed from v.1.6  
changed lines
  Added in v.1.14

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>