2 Known Issues in Oracle Linux Manager
The following known issues pertain to Oracle Linux Manager.
Synchronizing From ULN Channels Might Generate Error 403 Message
When you run the spacewalk-repo-sync command
on a repository that synchronizes from a ULN channel, that is, a
channel that has the uln:///
prefix, a mirror
related error is displayed.
For example, when synchronizing from
uln:///ol7_x86_64_addons
, the command might
include the following message in the output:
... Could not retrieve mirrorlist https://linux-update.oracle.com/XMLRPC/GET-REQ/ol7_x86_64_addons error was 14:HTTP Error 403 - Forbidden
You can safely disregard this message. (Bug ID 32165904)
Synchronizing Using --latest
Bypasses Required
Packages
The mechanism that underlies --latest
, an
option for synchronizing channels, is not module-aware. If you
use this option when synchronizing module-enabled channels such
as ol8_Appstream
, required packages might be
bypassed. Therefore, when synchronizing modularized channels,
DO NOT use the option
--latest
, either in the web UI or on the
command line.
64-bit Arm (aarch64) Platform Not Supported
This current release of Oracle Linux Manager does not support systems using the 64-bit Arm (aarch64) architecture. (Bug ID 31053096)
Errors Reported During Proxy Server Installation
During an installation of a proxy server, the log might report the following:
... 2020/06/16 11:19:27 -04:00 1655 172.16.0.210: config_mgmt/rhn_config_management.management_put_file 2020/06/16 11:19:27 -04:00 1655 172.16.0.210: server/apacheRequest.call_function('ERROR', 'Unhandled exception', AttributeError("'list' object has no attribute 'write'",))
You can safely ignore these messages. (Bug ID 31499690)
Snapshot Rollback Feature Requires Remote Management Client To Be Installed and Enabled
To successfully roll back a target system to a previous snapshot
by using Oracle Linux Manager, ensure that the target server must have the
Oracle Linux Manager Remote Management client installed with at least the
deploy files
option enabled. However, Oracle
recommends enabling all remote configuration options.
For information about administering Oracle Linux Manager Remote Management client, see Oracle Linux Manager: Client Life Cycle Management Guide for Release 2.10 .
Issues That Require You to Replace the jabberd Database
You might need to replace the jabberd
database on an Oracle Linux Manager 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/messages
on Oracle Linux Manager server or proxy. -
"db: corruption detected! close all jabberd processes and run db_recover" message in
/var/log/messages
on Oracle Linux Manager server or proxy.
These issues typically occur if you have upgraded from an earlier Spacewalk version but did not change the default database to SQLite that is now used by later versions.
For detailed instructions on replacing the jabberd/osa
database, see Oracle Linux Manager: Installation Guide for
Release 2.10 .
SELinux Policy Prevents SQL*Plus From Connecting to Oracle Database
If Oracle Linux Manager and Oracle Database are installed on the same host and SElinux is enabled, the default SELinux policy prevents the version of SQL*Plus that is installed by the Oracle Instant Client packages from connecting to the Oracle Database.
To work around this issue, use the SQL*Plus binary that is
installed by Oracle Database itself, which is located in
$ORACLE_HOME/bin
. Another workaround is to
set SELinux to permissive mode. (Bug ID 25743208)
Oracle Linux 6 Update 8 Fails to Run yum Commands After Registration
Registration of an Oracle Linux 6 Update 8 server succeeds with the built-in packages, but subsequent yum commands fail with the error: "KeyError: 'X-RHN-Auth-Expiration’”.
Installing the full Spacewalk client for Oracle Linux 6 resolves this problem and should be done prior to registration. Follow the steps in Installing the Oracle Linux Manager Client Software and Registering a Client System by Using the rhnreg_ks Command in Oracle Linux Manager: Client Life Cycle Management Guide for Release 2.10 .
Oracle Linux Manager Logging Settings
Oracle Linux Manager generates large numbers of log messages, particularly
under /var/log/httpd
. 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 the relevant information in Oracle® Linux 6: Administrator's Guide or Oracle Linux 7: Security Guide.
Oracle Linux Manager Fails to Install Due to the slf4j Package Being Installed
In some circumstances, Oracle Linux Manager 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.
Tomcat Fails to Start After Initial Oracle Linux Manager Configuration
The Tomcat service fails to start if the jta
package is installed on the system instead of the
geronimo-jta-1.1-api
package.
To resolve the issue, remove the jta
package
and then install the geronimo-jta-1.1-api
package. After the correct package is installed, restart the
Spaacewalk services.
sudo /usr/sbin/spacewalk-service restart
Issues Related to FQDNs
Fully Qualified Domain Names (FQDNs) for host names are strict requirements for installing Oracle Linux Manager Server. If you do not use FQDNs, or if you use invalid FQDNs, various errors would arise such as invalid Preboot eXecution Environment (PXE) boot configuration files. Further, Oracle Linux Manager would be unable to create valid CA certificates, which would impact client registrations.
For more information on the proper use of FQDNs, see Networking Requirements in Oracle Linux Manager: Installation Guide for Release 2.10 .
Out of Memory Issues With Large Repositories or Data Sets
When building repository metadata, Oracle Linux Manager can fail with an "Out of Memory" error that is linked to default Java memory settings. For a detailed discussion about this issue and its resolution, see Memory Considerations When Building Repositories in Oracle Linux Manager: Client Life Cycle Management Guide for Release 2.10 .
Clients Might Have to Re-Register After an Upgrade
After an Oracle Linux Manager server is upgraded, Oracle Linux Manager clients might
have to re-register with Oracle Linux Manager server. The web interface
shows these clients as registered, but when you run the
rhncfg-client command on the client, errors
such as Authentication failed: Invalid digital server
certificate
are displayed.
If this problem occurs, use either the rhn_register command or the rhnreg_ks --force command to re-register the client.
Oracle Linux Manager Does Not Work If root User Has a Restrictive umask
If the root
user's umask
is too restrictive (for example, 0077
or
similar, instead of 0022
), Apache, Tomcat,
and Java processes cannot read some files that are written
during an Oracle Linux Manager installation or written by commands such as
spacewalk-repo-sync or
spacecmd. Clients might also stop working
because Oracle Linux Manager cannot serve yum
metadata
or package files.
yum Command Displays HTML
To prevent the yum
command from displaying
many lines of HTML when it is run on an Oracle Linux Manager client, do
either of the following:
-
Edit the
/etc/yum/pluginconf.d/ulninfo.conf
file and set theenable
value to0
. -
Remove the
yum-plugin-ulninfo
package.
Issues With Kickstart After an Upgrade
After an Oracle Linux Manager server is upgraded, using existing kickstart profiles and distributions might result in errors.
The web interface might display error messages such as the following:
This kickstart profile uses a different type of
encryption by default than the root password is currently using.
You must reset the root password to encrypt it with the new
method.
As a workaround, do the following:
-
Reset the
root
password. -
Restart Oracle Linux Manager service.
sudo/usr/sbin/spacewalk-service restart
-
Remount your distribution trees and ISO images.