Local up2date server setup for RHEL Enterprise 3, 4

Posted on 2006-05-08
Last Modified: 2013-12-16

   I've a mixes of RHEL Enterprise WS, AS machines running version 3 and 4. Both i686 and x64 architecture. How can I create a local update repository to update all my machines from our local up2date server. To save on bandwidth and time. We have around 100+ machines.
   Please give a detailed step by step instruction. We have all the CDs and are registered to all RHEL channel. I would appreciate a detailed setup of the server for diff architecture and version and what needs to be modify on the clients side to use the new up2date server.

On a side note: Is there an easy way to upgrade WS or AS from 3 to 4. Using network kickstart, or create an upgrade CD/DVD.
Question by:n0thing
    LVL 14

    Accepted Solution


    A short answer to a long question: Buy a RHN Satellite Server (a product from Red Hat to manage your boxes, like Red Hat Network but you have your own server)

    From that you can;
    -kickstart boxes
    -apply / rollback rpm's
    -manage configuration files (apply / rollback)
    -group boxes and work with groups instead of a single box

    There is no other (supported way) to use up2date...

    If you don't want that (or can't afford it) look at yum to do the same thing. (

    >On a side note: Is there an easy way to upgrade WS or AS from 3 to 4. Using network kickstart, or create an upgrade CD/DVD.
    No! ;-)

    In my experience there is no way to do this and be sure it works all the way.

    (I have worked at Red Hat and done numerous installes...)


    LVL 15

    Assisted Solution

    A shorter answer: don't buy RHN Sattelite Server.

    On the server that is fully subscribed to RHN, locate the file /etc/sysconfig/rhn/up2date . Edit this file and set the parameter keepAfterInstall to 1:

    KeepAfterInstall[comment]=Keep packages on disk after installation

    This will keep all new RPMs as they come.

    Second, copy all RPMs from the CD's to /var/spool/up2date.

    Third, create the following shell script somewhere (we'll turn our bunch of downloaded RPM's into a yum repo):

    yum-arch -q /var/spool/up2date

    I do it daily in /etc/cron.daily, right ufter u2pdate -u, you can do it however you like. Run it once after you create it to create a yum repo.

    Configure a webserver with /var/spool/up2date as DocumentRoot directory. This webserver will serve your yum repository. For this example, let's say this is

    On a new RHEL server (IMPORTANT!), before you run up2date the first time, you edit /etc/sysconfig/rhn/sources file this way:

    a) we need to locate the line:

    up2date default

    and comment it out like:

    #up2date default

    b) we need to add at the end:

    yum MyRepo

    That's it. Now, if you HAD run up2date on this server and instead of updating from your repository up2date -u asks you to register, you need to remove up2date:

    rpm -e up2date

    and reinstall it again: you can do it over HTTP like

    rpm -i

    and try again.

    NOTE: as far as I was told by RedHat, you still need to buy separate licenses for each of your RHEL servers. However, this setup will save you some dough on RHN Sattelite Server.

    LVL 14

    Expert Comment


    Using yum (as you are through up2date) is a good solution. An even better one is to setup a proxy-server and run up2date normally. (IMHO)

    But at least now you have some options!

    Good luck,



    Featured Post

    Maximize Your Threat Intelligence Reporting

    Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

    Join & Write a Comment

    How many times have you wanted to quickly do the same thing to a list but found yourself typing it again and again? I first figured out a small time saver with the up arrow to recall the last command but that can only get you so far if you have a bi…
    It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
    Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
    Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now