Taskomatic process fails to start

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

Environment

SUSE Manager 3.2

Situation

While starting spacewalk services, taskomatic.service fails to start.
Below error can be seen in /var/log/rhn/rhn_taskomatic_daemon.log:

STATUS | wrapper  | 2020/01/10 11:02:11 | Launching a JVM...
ERROR  | wrapper  | 2020/01/10 11:02:11 | JVM exited while loading the application.
INFO   | jvm 5    | 2020/01/10 11:02:11 | Unrecognized option: -Xdump:heap:file=/var/crash/heapdump.%Y%m%d.%H%M%S.%pid.%seq.phd
INFO   | jvm 5    | 2020/01/10 11:02:11 | Error: Could not create the Java Virtual Machine.
INFO   | jvm 5    | 2020/01/10 11:02:11 | Error: A fatal exception has occurred. Program will exit.

/var/log/messagess

Jan 10 11:02:11 dekalssps006 systemd[1]: taskomatic.service: Main process exited, code=exited, status=1/FAILURE
Jan 10 11:02:11 dekalssps006 taskomatic[23034]: Stopping Taskomatic...
Jan 10 11:02:11 dekalssps006 taskomatic[23034]: Taskomatic was not running.
Jan 10 11:02:11 dekalssps006 systemd[1]: taskomatic.service: Unit entered failed state.
Jan 10 11:02:11 dekalssps006 systemd[1]: taskomatic.service: Failed with result 'exit-code'.
Jan 10 11:02:12 dekalssps006 systemd[1]: taskomatic.service: Service RestartSec=100ms expired, scheduling restart.

Resolution

Use below command on SUMA server:

update-alternatives --config java

Choose /usr/lib64/jvm/jre-1.8.0-ibm/bin/java and restart spacewalk-service after.

Cause

java-1_8_0-openjdk was installed and from that time used by default instead of java-1_8_0-ibm

java-1_8_0-openjdk is not needed on SUMA server and is not installed by default

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.