JavaScript must be enabled to correctly display this content

The software described in this documentation is either no longer supported or is in extended support.
Oracle recommends that you upgrade to a current supported release.

Chapter 1 Installing and Upgrading Spacewalk Servers

This chapter describes how to install and upgrade Spacewalk servers and proxies.

1.1 Oracle Linux Requirements

Oracle supports Spacewalk servers that are running on Oracle Linux 6 (x86_64) or Oracle Linux 7 (x86_64). Oracle recommends that you update Oracle Linux with the latest packages that are available on the Oracle Linux yum server.

Note

Do not register a Spacewalk server or client with ULN. You can register a Spacewalk server as a client of itself to receive updates.

You should install Oracle Linux 6 or Oracle Linux 7 by using either the Minimal or Basic Server software set. If you select additional package groups during installation, remove the jta package before installing Spacewalk, as this package causes Spacewalk services to fail to start.

Install Spacewalk by using only the packages that are provided by Oracle from the Oracle Linux yum server at https://yum.oracle.com.

No third-party package repositories are required to install Spacewalk on Oracle Linux 6 or Oracle Linux 7. All of the required packages are available in the Spacewalk repositories on the Oracle Linux yum server.

1.2 Storage Requirements for a Spacewalk Server

A Spacewalk server should have a minimum of 8 GB of memory. If the Spacewalk server also runs the database that stores the Spacewalk repository, this memory requirement is in addition to what is required to run the database.

To preserve errata mapping, by default, Spacewalk maintains all available versions of all available packages in each software channel that you configure. As a result, the storage requirements for a Spacewalk server can be significant, depending on the number of major versions and architectures that you choose to support. Typically, the Oracle Linux binary repositories require approximately 60 GB for each combination of Oracle Linux release and architecture. An extra 40 GB is required for source packages and 80 GB is required for Ksplice updates for each combination of Oracle Linux release and architecture.

Note

With Spacewalk 2.6, you can reduce the storage requirements considerably by specifying the --latest option to the spacewalk-repo-sync command, which causes the server to synchronize only the latest packages that are available at the time of synchronization. It does not remove older packages from the channel. If the synchronization interval is large, you might miss a particular version of a package, which can have implications for errata handling, where errata are associated with specific package versions. If errata consistency is important to you, Oracle recommends that you do not use --latest. However, using --latest with a Ksplice channel is an exception because its packages are always cumulative.

Caution

Packages are never removed from Oracle Linux repositories, so the space that is required for each repository only ever increases. You should actively monitor the available disk space on the Spacewalk server.

A Spacewalk server stores the packages that it hosts under the /var/satellite/redhat directory hierarchy. You should plan how best to configure the /var file system before you install Spacewalk. For example, if you set up /var as an ext4 or XFS file system by using Logical Volume Manager (LVM), you can expand the storage when required.

1.3 Networking Requirements for a Spacewalk Server

Prior to installing a Spacewalk server, refer to the following networking requirements and configuration information:

Configure a fully qualified domain name

You must configure a fully qualified domain name (FQDN) for the Spacewalk server. Note that Spacewalk does not consider .local and .localdomain to be valid domain names.

Caution

The Spacewalk server and clients must be able to resolve the Spacewalk server's FQDN for both forward and reverse lookups in DNS. If these conditions are not met, neither certificate validation nor PXE booting work. In addition, clients cannot register with the Spacewalk server. In particular, a lack of reverse DNS lookup causes Inter-Server Synchronization (ISS) to fail.

Also, verify that the host name that is returned by the hostname command and the value of HOSTNAME that is defined in the /etc/hostname file (for Oracle Linux 7) or the /etc/sysconfig/network file (for Oracle Linux 5 and Oracle Linux 6) are identical.

As shown in the following example, the host name must be consistent with the FQDN that is defined for the system in DNS, for both forward and reverse lookups:
```
# hostname
swksvr.mydom.com
# grep HOSTNAME /etc/sysconfig/network
HOSTNAME=swksvr.mydom.com
```
You can also use the host command to verify this information on systems that are running Oracle Linux 5 and Oracle Linux 6:
```
# host swksvr.mydom.com
swksvr.mydom.com has address 192.168.1.3
# host 192.168.1.3
3.1.168.192.in-addr.arpa domain name pointer swksvr.mydom.com.
```
You will need to edit the /etc/hosts file and configure the actual IP address for the FQDN and host name, but not the loopback address (127.0.0.1), as shown in the following example:
```
127.0.0.1      localhost localhost.localdomain localhost4 localhost4.localdomain4
::1            localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.3    swksvr.mydom.com swksvr
```

Port numbers for a Spacewalk server

The following table describes the network ports that a Spacewalk server uses, depending on its configuration.

Port/Protocol	Direction	Purpose
69/udp	Inbound	TFTP (if PXE provisioning support is required)
80/tcp	Inbound and outbound	HTTP access
443/tcp	Inbound and outbound	HTTPS access
5222/tcp	Inbound	Push support to Spacewalk clients (if required)
5269/tcp	Inbound	Push support to Spacewalk proxies (if required)

Configure network time synchronization

Configure the Spacewalk server, proxies, and clients to use a network time synchronization mechanism such as the Network Time Protocol (NTP) or the Precision Time Protocol (PTP). In order to establish a Secure Socket Layer (SSL) based connection, Spacewalk requires that the system time on these systems be consistent to within 120 seconds. Furthermore, if the system times (corrected for time zone difference) of the server and a client differ by more than 120 seconds, authentication of the osad service on the client by the jabberd service on the server fails.

For more information, see Oracle® Linux 6: Administrator's Guide or Oracle® Linux 7: Administrator's Guide.

1.4 Database Requirements

You can use the following database solutions to store Spacewalk data:

Oracle Database
Oracle Database Express Edition (Oracle Database XE)
PostgreSQL

However, note that Oracle supports only Oracle Database for use with Spacewalk and provides a restricted-use license for the use of Oracle Database 12c Enterprise Edition for Oracle Linux support customers. For more information, see Oracle® Linux 6: Licensing Information User Manual or Oracle® Linux 7: Licensing Information User Manual.

Note

