1.4 Known Issues

1.4.1 Spacewalk Fails to Install Due to slf4j Package
1.4.2 Tomcat Fails to Start After Spacewalk Configuration
1.4.3 Spacewalk Client Fails to Install on Oracle Linux 5
1.4.4 Oracle Linux 5 Does Not Register with Spacewalk after Kickstart Installation
1.4.5 PXE Booting Fails Due to Incorrect Host Name Configuration
1.4.6 Memory Issues With Large Repositories or Data Sets
1.4.7 Client Registration Issues

1.4.1 Spacewalk Fails to Install Due to slf4j Package

In some circumstances, the Spacewalk installation can fail if the 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.

1.4.2 Tomcat Fails to Start After Spacewalk Configuration

If the Tomcat service (tomcat6) fails to start after the initial configuration of Spacewalk, check that the geronimo‑jta‑1.1‑api package is installed. If you installed Oracle Linux using a software set other than Minimal or Basic Server, the jta package might be installed on the system and the presence of this package prevents the geronimo‑jta‑1.1‑api package from being installed. The geronimo‑jta‑1.1‑api package is required to ensure that all the Spacewalk services start correctly. If the geronimo‑jta‑1.1‑api package is missing from your system, remove the jta package, install the geronimo‑jta‑1.1‑api package, and then shutdown and reboot the system.

1.4.3 Spacewalk Client Fails to Install on Oracle Linux 5

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 and up2date‑gnome packages manually using the rpm -e --nodeps command.

1.4.4 Oracle Linux 5 Does Not Register with Spacewalk after Kickstart Installation

If Oracle Linux 5 does not register with Spacewalk after Kickstart installation, add -up2date and -up2date-gnome to the Kickstart profile on the Software, Package Group screen.

1.4.5 PXE Booting Fails Due to Incorrect Host Name Configuration

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:

  1. Edit the /etc/cobbler/settings file and change all instances of incorrect host names, such as localhost.localdomain.

  2. Restart Spacewalk by running spacewalk-service restart.

  3. Resynchronise Cobbler by running cobbler sync.

1.4.6 Memory Issues With Large Repositories or Data Sets

When building repository metadata, Spacewalk can fail with Out of Memory issues. This is caused by the default Java memory settings for the Taskomatic daemon. The solution is to increase the JVM memory settings in the configuration file for the Taskomatic daemon /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf.

Similar memory issues can also occur in the web interface if you have big data sets, such as a large number of servers or packages. The solution is to increase the Tomcat memory limits in the /etc/sysconfig/tomcat6 file. Edit the JAVA_OPTS environment variable, and increase the -Xms (the start or initial amount of memory) and -Xmx (the maximum amount of memory) parameters.

1.4.7 Client Registration Issues

During installation, Spacewalk generates a CA certificate. This certificate is used in the client registration process. If a Spacewalk server does not have a valid fully-qualified domain name (FQDN), Spacewalk does not generate a valid CA certificate. Spacewalk does not consider .local and .localdomain to be valid domain names.