RUSH RENDER QUEUE - WINDOWS UPGRADE
(C) Copyright 1995,2000 Greg Ercolano. All rights reserved.
V 102.40g 05/06/03


102.40g Windows Upgrade Instructions

  1. Make sure the rush network is idle.
  2. To install the new release, you must first stop the old release network wide. The new version is not backwards compatible.

    Weekends are generally a good time to do upgrades.

    In the text below, change the red text as needed.

  3. Verify no jobs are running.
  4. Check the network to make sure no jobs are running with either:

      rush -laj
    OR
      rush -lj +any

    Dump any jobs that are running.

  5. Install first on the license server.
    1. Stop the daemon on the license server:
      net stop rushd
    2. Rename out the old release:

      cd c:\
      move \rush \rush.old

      If you get errors during the 'move' about 'file in use' or 'sharing violation', use the task manager to kill processes called 'rush', 'rushd', or any rush invoked renders or scripts.
    3. Extract the new version to C:\rush
    4. Preserve your previous hosts and license.dat files:

      copy \rush.old\etc\hosts \rush\etc
      copy \rush.old\etc\license.dat \rush\etc

      Manually merge in any custom changes to your rush.conf file, e.g. check for local customizations to ntrushuid/ntrushgid, and smtpserver/smtpfrom. Do *NOT* just copy your old rush.conf file into the new release directory.

    5. Start the new daemon:
      net start rushd
    6. Verify the local daemon is running:
      rush -ping
  6. Upgrade the rest of the net.
  7. To upgrade the other machines is easier, usually just by having each machine run this batch script:

      Network Install Commands
           net stop rushd
           rush -sleep 5
           xcopy /s \\masterhost\C$\rush \rush    
           net start rushd
          

  8. Verify the network install is up.
  9. rush -ping +any

    ..all machines should reply with the same version number. Any that don't, check the c:\rush\var\rushd.log for errors.

    If a machine complains about 'bind(): address in use' for more than 2 minutes, you may need to reboot that machine.


Backout Procedure

    In the event you need to back out the new release, just stop the daemon on all machines, rename back the old directory, and restart.

    Again, start with the license server.