Oracle Database XE (Oracle Database Express Edition) and PostgreSQL are not supported and their use is not described in this document. Note also that Oracle does not provide any tools for migrating from an unsupported database.

1.4.1 Database Sizing Requirements

When determining the amount of space the Spacewalk database requires, be sure to include sizing estimates for the following in your overall calculation: number of client systems that will be served by the Spacewalk server, number of channels allocated to each client system, as well as the number of packages that each channel will contain.

To more accurately determine how much space the Spacewalk database requires, use the following calculation:

250 KiB per client system.
500 KiB per channel, plus an additional 230 KiB per package in the channel (a channel with 5000 packages would require 1.1 GiB).

For example, if you have a large Spacewalk server that is serving 10,000 systems, and each system has four channels that contain 12,000 packages per-channel, then 2.5 GiB would be required for the clients and 11 GiB would be required for the channels.

1.4.2 Oracle Database Installation Requirements

You must install an Oracle Database server and make this server available before you install Spacewalk.

Supported Oracle Database releases include the following:

Oracle Database 12c.

You can download the software from the Oracle Technology Network (OTN) at https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html.
Oracle Database 11gR2, release 11.2.0.3 or later (requires an active Oracle Database license).

To obtain the correct Oracle Database 11gR2 release, download the software from My Oracle Support (MOS) at https://support.oracle.com.

Consult with your Oracle database administrator for specific details about any prerequisite tasks, as well as specific installation options for your environment. For complete instructions, refer to the Oracle Database documentation at https://docs.oracle.com/en/database/database.html.

1.4.3 Oracle Database Configuration

The following are general guidelines for configuring Oracle Database. These steps can be performed during or after the installation. Consult with your Oracle database administrator to obtain any additional configuration instructions for your particular environment.

The database must use the AL32UTF8 character set that supports Unicode.

Note

You can select the AL32UTF8 character set if you select Advanced install in the Installation GUI, but not if you select the Typical install option.

If you installed the 12cR2 version of Oracle Database, the AL32UTF8 character set is the default.
The database must have a Spacewalk user. You create this user by using SQL*Plus commands, as described in the steps that follow. You can use any name that you choose for the Spacewalk user.

For example, you could create a user named spacewalk for Oracle Database 11gR2. For Oracle Database 12c, if the database is a pluggable database, you might create a user named c##spacewalk. Note that if the database is not a pluggable database, the c## prefix does not need to be part of the user name.
If several Spacewalk servers will share the same database server, you must create a separate Spacewalk user for each server. For example, if you intend to set up two Spacewalk servers that share the same database, you could create two users for Oracle Database 11gR2 with the following names: spacewalk and spacewalk2. For Oracle Database 12c, you could create the c##spacewalk and c##spacewalk2 users.
The Spacewalk user must have the CONNECT and RESOURCE roles.
The Spacewalk user must have the following system privileges:
- ALTER SESSION
- CREATE SYNONYM
- CREATE TABLE
- CREATE TRIGGER
- CREATE VIEW
- UNLIMITED TABLESPACE

Creating a Spacewalk User

Create a Spacewalk user as follows:

Log in to the system as a database administrator (typically, SYS or SYSDBA) on the database server.
```
$ sqlplus / as SYSDBA
```

Set up the Spacewalk user by running the following SQL*Plus commands:

SQL> create user sw_user identified by sw_passwd;
SQL> grant connect,resource to sw_user;
SQL> grant alter session, create synonym, create table, create trigger, create view to sw_user; 
SQL> grant unlimited tablespace to sw_user;

where sw_user and sw_passwd are the user name and password that you will use to administer Spacewalk.

Repeat these steps for each Spacewalk user that you need to set up.

1.5 Installing a Spacewalk Server

Before you install the Spacewalk server software, you must do the following:

Install the Oracle Database and ensure that it is up and running.

For specific instructions on installing and configuring Oracle Database, consult with your Oracle database administrator. See also the product documentation at https://docs.oracle.com/en/database/database.html.
Meet all of the requirements and perform any of the prerequisite tasks that are described in this document, as well as those that are specified in the product documentation.

In particular, make sure you have met the following networking requirements:

Configured a FQDN for the Spacewalk server, as described in Section 1.3, “Networking Requirements for a Spacewalk Server”. The /etc/hosts file should have an FQDN entry for the Spacewalk server.

Caution

The Spacewalk server and clients must be able to resolve the Spacewalk server's FQDN for both forward and reverse lookups in DNS. If these conditions are not met, neither certificate validation nor PXE booting work. In addition, clients cannot register with the Spacewalk server. In particular, a lack of reverse DNS lookup on the Spacewalk server or the clients causes Inter-Server Synchronization (ISS) to fail.

Follow these steps to install the Spacewalk server software:

Install Oracle Instant Client release 11.2.0.4 or later.
1. Download the following Instant Client packages. You can find out more about the Instant Client from:
  
  https://www.oracle.com/database/technologies/instant-client.html
  - Instant Client Package (Basic)
  - Instant Client Package (SQL*Plus)
  Note
  
  Do not download the packages for release 12.1 or later, as these releases are not supported.
2. Install the Instant Client packages.
```
# rpm -ihv oracle-instantclient11.2-basic-11.2.0.4.0-1.x86_64.rpm \
oracle-instantclient11.2-sqlplus-11.2.0.4.0-1.x86_64.rpm
```
3. Add the library path to ldconfig.
```
# echo /usr/lib/oracle/11.2/client64/lib > /etc/ld.so.conf.d/oracle-instantclient11.2.conf 
# ldconfig
```
Caution

The Spacewalk server configuration fails if the Instant Client is missing. Oracle recommends that you install the latest 11.2.0.4 release of the Instant Client.
Ensure that the jta package is not installed and prevent it from being installed when you install Spacewalk.

Check whether the jta package is installed as followed:
```
# yum list installed | grep jta
```
To remove the jta package:
```
# yum remove jta
```
To prevent the jta package from being installed later, do one of the following:
- Disable the Oracle Linux 6 or Oracle Linux 7 addons channels ([ol6_addons] or [ol7_addons]).
- Add the jta package to the exclude directive in the /etc/yum.conf file as follows:
```
exclude=jta*
```

