Taskomatic not starting on SUSE Manager 4.1

This document (000019667) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Enterprise Server 15 SP 2
SUSE Manager Server 4.1

Situation

After migration from SUSE Manager 4.0 on SLES15 SP1 to SUSE Manager 4.1 on SLES15 SP2 or after updating a SUSE Manager 4.2 server, taskomatic fails to start. On the system the "Development Tools Module 15 SP2" has been installed.

The log /var/log/rhn/rhn_taskomatic_deamon.log will show a memory error.

Resolution

To issue has been reported to engineering and is waiting a definitive solution.

The current workaround is to install the correct version:

rpm -e --nodeps httpcomponents-core
SUSEConnect -d -p sle-module-development-tools/15.2/x86_64
zypper in httpcomponents-core=4.4.1-1.110

Please check if the broken links are not presents any more.

Cause

The root cause is that in the development channel there is a newer of version of httpcomponents will be installed:

S | Name                | Typ   | Version     | Arch   | Repository
--+---------------------+-------+-------------+--------+----------------------------------------
i | httpcomponents-core | Paket | 4.4.10-1.63 | noarch | SLE-Module-DevTools15-SP2-Pool
v | httpcomponents-core | Paket | 4.4.1-1.110 | noarch | SLE-Module-SUSE-Manager-Server-4.1-Pool

In this newer RPMs the location has changed for needed jar files. The following command will show the broken links:

find /usr/share -xtype l

This will show several jars with broken links in /usr/share/spacewalk/taskomatic and /srv/tomcat/webapps/rhn/WEB-INF/lib

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.