Grant Gainey edited this page Dec 12, 2016 · 2 revisions
Clone this wiki locally

Spacewalk Installation Instructions

These are installation instruction for new installations of Spacewalk 1.3. If you are upgrading from older versions, see HowToUpgrade.

Spacewalk 1.2 installation instructions are available at HowToInstall12.


  • Outbound open ports 80, 443, 4545 (only if you want to enable monitoring)
  • Inbound open ports 80, 443, 5222 (only if you want to push actions to client machines) and 5269 (only for push actions to a Spacewalk Proxy), 69 udp if you want to use tftp
  • Storage for database: 250 KiB per client system + 500 KiB per channel + 230 KiB per package in channel (i.e. 1.1GiB for channel with 5000 packages)
  • Storage for packages (default /var/satellite): Depends on what you're storing; Red Hat recommend 6GB per channel for their channels
  • 2GB RAM minimum, 4GB recommended
  • Make sure your underlying OS up-to-date.
  • If you use LDAP as a central identity service and wish to pull user and group information from it, see SpacewalkWithLDAP

Setting up Spacewalk repo

RPM downloads of the project are available through a yum repository

To use this repository install spacewalk-repo with commands below:

Red Hat Enterprise Linux 5, CentOS

rpm -Uvh

Red Hat Enterprise Linux 6

rpm -Uvh

Fedora 13

rpm -Uvh

Fedora 14

rpm -Uvh

Nightly builds

If you want to use the nightly builds, add a .repo file pointing to the nightly repository.


cat > /etc/yum.repos.d/spacewalk.repo << 'EOF'
# RHEL 5 / CentOS 5
# RHEL 6
# Fedora 13
# Fedora 14


cat > /etc/yum.repos.d/spacewalk-client.repo << 'EOF'
# RHEL 5 / CentOS 5
# RHEL 6
# Fedora 13
# Fedora 14

NOTE: Nigthly repo contains developers snapshot and is not suitable in production environment.

Additional repos & packages

Jpackage repository

RHEL 6 and Fedora 13 & 14

For Spacewalk on RHEL6 and Fedora, a couple of additional dependencies are needed from jpackage. Please create the following yum repository before beginning your Spacewalk installation:

cat > /etc/yum.repos.d/jpackage-generic.repo << EOF
name=JPackage generic

We specifically want 5.0 generic directory in the above URL. Make sure, you do not use the jpackage-generic repository on RHEL5.

EPEL repository

Spacewalk requires a Java Virtual Machine with version 1.6.0 or greater. EPEL - Extra Packages for Enterprise Linux contains a version of the openjdk that works with Spacewalk. Other dependencies can get installed from EPEL as well. To get packages from EPEL just install this RPM:

EPEL5 (use for RHEL5)

rpm -Uvh

EPEL6 (use for RHEL6)

rpm -Uvh

Please make sure you have only one java version installed. Otherwise you get error messeges like :

  • " bad major version at off set=6" or
  • "INFO: validateJarFile(/usr/share/tomcat5/webapps/rhn/WEB-INF/lib/jspapi.jar) - jar not loaded."

When using RHEL6, make suer you are subscribed to following channels as well:

  • Red Hat High Availability Server 6
  • Red Hat Optional Server 6

CentOS 5

Follow the instructions to use EPEL5 with the additions:

Oracle Pre-Requisites

In order to get Spacewalk to run with Oracle database backend, you need the Oracle client and an Oracle 10g or 11g database server. The easiest way to do this is to install Oracle XE and the Oracle Instant Client. Instructions on how to do this can be found on the Oracle 10g Express Edition Setup page.

PostgreSQL Pre-Requisites

In order to get Spacewalk ro run with PostgreSQL database backend, you need PostgreSQL 8.4 server installed on the same or different machine. Use PostgreSQLServerSetup as a guide to get the server installed and setup.

Please note that the functionality of Spacewalk on PostgreSQL is very limited and sooner than later you will hit weird behaviour or Internal Server Error.

Conflicting Packages

There is an open bug 593402 that identifies the package cobbler-web as conflicting with Spacewalk's Taskomatic process. Until the issue is addressed, it is recommended that the cobbler-web package be removed from the Spacewalk server.

yum remove cobbler-web

Yum can also be configured to exclude that package in the future by adding the following entry to the main section in /etc/yum.conf:

vi /etc/yum.conf