Configure the system firewall.

For Oracle Linux 6, you would configure the system firewall as follows:

# iptables -I INPUT -p udp -m udp --dport 69 -j ACCEPT
# iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
# iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
# iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 5222 -j ACCEPT
# iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 5269 -j ACCEPT
# iptables -I OUTPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
# iptables -I OUTPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
# service iptables save

For Oracle Linux 7, you would configure the system firewall as follows:

# firewall-cmd --permanent --add-port=69/udp
# firewall-cmd --permanent --add-port=80/tcp
# firewall-cmd --permanent --add-port=443/tcp
# firewall-cmd --permanent --add-port=5222/tcp
# firewall-cmd --permanent --add-port=5269/tcp
# firewall-cmd --reload

Enable access to the repositories that contain the Spacewalk Server and dependent packages on the Oracle Linux yum server at https://yum.oracle.com.

For Oracle Linux 6, do the following:
1. Ensure that your system is up to date and that you have transitioned to use the modular yum repository configuration by installing the oraclelinux-release-el6 package and running the /usr/bin/ol_yum_configure.sh script.
```
# yum install oraclelinux-release-el6
# /usr/bin/ol_yum_configure.sh
```
2. Install the oracle-spacewalk-server-release-el6 release package to install appropriate yum repository configuration.
```
# yum install oracle-spacewalk-server-release-el6
```
3. Disable the disable ol6_spacewalk27_client and ol6_spacewalk27_server repositories:
```
# yum-config-manager --disable ol6_spacewalk27_server ol6_spacewalk27_client
```
4. Enable the ol6_spacewalk26_server and ol6_spacewalk26_client repositories in the repository configuration file:
```
# yum-config-manager --enable ol6_spacewalk26_server ol6_spacewalk26_client
```
For Oracle Linux 7, do the following:
1. Install the oraclelinux-release-el7 package and run the /usr/bin/ol_yum_configure.sh script:
```
# yum install oraclelinux-release-el7
# /usr/bin/ol_yum_configure.sh
```
2. Install the oracle-spacewalk-server-release-el7 release package to install appropriate yum repository configuration:
```
# yum install oracle-spacewalk-server-release-el7
```
3. Disable the disable ol7_spacewalk27_server and ol7_spacewalk27_client repositories:
```
# yum-config-manager --disable ol7_spacewalk27_server ol7_spacewalk27_client
```
4. Enable the ol7_spacewalk26_server and ol7_spacewalk26_client repositories in the repository configuration file.
```
# yum-config-manager --enable ol7_spacewalk26_server ol7_spacewalk26_client
```
5. Enable the ol7_optional_latest repository, which is included in the oraclelinux-release-el7 package:
```
# yum-config-manager --enable ol7_optional_latest
```
Install the Spacewalk Server packages that are configured to use Oracle Database.
```
# yum install spacewalk-oracle
```
Note

As part of the Spacewalk installation process, all of the Oracle Linux yum server configuration, as well as ULN configuration, is disabled because Spacewalk handles this configuration going forward.

If you need to re-enable yum repository configuration after an installation, but before you have configured any repositories in Spacewalk, you can temporarily rename any affected yum repository configuration files to enable them again, for example:
```
# mv /etc/yum.repos.d/oracle-linux-ol7.repo.rpmsave /etc/yum.repos.d/oracle-linux-ol7.repo
```
Remember to disable the yum repository configuration files again after you have configured repositories within Spacewalk.
(Optional) Install the spacecmd and spacewalk-utils packages if you want to use commands such as spacecmd, spacewalk-common-channels, spacewalk-hostname-rename, and spacewalk-sync-setup.
```
# yum install spacecmd spacewalk-utils
```
spacecmd

Enables you to administer Spacewalk from the command line. You can manage activation keys, configuration channels, kickstarts, software channels, systems, and users.

spacewalk-common-channels

Enables you to configure the software channels, public yum repositories, GNU Privacy Guard (GPG) keys, and activation keys for Oracle Linux from the command line.

spacewalk-hostname-rename

Enables you to regenerate the SSL certificate if you change the system's host name.

spacewalk-sync-setup

Enables you configure a primary-worker (master-slave) relationship between two Spacewalk servers that you want to use in ISS configuration. See Chapter 3, Configuring Inter-Server Synchronization for Spacewalk Servers.

Note

You can safely ignore any SELinux restorecon messages that are displayed when the packages are installed.

Alternatively, you can install the additional packages at a later time if you register the Spacewalk server as a client of itself and then subscribe it to the appropriate Spacewalk Server 2.6 channel.

Configure Spacewalk to use the Oracle Database by running the spacewalk-setup --external-oracle command.

The --external-oracle option is used because all Oracle databases are external to Spacewalk's setup, regardless of whether the database is running on the same system.

The following example shows how to run the command to initiate an interactive session where you provide the information that is required to complete the Spacewalk setup.

When configuring Spacewalk, keep the following key points in mind:

The sw_user and sw_passwd are the Spacewalk user name and password that you specified when you configured the Oracle Database, per Section 1.4.3, “Oracle Database Configuration”.
The value that is expected for the database service name (SID) is the global database name and not the value of ORACLE_SID.
The Database hostname [localhost]? prompt is bypassed if the setup tool detects that the Oracle Database and Spacewalk are co-located on the same host. You are only prompted for this information during the setup if the Oracle Database is on a host other than the host on which Spacewalk is installed.
The value that you specify for the Organization Unit must be the same as the FQDN of the server in DNS. Also, this value must match the system's host name.

# spacewalk-setup --external-oracle
* Setting up SELinux..
* Setting up Oracle environment.
* Setting up database.
** Database: Setting up database connection for Oracle backend.
Global Database Name or SID (requires tnsnames.ora)? company.mydom.com
Database hostname [localhost]? spacewalk-db.mydom.com
Username? sw_user
Password? sw_passwd 
Database: Testing database connection. 
** Database: Populating database. 
*** Progress: ############################################################ 
* Configuring tomcat.
* 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? my.email@mydom.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]? y 
** /etc/httpd/conf.d/ssl.conf has been backed up to ssl.conf-swsave 
* Configuring jabberd.
* Creating SSL certificates.
CA certificate password? cert_passwd
Re-enter CA certificate password? cert_passwd
Organization? Company Demo
Organization Unit [swksvr.mydom.com]? swksvr.mydom.com
Email Address [your.email@domain.com]? my.email@mydom.com
City? Redwood Shores
State? 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..
Cobbler requires tftp and xinetd services be turned on for PXE provisioning functionality.
Enable these services [Y]? y
* Restarting services. 
Installation complete. 
Visit https://swksvr.mydom.com to create the Spacewalk administrator account.

