6.4 Before You Patch the Server

Before you patch the server, perform the following procedures that apply:

6.4.1 Ensuring that All Services Are Installed before Patching the Server

When you patch the server, patches are applied only to services that are installed and configured on the server. Therefore, make sure to install and configure any services that you want on the server before you patch the server.

For procedures, see Installing or Configuring OES Components on an Existing Server.

If you want to install a service after the server has been patched, you should install it using updated media (the updated ISO images from the latest Support Pack).

6.4.2 Ensuring that the Server Has Enough Disk Space for the Support Pack Patches

IMPORTANT:Downloading and installing patches on an OES Linux server from the public update service at https://update.novell.com/data can be problematic if the server has insufficient disk space.

Before downloading and patching the server, make sure that the server has at least 6 GB of free disk space in the required locations to download and install the patches from the channel. For specific disk space requirements, see Table 6-4.

Table 6-4 Disks Space Requirements for Downloading and Installing Patches from the Channel

Action

Disk Space Requirement

More Information

Download

3 GB of free disk space in the partition that contains the /var/cache/rcd directory.

or

3 GB or more of free disk space anywhere on the server.

The /var/cache/rcd directory is the default directory that rug downloads patches to.

To verify the amount of space available in a partition, enter the df -h command at a shell prompt.

If you want to use 3 GB anywhere on the server, use the following command to configure rug to download to a specific directory rather than the default:

rug set-prefs cache-directory /directory_name

For example:

rug set-prefs cache-directory /patches

Install

3 GB in the /tmp directory.

After the patches have been downloaded, they are installed to various locations on the server.

If the server has insufficient disk space for downloading the patches from the OES channel, we recommend using the updated Support Pack CDs or ISO images to patch the server. See Section 6.5, Patching Using a Patch CD or ISO Images.

6.4.3 Setting Proxy Preferences

If you want to update the server using the Red Carpet utility and a proxy server exists in the network environment and needs to be used to access the Internet, you can change the preferences in Red Carpet to allow the server to be accessed using the following procedures.

IMPORTANT:You only set the username and password preferences if the proxy server requires a username.

At the commandline:

  1. Open a terminal window as root or su to root.

  2. Enter the following commands as applicable:

    rug set-prefs proxy-url http://proxyserver.com:8080

    rug set-prefs proxy-username username

    rug set-prefs proxy-password password

In the Red Carpet GUI:

  1. Open the Red Carpet GUI

  2. Click Edit > Preferences.

  3. On the General tab, select the Use a Proxy option.

  4. Specify the Proxy URL, Username, and Password information in the respective fields.

  5. Click close.

Now the proxy settings for use by the web browser need to be made. Change the settings for the web browser

  1. Open YaST.

  2. Click Network Services > Proxy, then select Enable Proxy.

  3. Specify the HTTP Proxy URL, then click Finish.

Activate the changed proxy setting for the web browser by logging out of the browser then logging in again.

6.4.4 Stopping iPrint Services

If the server is running OES SP1 or later, you can skip this step.

If the server was installed when OES initially shipped, has not been updated to OES SP1 or later, and has iPrint installed, configured, and running, you must stop the iPrint Driver Store and iPrint Print Manager before applying patches.

You can stop these services by using iManager or by entering the following commands at a command line prompt.

Table 6-5 Commands for Stopping iPrint

Service

Command Line Command

iPrint Print Manager

/etc/init.d/novell-ipsmd stop

iPrint Driver Store

/etc/init.d/novell-idsd stop

To verify that these services are stopped, enter the following command at a command line prompt:

ps auxwww | grep iprint | grep -v grep

HINT:Issuing this command lists the processes that either are running as the iPrint user or contain iPrint in their names. If no processes are running, nothing is listed.

If for any reason the ipsmd services didn't stop, force these processes to stop by entering the following command at a console shell prompt:

killall ipsmd

If running the killall ipsmd command does not stop the processes, enter the following command at the console shell prompt:

killall -9 ipsmd

