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

102.40g Unix 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.

  2. Verify no jobs are running.

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

      rush -laj
    OR
      rush -lj +any

    Dump any jobs that are running.

  3. Install first on the license server.

    1. Stop the daemon, e.g.:
      /etc/init.d/rush stop

    2. Rename out your old version:
      mv /usr/local/rush /usr/local/rush.old

    3. Extract the new version, eg::
      cd /usr/local
      gunzip -c /var/tmp/rush-102.31b-linux.tar.gz | tar xvfp -

    4. Preserve your hosts and license file:

      cp /usr/local/rush.old/etc/{hosts,license.dat} /usr/local/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. Update the boot script if necessary:
      cp /usr/local/rush/etc/S99rush /etc/init.d/rush

    6. Start the daemon:
      /etc/init.d/rush start

    7. Verify the local daemon is running:
      rush -ping

  4. Upgrade the rest of the net.

    5. To upgrade the other machines is fairly easy:

      Network Install Commands 
          foreach i ( host1 host2 host3 .. )
         echo --- $i
         rdist -oremove -c /usr/local/rush ${i}:/usr/local/rush    
         rsh $i /etc/init.d/rush stop \; /etc/init.d/rush start
    end

  5. Verify entire network is up.
    6. When you're done, check your work with:

    rush -ping +any

    ..all machines should reply with the same version number. Any that don't, check the /usr/local/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.