Verify that the Spacewalk services are running.

# /usr/sbin/spacewalk-service status
router (pid 5097) is running...
sm (pid 5105) is running...
c2s (pid 5113) is running...
s2s (pid 5121) is running...
tomcat6 (pid 5193) is running...                           [  OK  ]
httpd (pid  5303) is running...
osa-dispatcher (pid  5331) is running...
rhn-search is running (5353).
cobblerd (pid 5392) is running...
RHN Taskomatic is running (5419).

The process IDs on your system are likely to be different from those shown in this example.

Note the Spacewalk server URL that is mentioned in the output.

You will need the Spacewalk server URL to create the main Spacewalk administrator account and an initial organization, as described in Section 1.6.2, “Configuring a Spacewalk Administrator and an Initial Organization”.

After completing the Spacewalk server installation, perform any required or optional post-installation tasks. For instructions, see Section 1.6, “Configuring a Newly Installed Spacewalk Server”,

1.6 Configuring a Newly Installed Spacewalk Server

After installing a Spacewalk server, perform the following tasks. Some tasks, although recommended, are optional.

1.6.1 Replacing a Self-Signed SSL Certificate

When you install a Spacewalk server or Spacewalk proxy, you can create a self-signed SSL certificate to use with Spacewalk clients. The following procedure describes how to replace self-signed certificates or expired CA-signed certificates with certificates that have been signed by a Certificate Authority (CA).

You can use certificates for individual Spacewalk servers or Spacewalk proxies, or wildcard certificates for all Spacewalk servers or Spacewalk proxies in the domains that the wildcard certificates cover.

Replace the existing certificate on a Spacewalk server or Spacewalk proxy as follows:

Create a backup of the system's existing SSL configuration.

# tar -cvf SSLconfig.tar \ 
  /etc/httpd/conf/ssl.* \
  /etc/pki/spacewalk/jabberd/server.pem \
  /root/ssl-build \
  /var/www/html/pub

Obtain a server certificate by using one of the following methods:
- Obtain a server certificate from a CA and install this certificate in the SSL build hierarchy on the system as follows:
  1. Send the Certificate Signing Request (CSR) file /root/ssl-build/swksvr/server.csr to the CA.
    
    Note
    
    swksvr is the name of the Spacewalk server or Spacewalk proxy that you used to set up the existing SSL configuration, with the domain name removed.
    
    After validating your request, the CA returns a signed server certificate file.
  2. Create a backup of the signed server certificate file.
  3. If necessary, convert the certificate to Privacy Enhanced Mail (PEM) format.
    
    A PEM-formatted certificate file is a text file that contains a Base64 encoded certificate section between the BEGIN/END markers, as shown in the following output:
    
    -----BEGIN CERTIFICATE----- MIIF7DCCBNSgAwIBAgIQbsx6pacDIAm4zrz06VLUkTANBgkqhkiG9w0BAQUFADCB ... Rs/iGAZeqa6ogZpHFt4MKGwlJ7net4RYxh84HqTEy2Y= -----END CERTIFICATE-----
    
    A PEM-formatted certificate file usually has a file extension of .crt or .pem. However, binary DER-formatted certificate files also sometimes have a .crt extension.
    
    A DER-formatted certificate file is a binary file that usually has a file extension of .cer or .der, but can also have the extension .cert or .crt.
    
    Test whether a certificate file is in DER format by typing the following command:
    
    # openssl x509 -inform der -text -in certificate_file
  4. If a certificate file is in DER format, convert the file to a PEM-formatted certificate file by typing the following command:
    
    # openssl x509 -inform der -in server.cer -out server.pem
  5. If a PEM-formatted certificate file was not generated on a UNIX or a Linux system, the file might contain ^M carriage return characters. Use either of the following commands to remove these characters:
    
    # sed -i -e 's/\r//' server.pem
    
    # dos2unix server.pem
    
    Note that the dos2unix command is available in the dos2unix package.
  6. Copy the PEM-formatted server certificate file to /root/ssl-build/swksvr/server.crt.
    
    # cp server.pem /root/ssl-build/swksvr/server.crt
- Obtain a server certificate using an external tool as follows:
  1. Obtain both the private key and the signed certificate from the external tool in PEM format, then copy both to /root/ssl-build/swksvr.
  2. If the private key has an existing password, remove it, then replace the key as follows:
    
    # openssl rsa -in keyfilewithpasswd.key -out /root/ssl-build/swksvr/server.key
    
    This step ensures that the Spacewalk services can start unattended.
Add the CA public certificate to the /root/ssl-build directory as the RHN-ORG-TRUSTED-SSL-CERT file by using one of the following methods:
- If available, obtain the CA chain certificate from the CA that issued the server certificate. Copy this certificate file to /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT:
```
# cp ca_chain.pem /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT
```
- If the CA chain certificate is not available from the issuing CA, create the CA chain certificate as follows:
  1. Obtain the root CA public certificate and the intermediate CA public certificates from the issuing CA.
  2. Concatenate the chain of CA public certificate files starting with the public certificate file of the CA that issued your server certificate down to the public certificate file of the root CA to /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT:
    
    # cat intermediate_ca.pem root_ca.pem > /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT
    
    where intermediate_ca.pem is the public certificate file of the intermediate CA that signed your server certificate, and root_ca.pem is the public certificate file of the root CA that signed the intermediate certificate.
    
    Caution
    
    The order in which the public certificates in a CA chain certificate file appear is critical. The CA chain certificate does not work if its component certificates are not in the correct order.