6.4.5 Downloading and Running the Prepatch Script for Red Carpet

If you plan to update the OES Linux server from the initial version or OES SP1 version to OES SP2 using Red Carpet command line (rug) or GUI utility, you must update the Red Carpet software by running the OES SP2 prepatch script (oessp2prepatch.sh).

If you are updating from CDs or ISO images instead of using Red Carpet, skip this procedure.

IMPORTANT:If you have already run the oessp2prepatch.sh script on the server, you do not need to run it again.

The patching software for OES and OES SP1 servers did not support the Red Carpet GUI for patches via the OES Update service. This OES SP2 prepatch script updates the Red Carpet software and a few other modules to ensure that the server is ready to receive the patches from the OES Update service. You need to install this patch on the server one time only.

  1. Locate and download the oessp2prepatch.sh file from the Consolidated Support Pack Web site for OES.

    Download the file to a local directory on the server, or download the file to a directory on a workstation, then copy the file from the workstation to a local directory on the server.

  2. If you are not already logged in as user root, log in to the server as user root or su to root.

  3. Set up the server for downloading patches.

    Completing the following steps ensures that the update service is correctly added, that the server is activated and subscribed to the correct channel, and that the correct patches are available in the channel.

    1. Add the OES Update service.

      If you haven't previously added or verified that the OES Update service was added, complete this step; otherwise, skip to Step 3.b.

      During the server’s initial installation, the OES Update service is automatically added to the server. Verify that the OES Update service was added correctly by entering the following command at a shell command line prompt:

      rug sl

      HINT:In this command, the last letter is a lowercase L, not the number 1.

      If the service was added correctly, you should see a message displayed similar to the following:

      Service List URL example

      The service list number in the # column is variable, depending on the number of services that the server is subscribed to.

      If the Novell Update service was not added correctly during the install, add it now by entering the following rug command with the Service Add option:

      rug sa https://update.novell.com/data

    2. Activate the Novell Update service.

      If you haven't previously activated the Novell Update service, complete this step; otherwise, skip to Step 3.c.

      At a shell command line prompt, enter

      rug act -s service_list_number activation_code email_address

      The service list number is the number for the Novell_Update_Server service. See Step 3.a.

      For example:

      rug act -s 1 123DE567890 jim@example.com

      HINT:The activation code can be an evaluation activation code or a standard activation code, depending on which licensing option you selected when you downloaded the product. If you enter an evaluation activation code, you can receive updates for 30 days.

      If you initially activate using an evaluation activation code and later purchase the product and receive a standard activation code, you can apply the standard activation code by repeating this step and entering the standard activation code. You do not need to deactivate the Novell Update service and reactivate it with the new activation code.

      If you entered the correct information, the system responds with the following message:

      System successfully activated
      Refreshing channel data
      Refresh complete
      
    3. Subscribe to the OES update channel.

      If the server hasn’t previously been subscribed to the OES update channel, complete this step; otherwise, skip to Step 3.d.

      At a command line prompt, enter

      rug sub oes

      If you enter this command and receive the message Warning: Invalid channel:'oes', see TID 10098375 “OES Patch Channel Not Visible after Activating Open Enterprise Server”.

    4. Verify that OES patches exists in the channel that the server is subscribed to.

      If you haven’t previously verified that OES patches exist in the subscribed channel, complete this step; otherwise, skip to Step 4.

      At a command line prompt, enter

      rug pl oes

      This command lists all patches available in the OES channel.

      HINT:If no patches are shown after running rug pl oes, enter rug refresh to refresh the channel, and then enter rug pl oes again.

  4. Make the oessp2prepatch.sh file executable by entering the following command:

    chmod +x oessp2prepatch.sh

    If you fail to make the oessp2prepatch.sh file executable, the following message is displayed when you try to apply the script:

    permission denied
    
  5. Apply the script by entering the following command at a shell command line prompt:

    ./oessp2prepatch.sh

    If you downloaded this file to a Windows workstation, then copied the file to the server before applying the script, the following error might be displayed when you apply the script:

    bad interpreter: No such file or directory
    

    If you see this error, run the dos2unix command with the filename as the parameter and run the script again.

    For example,

    dos2unix oessp2prepatch.sh

    IMPORTANT:The prepatch download and installation takes approximately 30 minutes when using a high-speed connection.

    The download and installation process is complete when you see the following message:

    ............................................................
    The Open Enterprise Server SP2 Pre-patch setup is complete.
    ............................................................
    ************************************************************
    Now you can finish patching the server.
    For instructions, see Patching an OES Linux Server at
    http://www.novell.com/documentation/oes/install_linux/data
    /bxlu3xc.html#bxlu3xc
    ************************************************************
    