There is a workaround to be able to install cobbler-web and use it alongside Spacewalk. Instructions can be found at CobblerWebWorkaround.

Installing Spacewalk

Just ask yum to install the necessary packages. This will pull down and install the set of RPMs required to get Spacewalk to run.

If you tend to use the Oracle backend:

yum install spacewalk-oracle 

If you prefer the PostgreSQL backend:

yum install spacewalk-postgresql 

Note: Please note that the functionality of Spacewalk on PostgreSQL is very limited. You may want to take a look at the PostgreSQL page for further information.

Configuring the firewall

Spacewalk needs different inbound ports to be connectible. Assuming you have a default RHEL5/CentOS5 set up, proceed as following:

iptables -D RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
iptables -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 443 -j ACCEPT
iptables -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 80 -j ACCEPT
iptables -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
service iptables save
service iptables restart

Add port 5222 if you want to push actions to client machines and 5269 for push actions to a Spacewalk Proxy, 69 udp if you want to use tftp.

Configuring Spacewalk

Note: Your Spacewalk server should have a resolvable FQDN such as ''. If the installer complains that the hostname is not the FQDN, do not use the --skip-fqdn-test flag to skip !

Also, the setup requires that the database account has a password. Please don't use '#' (number sign/pound/hash) in your database password otherwise installation will fail.

Once the Spacewalk RPM is installed you need to configure the application, you can run:

spacewalk-setup --disconnected

An example session is as follows:

# spacewalk-setup --disconnected
* Setting up Oracle environment.
* Setting up database.
** Database: Setting up database connection for Oracle backend.
Database service name (SID)? XE
Username? spacewalk
** 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? root@localhost
* 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/tomcat5/tomcat5.conf has been backed up to tomcat5.conf-swsave
** /etc/tomcat5/server.xml has been backed up to server.xml-swsave
** /etc/tomcat5/web.xml has been backed up to web.xml-swsave
* Configuring jabberd.
* Creating SSL certificates.
CA certificate password? 
Re-enter CA certificate password? 
Organization? Fedora
Organization Unit []? Spacewalk Unit
Email Address [root@localhost]? 
City? Brno
State? CZ
Country code (Examples: "US", "JP", "IN", or type "?" to see a list)? CZ
** 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..
Cobbler requires tftp and xinetd services be turned on for PXE provisioning functionality. Enable these services [Y/n]?
cobblerd does not appear to be running/accessible
* Restarting services.
Installation complete.
Visit to create the Spacewalk administrator account.

Configuring Spacewalk with an Answer File

You can also configure spacewalk by using an answer file. To configure spacewalk by using an answer you just need to run the following

spacewalk-setup --disconnected --answer-file=<FILENAME>

An example answer file is as follows

admin-email = root@localhost
ssl-set-org = Spacewalk Org
ssl-set-org-unit = spacewalk
ssl-set-city = My City
ssl-set-state = My State
ssl-set-country = US
ssl-password = spacewalk
ssl-set-email = root@localhost
ssl-config-sslvhost = Y

NOTE: If you do not supply a value or leave out a key you will be prompted to supply that answer

For Postgres you need to create something like this

admin-email = root@localhost
ssl-set-org = Spacewalk Org
ssl-set-org-unit = spacewalk
ssl-set-city = My City
ssl-set-state = My State
ssl-set-country = US
ssl-password = spacewalk
ssl-set-email = root@localhost
ssl-config-sslvhost = Y

After spacewalk-setup is complete your application is ready to go! Be sure to use the FQDN of the host when you connect.

Once you've made sure you can login to the Spacewalk web UI, you can then proceed to the next step: Uploading Content.

Managing Spacewalk

Spacewalk consists of several services. Each of them has its own init.d script to stop/start/restart. If you want manage all spacewalk services at once use

/usr/sbin/spacewalk-service [stop|start|restart].

Known Issues

  • For issues with Oracle XE, see Oracle XE Setup Known Issues

  • You can find following messages: /usr/share/tomcat6/logs/catalina.2011-02-03.log (Permission denied) in /var/log/tomcat6/catalina.out on RHEL6. The reason is a bug in tomcat6. Workaround:

    chmod g+w /var/log/tomcat6

  • if installing Spacewalk with oracle DB on Fedora14, you might get selinux AVC denials containing oracledb_port_t type Workaround: do not use selinux-policy-targeted-3.9.7-28.fc14.noarch, install a newer (or older) policy before the install process