- If a root CA signed your server certificate directly (which is unlikely nowadays), only the public certificate of the root CA is required. Copy the root CA public certificate file to /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT:
```
# cp root_ca.pem /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT
```
Validate the server certificate against the CA public certificate by typing the following command:
```
# openssl verify -CAfile /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT \
  /root/ssl-build/swksvr/server.crt
/root/ssl-build/swksvr/server.crt: OK
```
If the command returns an error, verify that you correctly created RHN-ORG-TRUSTED-SSL-CERT and also verify that the date and time on the server are configured correctly.
Store the CA public certificate in the Spacewalk database so that it is available for use in provisioning client systems:
```
# rhn-ssl-dbstore -v --ca-cert=/root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT
Public CA SSL certificate:  /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT
```
If the command returns an error, run the command again, specifying a higher level of debugging, such as -vvv, to gather more information about the problem.

Generate and install the web server SSL package as follows:

Generate the web server SSL package.

# rhn-ssl-tool --gen-server --rpm-only --dir /root/ssl-build

...working...

Generating web server's SSL key pair/set RPM:
    /root/ssl-build/swksvr/rhn-org-httpd-ssl-key-pair-swksvr-1.0-rev.src.rpm
    /root/ssl-build/swksvr/rhn-org-httpd-ssl-key-pair-swksvr-1.0-rev.noarch.rpm

The most current Spacewalk Proxy Server installation process against RHN hosted
requires the upload of an SSL tar archive that contains the CA SSL public
certificate and the web server's key set.

Generating the web server's SSL key set and CA SSL public certificate archive:
    /root/ssl-build/swksvr/rhn-org-httpd-ssl-archive-swksvr-1.0-rev.tar

Deploy the server's SSL key pair/set RPM:
    (NOTE: the Red Hat Satellite or Proxy installers may do this step for you.)
    The "noarch" RPM needs to be deployed to the machine working as a
    web server, or Red Hat Satellite, or Spacewalk Proxy.
    Presumably 'swksvr.mydom.com'.

Run the rpm command to list the files that the packages install.

# rpm -qlp /root/ssl-build/swksvr/rhn-org-httpd-ssl-key-pair-swksvr-1.0-rev.src.rpm
rhn-org-httpd-ssl-key-pair-swksvr-1.0.tar.gz
rhn-org-httpd-ssl-key-pair-swksvr.spec
# rpm -qlp /root/ssl-build/swksvr/rhn-org-httpd-ssl-key-pair-swksvr-1.0-rev.noarch.rpm
/etc/httpd/conf/ssl.crt/server.crt
/etc/httpd/conf/ssl.csr/server.csr
/etc/httpd/conf/ssl.key/server.key
/etc/pki/spacewalk/jabberd/server.pem

Install the web server SSL noarch package.

# rpm -Uhv /root/ssl-build/swksvr/rhn-org-httpd-ssl-key-pair-swksvr-1.0-rev.noarch.rpm
Preparing...                ########################################### [100%]
   1:rhn-org-httpd-ssl-key-p########################################### [100%]

Generate the public CA certificate package and make both the package and the CA public certificate file available to clients.

Generate the public CA certificate package.

# rhn-ssl-tool --gen-ca --dir=/root/ssl-build --rpm-only

...working...
Generating CA public certificate RPM:
    /root/ssl-build/rhn-org-trusted-ssl-cert-1.0-rev.src.rpm
    /root/ssl-build/rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm

Make the public CA certificate publicly available:
    (NOTE: the Red Hat Satellite or Proxy installers may do this step for you.)
    The "noarch" RPM and raw CA certificate can be made publicly accessible
    by copying it to the /var/www/html/pub directory of your Red Hat Satellite or
    Proxy server.

Run the rpm command to list the files that the packages install.

# rpm -qlp /root/ssl-build/rhn-org-trusted-ssl-cert-1.0-rev.src.rpm
rhn-org-trusted-ssl-cert-1.0.tar.gz
rhn-org-trusted-ssl-cert.spec
# rpm -qlp /root/ssl-build/rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm 
/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

If a Spacewalk server or proxy is also configured as a client, install the public CA certificate noarch package on this system.

# rpm -Uhv /root/ssl-build/pub/rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm
Preparing...                ########################################### [100%]
   1:rhn-org-trusted-ssl-cer########################################### [100%]

The public CA certificate is installed as /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT.

Copy the rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm package and CA public certificate file to /var/www/html/pub for access by clients.

# cp /root/ssl-build/rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm /var/www/html/pub
# cp /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT /var/www/html/pub

Note

If you do not copy the updated RHN-ORG-TRUSTED-SSL-CERT to /var/www/html/pub, the osa-dispatcher service fails to start.

Verify that the installed copies of RHN-ORG-TRUSTED-SSL-CERT are identical by comparing their digest values as follows:

# sha1sum /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT \
  /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT \
  /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT
74380a372bfa55d8ab7579bf01502c874b8aae84
                      /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT
74380a372bfa55d8ab7579bf01502c874b8aae84
                      /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
74380a372bfa55d8ab7579bf01502c874b8aae84
                      /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT

The rhn-org-trusted-ssl-cert-1.0-rev.src.rpm package is usually not made available to clients.

On a Spacewalk server, stop the Spacewalk services, clear the jabberd database, then restart Spacewalk.
```
# /usr/sbin/spacewalk-service stop
# rm -Rf /var/lib/jabberd/db/*
# /usr/sbin/spacewalk-service start
```
On a Spacewalk proxy, restart the Spacewalk proxy services.
```
# /usr/sbin/rhn-proxy restart
```

On the remaining Spacewalk clients, download and install the public CA certificate package.

# wget https://swksvr.mydom.com/pub/rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm
--2015-06-05 15:15:44--  https://swksvr.mydom.com/pub/rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm
Resolving swksvr.mydom.com... 192.168.1.3
Connecting to swksvr.mydom.com|192.168.1.3|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4840 (4.7K) [application/x-rpm]
Saving to: “rhn-org-trusted-ssl-cert-1.0-2.noarch.rpm”

100%[======================================>] 4,840       --.-K/s   in 0s      

2015-06-05 15:15:44 (57.5 MB/s) - “rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm” saved [4840/4840]

# rpm -Uhv /root/ssl-build/pub/rhn-org-trusted-ssl-cert-1.0-rev.noarch.rpm
Preparing...                ########################################### [100%]
   1:rhn-org-trusted-ssl-cer########################################### [100%]

Note

If you subsequently replace the server certificate because it is revoked or expired, you do not need to update the public CA certificate on the clients unless you change the CA that signs the server certificate.

1.6.2 Configuring a Spacewalk Administrator and an Initial Organization

After installing a Spacewalk server and connecting to the Oracle Database, you must create the main Spacewalk administrator account and an initial organization. Follow these steps:

Point a browser at the URL that is specified in the Step of 7 of in Section 1.5, “Installing a Spacewalk Server”.

For example, the server that is shown in the following output (swksvr.mydom.com) matches the host name that you provided when you configured the Oracle Database:
```
Installation complete.
Visit https://swksvr.mydom.com to create the Spacewalk administrator account.
```
Because Spacewalk uses a self-signed certificate by default, you will be prompted to trust this certificate the first time you launch the Spacewalk user interface by using a web browser, unless you have replaced the SSL certificate. See Section 1.6.1, “Replacing a Self-Signed SSL Certificate”.
On the Create Organization page (located under Create First User), enter the required values in the appropriate fields.
Accept any of the default values that are provided for you.
If you are prompted to provide additional configuration details, click the link to be taken to a General Configuration page, where you can enter any additionally required values.
Save the changes and then log in to the Spacewalk web interface.

The Overview page for the Spacewalk web interface is displayed

See About the Spacewalk Web Interface in Spacewalk for Oracle® Linux: Client Life Cycle Management Guide for Release 2.6.

1.6.3 Replacing the jabberd/osa Database on Spacewalk Servers or Spacewalk Proxies

You might need to replace the jabberd/osa database on a Spacewalk server or proxy if you encounter any of the following errors:

OSA status shows "offline as of unknown" for client servers.
osa-dispatcher errors in /var/log/mesasges on the Spacewalk server or proxy.
"db: corruption detected! close all jabberd processes and run db_recover" message in /var/log/messages on the Spacewalk server or proxy.

This problem occurs because the default Berkeley database format does not support transactions, and as a result, can become damaged when too many clients attempt to update at the same time. Switching to SQLite provides transactional support for the jabberd database and can handle significantly more downstream clients.

Follow these steps to resolve the problem:

Stop the osa-dispatcher and jabberd services.

If you are running Oracle Linux 7, use the systemctl command:
```
# systemctl stop osa-dispatcher
# systemctl stop jabberd
```
If you are running Oracle Linux 6, use the service command:
```
# service osa-dispatcher stop
# service jabberd stop
```
Edit the /etc/jabberd/sm.xml file and change "<driver>db</driver>" to "<driver>sqlite</driver>".
Edit the /etc/jabberd/c2s.xml file and change "<module>db</module>" to "<module>sqlite</module>".

Create the SQLite database as follows:

# sqlite3 /var/lib/jabberd/db/sqlite.db < /usr/share/jabberd/db-setup.sqlite
# chown jabber:jabber /var/lib/jabberd/db/sqlite.db

Start the jabberd and osa-dispatcher services again.

For Oracle Linux 7, type the following commands:
```
# systemctl start jabberd
# systemctl start osa-dispatcher
```
For Oracle Linux 6, type the following commands:
```
# service jabberd start
# service osa-dispatcher start
```

Check /var/log/messages to ensure that SQLite is being used.

# cat /var/log/messages | grep sqlite
   Feb 24 12:46:18 sw24 jabberd/sm[15196]: loading 'sqlite' storage module
   Feb 24 12:46:18 sw24 jabberd/sm[15196]: initialised storage driver 'sqlite'
   Feb 24 12:46:18 sw24 c2s: Fri Feb 24 12:46:18 2017 [info] loading 'sqlite' authreg module
   Feb 24 12:46:18 sw24 c2s: Fri Feb 24 12:46:18 2017 [notice] initialized auth module 'sqlite'
   Feb 24 12:46:18 sw24 jabberd/c2s[15199]: [sirius.lot209.com] configured; realm=, authreg=sqlite, registration enabled, using PEM:/etc/pki/spacewalk/jabberd/server.pem

Reset and restart the osad service on the client servers.

If you previously registered client servers and installed the osad service on those servers, you will need to remove the osad-auth.conf file and then restart the osad service on these systems after the database has been switched.

For Oracle Linux 7, type the following commands:
```
# systemctl stop osad
# rm -f /etc/sysconfig/rhn/osad-auth.conf
# systemctl start osad
```
For Oracle Linux 6, type the following commands:
```
# service osad stop
# rm -f /etc/sysconfig/rhn/osad-auth.conf
# service osad start
```
Running these commands triggers the osad client on each server to re-authenticate to jabberd.

1.6.4 Configuring a Web Proxy for a Spacewalk Server

If the Spacewalk server needs to connect though a web proxy, you can configure the web proxy by using one of the following methods after you have installed Spacewalk:

Edit the /etc/rhn/rhn.conf file and provide the web proxy configuration settings for the server.satellite.http_proxy, server.satellite.http_proxy_username, and server.satellite.http_proxy_password parameters, as shown in the following example:
```
server.satellite.http_proxy = webproxy.mydom.com:80
server.satellite.http_proxy_username = another
server.satellite.http_proxy_password = examplepass
```
In the Spacewalk web interface, do the following:
1. Select the Admin tab, then Spacewalk Configuration, and then General.
2. Provide the web proxy configuration settings in the fields HTTP proxy, HTTP proxy username, HTTP proxy password, and Confirm HTTP proxy password, and then click Update.

1.7 Upgrading a Spacewalk Server

Upgrade a Spacewalk 2.2 or 2.4 server to Spacewalk 2.6 as follows:

Back up the all of the Spacewalk configuration files in the following directories:
- /etc/jabberd
- /etc/rhn
- /etc/sysconfig/rhn
- Server SSL build directory, typically /root/ssl-build
For example, you could use the tar command to create a backup as follows:
```
# tar -cvf preSWupgrade.tar /etc/jabberd /etc/rhn /etc/sysconfig/rhn /root/ssl-build
```
Back up the Spacewalk database.