6.4.6 Installing Additional Updates to Red Carpet

Since OES SP2 has been released, several patches have been released to update the Red Carpet command line and GUI utilities.These patches have been incorporated into the OES SP2 prepatch script. If you have already run this script on your server, the latest changes might or might not be installed on your server. The latest update is patch-11461.

To see whether this patch has already been installed, enter the following command at the shell command line prompt:

rug pi patch-11461

If this patch has been installed, the status shows the following:

Installed: Yes

To update the Red Carpet utility and refresh the server to show all the patches in the channel:

  1. If you are not already logged in as user root, log in to the server as user root or su to root.

  2. Entering the following command at a shell command line prompt:

    rug pin oes:patch-11147

  3. After the patch has been downloaded and installed, restart the rcd daemon using this command:

    rcrcd restart

  4. Refresh the channel and list the patches using these commands:

    • rug refresh
    • rug pl

6.4.7 Downloading the Updated ISO Images for Use with YaST Patch CD Update

To update an OES Linux server to OES SP2 only, you need to download and mount the ISO images and optionally burn CDs of them.

NOTE:If you are updating the server using the Red Carpet utility, you do not need to download the OES SP2 ISO images.

  1. Download the following required ISO images from the OES Consolidated Support Pack Web site:

    ISO Image File

    CD Label

    Screen Prompt When Patching from CD

    oessp2linux01.iso

    Open Enterprise Server SP2 CD 1

    NA

    oessp2linux02.iso

    Open Enterprise Server SP2 CD 2

    YOU Patch CD CD 2

    oessp2linux03.iso

    Open Enterprise Server SP2 CD 3

    YOU Patch CD CD 3

  2. (Conditional) If you are updating the server from physical CDs via the YaST Patch CD Update, you must burn the ISO images to CDs:

    1. Insert a blank, writable CD into your CD burner.

    2. Select the option to create a CD from an image file.

    3. Select ISO as the file type.

    4. Select an image file (see Step 1) from the location you downloaded it to.

    5. Complete the CD creation process.

    6. Repeat this process for each of the ISO image files.

      Your CDs are now ready to be used for patching.

  3. (Conditional) If you are updating the server from local ISO images via the YaST Patch CD Update, you need to mount the local ISO files:

    1. Create a directory for each of the images in the /mnt directory.

      For example, create the iso-1, iso-2, and iso-3 directories in the /mnt directory by entering the following commands:

      mkdir /mnt/iso-1
      
      mkdir /mnt/iso-2
      
      mkdir /mnt/iso-3
      
    2. Mount each of the the images by entering the following command at a command line prompt:

      mount -o loop /path/isofilename /mnt/isodirname

      For example:

      If you have saved the files in the /home/download/patchcd directory, you would enter the following command to mount the first ISO image:

      mount -o loop /home/download/patchcd/oessp2linux01.iso /mnt/iso-1

      Repeat the mount command for each image.

  4. (Conditional) If you are updating the server from ISO images on the network via the YaST Patch CD Update, you need to make a note of the network path so you can access them when you update using the OES Update channel in Red Carpet.

6.4.8 What’s Next

When you have completed all the applicable steps for preparing the server, you can proceed with patching the server using one of the following methods.

For more information about which method you might want to choose, see Table 6-3.