Setting up a local update server for SLE 10 with YUP
This document (3065146) is provided subject to the disclaimer at the end of this document.
To configure and use a local update service by using "yup" (Yum Update Proxy) for SUSE Linux Enterprise 10 (SLE 10) packages in order to lower bandwidth usage and to be able to perform updates faster.
Please note, that as of July 2008 yup is deprecated. It has been replaced by SMT (Subscription Management Tool for SUSE Linux Enterprise). This tool acts as Novell Customer Center proxy both for client registrations and as software update repository for SLES/SLED 9 and 10 clients. It runs on a SLES 10 SP2 server. You will find an overview on the SMT products page. Furtheron the Novell Appnote Keep your SUSE Linux Desktops, Servers and OES Servers Updated with Subscription Management Tool for SUSE Linux Enterprise gives an overview of its features as well as instructions on how to implement it. For information on how to migrate from yup to SMT see TID 7000848, Migrating from YUP to SMT.
Please also refer to the Additional Notes section below for information about the support status of yup and for other alternative approaches.
A system running a SUSE Linux Enterprise 10 product or SUSE Linux Enterprise Server 9 can be configured by to mirror package updates for SLE 10 from the Novell update service and make these updates accessible to local clients. In this example configuration, an FTP server is used to offer the updates to clients; other protocols can be used instead (like HTTP or NFS), but will not be covered here.
- Install the "yup"
(Yum Update Proxy)
package. This package provides the "yup" command which allows
mirroring of updates to the local file system.
Please note that this package is not part of the core product; it is part of the software development kit (SDK) which is a separate product. Thus, the "yup" package for use on SLE10 is part of the SLE SDK 10 and the "yup" package for use on SLES9 is part of the SLES9 SDK. In both cases, the"yup" package was not included in the initial release of the SDK but was added to them as an online update later.
- Install the "vsftpd" package.
- Runyupand follow its instructions on how to configure it. For the destination path, use/srv/ftp/SLE10-YUP.
As yup needs to mirror downloads which require authentication, yup's configuration needs to include the authentication credentials for the appropriate product(s). These credentials, the machine ID and the machine secret are 32-character hex strings which need to be copied from the /etc/zmd/deviceid and/etc/zmd/secret files of a system which runs the SLE10 product(s) to be mirrored and which has already been registered successfully for online updates.
- Runyupto mirror the updates.
- Runinsserv vsftpdto enable the FTP service.
- Configure a cron job callingyup
to regularly refresh the mirror. See TID
scripts or commands with cron for
Client system configuration
To make a client system use the local update service, execute the following commands:
- Add the update
service:rug service-add ftp://the.local.yup.server/SLE10-YUP/product/architecture --type yum local-yupe.g.ftp://10.23.1.42/SLE10-YUP/SLES10/i586 --type yum local-yup
- Subscribe to
the update channel:rug subscribe local-yup
information about available updates:rug refresh
- And proceed to
perform updates as usual, e.g.rug list-updatesto list updates andrug updateto actually update.
Yup is unsupported software. For a supported solution, use the SUSE Linux Enterprise Subscription Management Tool or the ZENworks Linux Management product.
With the release of SLE10 SP1, there have been some changes to the update server infrastructure which required changes in Yup in turn. To succesfully set up Yup for locally mirroring SLE10 SP1, a recent Yup version is necessary. The first Yup version to support mirroring SLE10 SP1 is 222-2.4 (for SLE10 Yup servers; zypp patch 3853) or 222-3.1 (for SLES9 Yup servers; from patch-11571); refer to Recommended update for yup.
Older Yup versions do not mirror all files necessary for clients. This typically manifest as clients of the Yup update server not being able to update due to a missing product.xml file.
Local update service for SLES 8 and SLES9
Earlier releases of SUSE Linux Enterprise products use a different update mechanism, YaST Online Update. A local update service can be configured for this mechanism as well; refer to the article Set Up A Local YaST Online Update Server.
Berthold Gunreben, Mirroring Update Servers, Novell Cool Solutions.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3065146
- Creation Date: 27-Feb-2008
- Modified Date:03-Mar-2020
- Subscription Management Tool
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Software Development Kit
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com