For more information about using the Recovery Manager (RMAN) to create a backup,refer to the following documents:
- Getting Started with RMAN (Oracle Database 11gR2)
- Getting Started with RMAN (Oracle Database 12c)
Disable access to the Spacewalk 2.2 or 2.4 Server packages and enable access to the Spacewalk 2.6 Server packages.
- If the Spacewalk server is registered as a client of itself, do the following:
  1. Create a Spacewalk Server 2.6 channel as a child of the Oracle Linux 6 base channel.
  2. Create a Spacewalk Server 2.6 repository that accesses the Spacewalk Server 2.6 channel on the Oracle Linux yum server (https://yum.oracle.com/repo/OracleLinux/OL6/spacewalk26/server/x86_64/), using the same GPG settings as for Oracle Linux 6.
  3. Associate the Spacewalk Server 2.6 repository with the Spacewalk server 2.6 channel and synchronize the repository's packages from the Oracle Linux yum server.
  4. Change the channel subscription of the Spacewalk server in Spacewalk from the previous version to the Spacewalk Server 2.6 channel.
- If the Spacewalk server is configured to obtain Spacewalk Server 2.2 or 2.4 packages from the Oracle Linux yum server, do the following:
  1. Disable the Spacewalk Server 2.2 or 2.4 repository in the Oracle Linux yum server repository configuration file. Or, delete your Spacewalk Server 2.2 or 2.4 .repo file.
  2. Ensure that your system is up to date and that you have transitioned to use the modular yum repository configuration by installing the oraclelinux-release-el6 or oraclelinux-release-el7 package and running the /usr/bin/ol_yum_configure.sh script. For example, on Oracle Linux 6, do:
    
    # yum install oraclelinux-release-el6 # /usr/bin/ol_yum_configure.sh
  3. Install the oracle-spacewalk-server-release-el6 or release oracle-spacewalk-server-release-el7 package to install appropriate yum repository configuration. For example, on Oracle Linux 6, do:
    
    # yum install oracle-spacewalk-server-release-el6
  4. Disable the ol6_spacewalk27_server and the ol6_spacewalk27_client (or ol7_spacewalk27_server and ol7_spacewalk27_client) repositories in the repository configuration file. For example, for Oracle Linux 6, do:
    
    # yum-config-manager --disable ol6_spacewalk27_client # yum-config-manager --disable ol6_spacewalk27_client
  5. Enable the ol6_spacewalk26_server and the ol6_spacewalk26_client (or ol7_spacewalk26_server and ol7_spacewalk26_client) repositories in the repository configuration file. For example, for Oracle Linux 6, do:
    
    # yum-config-manager --enable ol6_spacewalk26_client # yum-config-manager --enable ol6_spacewalk26_client
Lock the versions of any third-party libraries by running the following commands:
```
# yum install yum-versionlock
# yum versionlock cglib
```
This step is necessary because Spacewalk requires a specific version of cglib, which must be locked prior to upgrading.
Upgrade the Spacewalk packages.
```
# yum upgrade
```

Stop the Spacewalk services.

# /usr/sbin/spacewalk-service stop
Shutting down spacewalk services...
Stopping RHN Taskomatic...
Stopped RHN Taskomatic.
Stopping cobbler daemon:                                   [  OK  ]
Stopping rhn-search...
Stopped rhn-search.
Shutting down osa-dispatcher:                              [  OK  ]
Stopping httpd:                                            [  OK  ]
Stopping tomcat6:                                          [  OK  ]
Terminating jabberd processes ...
Stopping s2s:                                              [  OK  ]
Stopping c2s:                                              [  OK  ]
Stopping sm:                                               [  OK  ]
Stopping router:                                           [  OK  ]
Done.

You can safely ignore any SELinux restorecon messages that are displayed when the packages are installed.

(Optional) Install the rpmconf package and then run the rpmconf command to copy any customizations you want to preserve to the upgraded configuration files.
```
# yum install rpmconf
# rpmconf -a
```
Note

Accept the default option, keep your currently-installed version, for each configuration file unless directed by Oracle support to do otherwise.
Upgrade the Spacewalk database schema by typing the following command on the Spacewalk server:
```
# /usr/bin/spacewalk-schema-upgrade
```
The output of the spacewalk-schema-upgrade command confirms whether or not the schema upgrade was successful.

In the event of a failure, do the following:
- Check the log files in the /var/log/spacewalk/schema-upgrade directory to determine the cause.
- Restore the database from backup.
- Fix the cause of the problem, for example, by extending the tablespaces if there is insufficient space.
- Upgrade the database schema.
Upgrade the Spacewalk configuration for the Oracle Database.
```
# spacewalk-setup --external-oracle --upgrade
```
Note

This step resets the jabberd-dispatcher/osa-dispatcher configuration back to the default. If you have switched to using SQLite, you will need to manually edit the configuration.

Restart the Spacewalk services.

# /usr/sbin/spacewalk-service start
Starting spacewalk services...
Initializing jabberd processes ...
Starting router:                                           [  OK  ]
Starting sm:                                               [  OK  ]
Starting c2s:                                              [  OK  ]
Starting s2s:                                              [  OK  ]
Starting tomcat6:                                          [  OK  ]
Waiting for tomcat to be ready ...
Starting httpd:                                            [  OK  ]
Starting osa-dispatcher:                                   [  OK  ]
Starting rhn-search...
Starting cobbler daemon:                                   [  OK  ]
Starting RHN Taskomatic...
Done.

Perform any necessary post-installation tasks.

Review the information in Section 1.6, “Configuring a Newly Installed Spacewalk Server”.

1.8 Troubleshooting Spacewalk Server Problems

The following information describes how to diagnose and fix problems that you might encounter on a Spacewalk server. For information about other known issues and possible workarounds, see Spacewalk for Oracle® Linux: Release Notes for Release 2.6.

Use the /usr/sbin/spacewalk-service status command to verify whether any Spacewalk services are not running correctly. If a service does not start correctly, the problem is usually caused by incorrect configuration information being provided during installation.

Check the following log files for errors:

/var/log/httpd/*: Are httpd service log files.
/var/log/rhn_satellite_install.log: Is the installation log file.
/var/log/rhn/reposync/*: Are the repository synchronization log files.
/var/log/rhn/rhn_server_satellite.log: Is the synchronization log file.
/var/log/rhn/rhn_server_xmlrpc.log: Is the XML-RPC transaction log file.
/var/log/rhn/rhn_taskomatic_daemon.log: Is the Red Hat Network (RHN) Task Engine (Taskomatic) log messages.
/var/log/tomcat6: Is the Tomcat log messages for Oracle Linux 6.
/var/log/tomcat: Is the Tomcat log messages for Oracle Linux 7.
/var/log/yum.log: Is the yum log file.

1.8.1 Managing Spacewalk Logging

Spacewalk generates large numbers of log messages, particularly under the /var/log/httpd directory. To avoid running out of disk space, you might need to adjust the logrotate settings to implement more active rotation, compression, and archival of log files.

For more information, see Oracle® Linux 6: Administrator's Guide and Oracle® Linux 7: Administrator's Guide.

1.8.2 osa-dispatcher Reports a Certificate Verification Failure

If the osa-dispatcher service does not start, an error similar to the following might be displayed if you attempt to start the service manually with the service osa-dispatcher start command on Oracle Linux 6 or the systemctl start osa-dispatcher command on Oracle Linux 7:

Starting osa-dispatcher: Spacewalk 10611 2015/05/26 17:11:22 +01:00: ('Traceback caught:',)
Spacewalk 10611 2015/05/26 17:11:22 +01:00: ('Traceback (most recent call last):\n  
    File "/usr/share/rhn/osad/jabber_lib.py", line 631, in connect\n    
    ssl.do_handshake()\nError: [(\'SSL routines\', \'SSL3_GET_SERVER_CERTIFICATE\', 
    \'certificate verify failed\')]\n',)
                                                          [FAILED]

This error usually indicates that the system's host name does not match its FQDN in DNS, or that you specified an incorrect FQDN for name of the Organization Unit when you installed Spacewalk.

To regenerate the SSL certificate, run the spacewalk-hostname-rename command, which is available in the spacewalk-utils package.
If the host name has changed, the spacewalk-hostname-rename command prompts you to type the same certificate password that you used when you created the existing certificate. To verify that you know the correct password before running spacewalk-hostname-rename, run the following command, which returns the base64-encoded private key if the password is correct or the unable to load Private Key error otherwise:
```
# openssl rsa -in /root/ssl-build/RHN-ORG-PRIVATE-SSL-KEY 
Enter pass phrase for /root/ssl-build/RHN-ORG-PRIVATE-SSL-KEY: cert_passwd
writing RSA key
-----BEGIN RSA PRIVATE KEY-----
MIIEowIBAAKCAQEAvYQ/Enqo+T3WByuXiOQCpIh7eBFdqWt/e+cm3pfvGYBqi/1g
...
+rEs1ZK2mCoofnPzg2o097oPj5v4IHYh8Bmlssbk9BHvQ2ZQckSA
-----END RSA PRIVATE KEY-----
```
Run the spacewalk-hostname-rename command, specifying the IP address and FQDN of the server as arguments to the command, as shown in the following example:
```
# /usr/sbin/spacewalk-hostname-rename IP_address --ssl-orgunit=FQDN
```

After regenerating the SSL certificate, stop the jabberd and osa-dispatcher services, clear the jabberd database, and restart the jabberd and osa-dispatcher services.

For Oracle Linux 6, type the following commands:

# service jabberd stop
# service osa-dispatcher stop
# rm -Rf /var/lib/jabberd/db/*
# service jabberd start
# service osa-dispatcher start

For Oracle Linux 7, type the following commands:

# systemctl stop jabberd
# systemctl stop osa-dispatcher
# rm -Rf /var/lib/jabberd/db/*
# systemctl start jabberd
# systemctl start osa-dispatcher

On every client that is registered with the server, verify that the value of serverURL in /etc/sysconfig/rhn/up2date is configured with the correct server host name or IP value, for example:
```
serverURL=https://swksvr.mydom.com/XMLRPC
```

1.8.3 osa-dispatcher Reports an Invalid Password

If the osa-dispatcher service starts correctly, but later stops unexpectedly, you might see a log error similar to the following:

Spacewalk 2316 2015/06/05 20:38:47 +01:00: ('Invalid password',)

This error can occur if the jabberd database contains invalid entries.

To clear the error, stop the jabberd and osa-dispatcher services, clear the jabberd database, then restart the jabberd and osa-dispatcher services.

For Oracle Linux 6, type the following commands:

# service jabberd stop
# service osa-dispatcher stop
# rm -Rf /var/lib/jabberd/db/*
# service jabberd start
# service osa-dispatcher start

For Oracle Linux 7, type the following commands:

# systemctl stop jabberd
# systemctl stop osa-dispatcher
# rm -Rf /var/lib/jabberd/db/*
# systemctl start jabberd
# systemctl start osa-dispatcher

Note

To avoid problems with OSA, you should clear the jabberd database at regular intervals.

To avoid database corruption, follow the instructions in Section 1.6.3, “Replacing the jabberd/osa Database on Spacewalk Servers or Spacewalk Proxies”.

1.8.4 Tomcat Does Not Start

If the Tomcat service does not start, most likely the jta package was installed instead of the geronimo-jta-1.1-api package.

To resolve the issue, remove the jta package and install the geronimo-jta-1.1-api package.

Restart the Spacewalk services.

# /usr/sbin/spacewalk-service restart

1.8.5 Tomcat Runs Out of Memory

If you see messages such as OutOfMemoryError: Java heap space in the Tomcat logs, increase the maximum amount of memory that is available to the Tomcat service for its heap as follows:

Edit the /etc/sysconfig/tomcat6 (Oracle Linux 6) or /etc/sysconfig/tomcat (Oracle Linux 7) file and increase the argument to -Xmx in the JAVA_OPTS setting. For example, -Xmx1024m increases the maximum size of the heap to 1 GB.
Restart the Spacewalk services.
```
# /usr/sbin/spacewalk-service restart
```