Oracle Legal Notices
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
License Restrictions Warranty/Consequential Damages Disclaimer
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
Restricted Rights Notice
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
Hazardous Applications Notice
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Third-Party Content, Products, and Services Disclaimer
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Alpha and Beta Draft Documentation Notice Disclaimer
If this document is in preproduction status:
This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
This document contains information about the Spacewalk 2.0 release available from Oracle. It describes the differences from the upstream version, includes notes on installing and configuring Spacewalk, and provides a statement of what is supported.
Document generated on: 2013-11-11 (revision: 1442)
Table of Contents
The Spacewalk 2.0 for Oracle Linux Release Notes provides details of the Spacewalk 2.0 release available from Oracle.
This document is written for system administrators who want to use the Unbreakable Enterprise Kernel with Oracle Linux. It is assumed that readers have a general understanding of the Linux operating system.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
The following text conventions are used in this document:
Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
There are no significant changes in the Oracle version of Spacewalk from the upstream project.
Minor changes include:
Addition of Oracle Linux 6 GPG keys
Addition of Oracle Linux repositories to the spacewalk‑common‑channels tool
Spacewalk provided by Oracle is only supported on Oracle Linux 6 (x86_64).
You should install Oracle Linux 6 using the
Basic Server software set.
If you select additional package groups during installation,
you must remove the
jta package before
installing Spacewalk, as this package causes Spacewalk
services to fail to start.
Only install Spacewalk using the packages provided by Oracle from the Oracle Public Yum repository at http://public-yum.oracle.com.
No third‑party package repositories are required to install Spacewalk on Oracle Linux 6. All the required packages are available in the Oracle Linux Spacewalk repository.
A database is required to store the Spacewalk data. The database options are:
Oracle Database Express Edition (Oracle Database XE)
Oracle only supports Oracle Database for use with Spacewalk. Oracle Database XE and PostgreSQL are not supported.
Oracle does not provide any tools for migrating from an unsupported database.
You must have an Oracle Database server installed and available before you install Spacewalk.
Only Oracle Database 11gR2 (release 18.104.22.168 or later) is supported. Oracle Database 12c is not supported. To obtain the correct Oracle Database 11gR2 release, you must download the software from My Oracle Support (MOS) at https://support.oracle.com.
Documentation for Oracle database is available at http://www.oracle.com/pls/db112/homepage.
The database must be configured as follows:
The database must use the
The database must have a user named
spacewalk user must have the
spacewalk user must have the
TABLESPACE system privileges.
To create the
spacewalk user with a
password of "password" using SQL, the following SQL*Plus
commands can be used:
create user spacewalk identified by password;SQL>
grant connect,resource to spacewalk;SQL>
grant alter session, create synonym, create table, create trigger, create view to spacewalk;SQL>
grant unlimited tablespace to spacewalk;
To connect to an Oracle Database, Oracle Instant Client 22.214.171.124 packages must be installed on the Spacewalk server. The Spacewalk server configuration fails if these packages are missing.
You can download the packages from:
The following are the required packages:
Once you have installed the Oracle Instant Client, you must add the library path to ldconfig as follows:
echo /usr/lib/oracle/11.2/client64/lib > /etc/ld.so.conf.d/oracle‑instantclient11.2.conf#
To ensure that errata mapping is maintained for all versions of each package, Spacewalk mirrors all available versions of all available packages. As a result, the storage requirements for a Spacewalk server can be significant, based on the number of major versions and architectures you chose to support. As a guide, the Oracle Linux binary repositories require approximately 50GB for each architecture, with an extra 30-40GB required for source packages.
Packages are never removed from Oracle Linux repositories, so the space required for each repository only ever increases. You should actively monitor the available disk space on the Spacewalk server.
If you use a local yum server to mirror ULN (see the section called “Using Unbreakable Linux Network (ULN) Instead of Oracle Public Yum”), you require double the amount of disk space because packages are stored on the yum mirror server as well as the Spacewalk server.
You must configure the Spacewalk server with a fully-qualified domain name (FQDN). Clients must be able to resolve the FQDN in DNS (forward and reverse lookups), otherwise PXE booting does not work.
The following table shows the required network ports depending on the configuration of the Spacewalk server.
Port and Protocol
tftp for PXE provisioning support
Spacewalk web access
Spacewalk web access
Spacewalk client push support
Spacewalk proxy push support
Enable access to the Spacewalk Server repository.
Spacewalk is installed from the Oracle Public Yum server at http://public-yum.oracle.com.
file with the following content:
[ol6_spacewalk20_server] name=Spacewalk Server 2.0 for Oracle Linux 6 ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/spacewalk20/server/$basearch/ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle gpgcheck=1 enabled=1
yum install spacewalk-oracle
If you are using an Oracle database, either on the same server or on a remote server, use the following command:
spacewalk-setup --disconnected --external-db
Otherwise, use the following command:
The following example shows an interactive configuration:
spacewalk-setup --disconnected --external-db* Setting up Oracle environment. * Setting up database. ** Database: Setting up database connection for Oracle backend. Database service name (SID)?
<orcl.domain.com>Database hostname [localhost]?
**Database: Testing database connection. ** Database: Populating database. *** Progress: ############################################################ * Setting up users and groups. ** GPG: Initializing GPG and importing key. ** GPG: Creating /root/.gnupg directory You must enter an email address. Admin Email Address?
<email@example.com>* Performing initial configuration. * Activating Spacewalk. ** Loading Spacewalk Certificate. ** Verifying certificate locally. ** Activating Spacewalk. * Enabling Monitoring. * Configuring apache SSL virtual host. Should setup configure apache's default ssl server for you (saves original ssl.conf) [Y]? ** /etc/httpd/conf.d/ssl.conf has been backed up to ssl.conf-swsave * Configuring tomcat. ** /etc/sysconfig//tomcat6 has been backed up to tomcat6-swsave ** /etc/tomcat6//server.xml has been backed up to server.xml-swsave ** /etc/tomcat6//web.xml has been backed up to web.xml-swsave * Configuring jabberd. * Creating SSL certificates. CA certificate password? Re-enter CA certificate password? Organization?
<Oracle Demo>Organization Unit [spacewalk.domain.com]? Email Address [firstname.lastname@example.org]? City?
<CA>Country code (Examples: "US", "JP", "IN", or type "?" to see a list)?
<US>** SSL: Generating CA certificate. ** SSL: Deploying CA certificate. ** SSL: Generating server certificate. ** SSL: Storing SSL certificates. * Deploying configuration files. * Update configuration in database. * Setting up Cobbler.. Processing /etc/cobbler/modules.conf `/etc/cobbler/modules.conf' -> `/etc/cobbler/modules.conf-swsave' Processing /etc/cobbler/settings `/etc/cobbler/settings' -> `/etc/cobbler/settings-swsave' cobblerd does not appear to be running/accessible Cobbler requires tftp and xinetd services be turned on for PXE provisioning functionality. Enable these services [Y]? cobblerd does not appear to be running/accessible * Restarting services. Installation complete. Visit https://spacewalk.domain.com to create the Spacewalk administrator account.
Oracle Linux channels can be configured using the
command provided in the
spacewalk‑utils package. This
command can automatically configure the required software
channels, yum repositories, GPG keys and activation keys for
both Oracle Linux 5 and 6.
The following channels can be created using the spacewalk-common-channels command:
For Oracle Linux 6 (i386 and x86_64):
oraclelinux6 (base channel)
For Oracle Linux 5 (i386 and x86_64):
oraclelinux5 (base channel)
For example, to create 32‑bit and 64‑bit
software channels for Oracle Linux 6, install the
spacewalk‑utils package and then run
tool, as follows:
yum install spacewalk‑utils#
spacewalk‑common‑channels -v -u
<password>-a i386,x86_64 -k unlimited ‘oraclelinux6*’
Use the spacewalk‑common‑channels -h command to see full usage information.
The spacewalk‑common‑channels tool uses the Oracle Public Yum repository as the source for packages. You might prefer to use the Unbreakable Linux Network (ULN) instead, however Oracle currently does not support a direct connection between Spacewalk and ULN. The workaround is use an intermediate yum server to mirror packages from ULN and provide them to Spacewalk, but be aware that this requires double the amount of disk space because packages will be stored on the intermediate yum mirror server as well as the Spacewalk server. Details on how to configure an intermediate yum mirror server can be found on the Oracle Technology Network at:
Once you have configured the software channels, you can synchronize the software either by performing an immediate manual synchronization or by scheduling a recurring synchronization job.
As a minimum, Oracle recommends that you update the Oracle Linux 5 and Oracle Linux 6 latest channels daily.
The initial synchronization of the Oracle Linux 5 and Oracle Linux 6 channels can take several days to complete. Oracle recommends that you perform an initial manual synchronization to populate the channels, and then configure a recurring job to keep them updated.
You synchronize software as follows:
In the Spacewalk web interface, go to Channels, then Software Channels, and select the required channel.
Select Repositories, and then Sync.
Synchronize the software.
To perform an immediate manual synchronization, click the Sync Now button.
To schedule a recurring synchronization job, select the preferred schedule, and click the Schedule button.
After you have configured and synchronized the software channels, you must create an activation key so that servers can register to those channels.
Create an activation key for each base channel and architecture you configured. If you configured all the channels, you need four activation keys, two for Oracle Linux 5 (i386 and x86_64) and two for Oracle Linux 6 (i386 and x86_64).
You synchronize software as follows:
In the Spacewalk web interface, go to Systems, and then Activation Keys.
Click Create New Key.
Oracle recommends that you do not use the generate
function to create an activation key. Instead, create a
key with a label that is easy to understand, for example
based on the version number and architecture
oraclelinux6-x86_64), or based on the
server type (
appserver). Spacewalk automatically
adds a number to the activation key label. For example, if
oraclelinux-x86_64 as the
label, the key that is actually created might be called
1-oraclelinux-x86_64. This enables you
to create multiple activation keys for the same base
channel, each with different configuration options. The
name you use is presented during Spacewalk client
registration and creating your own key labels helps you to
select the right key.
Oracle provides Spacewalk client packages for Oracle Linux 5 and 6 for both i386 and x86_64 architectures. Oracle supports only Oracle Linux servers as Spacewalk clients.
If the Spacewalk Client channel provided by Oracle is mirrored on the Spacewalk server, the Spacewalk client is installed automatically on servers that are provisioned from Spacewalk. The Spacewalk Client channel can be configured using the spacewalk-common-channels command, as described in Section 1.2.6, “Configuring and Synchronizing Software Channels”.
For an Oracle Linux server that is not yet connected to Spacewalk, you install the Spacewalk client and register the server, as follows:
Enable access to the Spacewalk Client repository.
file with the following content:
For Oracle Linux 6 servers:
[ol6_spacewalk20_client] name=Spacewalk Client 2.0 for Oracle Linux 6 ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/spacewalk20/client/$basearch/ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle gpgcheck=1 enabled=1
For Oracle Linux 5 servers:
[ol5_spacewalk20_client] name=Spacewalk Client 2.0 for Oracle Linux 5 ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/spacewalk20/client/$basearch/ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle gpgcheck=1 enabled=1
Install the Spacewalk client.
(Oracle Linux 5 servers
only) Before you install the Spacewalk client,
up2date‑gnome packages manually
using the rpm -e --nodeps command.
Use the following command to install the Spacewalk client on both Oracle Linux 5 and Oracle Linux 6 servers:
yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin
The above command replaces the existing packages and deletes a registered server from ULN.
Register the server with Spacewalk using the rhnreg_ks command.
Before you can register a server, you must have already created a client activation key, as described in Section 1.2.7, “Creating Activation Keys for Spacewalk Clients”.
You cannot use the rhn_register command to register a server with Spacewalk because this command cannot use Spacewalk activation keys.
Disable access to the Spacewalk Client repository.
In some circumstances, the Spacewalk installation can fail if
slf4j (Simple Logging Facade for Java)
package is installed. The workaround is to remove the
slf4j package. Be aware that Eclipse
depends on this package, so you either have to uninstall
Eclipse or remove the package with the rpm -e
--nodeps slf4j command.
If Tomcat fails to start after the initial configuration of
Spacewalk, check that the
package is installed. If Oracle Linux is installed using a
software set other than
Basic Server, the
jta package might be installed on the
system and the presence of this package prevents the
package from being installed. If the
package is missing, you might have to install it manually,
after removing the
jta package. The
package is required to ensure that all the Spacewalk services
The Spacewalk client conflicts with the
up2date client installed by default for
connectivity to the Unbreakable Linux Network. Before you
install the Spacewalk client for Oracle Linux 5, remove the
up2date‑gnome packages manually
using the rpm -e --nodeps command.
If the Spacewalk server was installed without a fully-qualified domain name (FQDN), or a name that cannot be resolved in DNS, Spacewalk creates invalid PXE boot configuration files.
You can validate that Cobbler is configured correctly by checking that the IP address
used in the
ks= parameter in the
/var/lib/tftpboot/pxelinux.cfg/default file is correct.
To reconfigure a Spacewalk server after installation:
and change all instances of incorrect host names, such as
Restart Spacewalk by running spacewalk-service restart.
Resynchronise Cobbler by running cobbler sync.
Release notes for the Spacewalk project can be found at:
User documentation for the Spacewalk project can be found at: