500 Internal Error When Logging Into Spacewalk BUI

(Doc ID 2333105.1)

Last updated on DECEMBER 04, 2017

Applies to:

Linux OS - Version Oracle Linux 6.0 and later
Information in this document applies to any platform.

Goal


The Spacewalk is giving 500 Internal Error when logging into the BUI

--snip from status

Redirecting to /bin/systemctl status taskomatic.service
‚óŹ taskomatic.service - Taskomatic
Loaded: loaded (/usr/lib/systemd/system/taskomatic.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-10-27 12:28:01 EDT; 48min ago
Process: 23927 ExecStop=/usr/sbin/taskomatic stop (code=exited, status=0/SUCCESS)
Process: 23380 ExecStart=/usr/sbin/taskomatic start (code=exited, status=0/SUCCESS)
Main PID: 23393 (code=exited, status=1/FAILURE)

--snip from system logs

Oct 27 12:28:01 spacewalk-server systemd[1]: Unit taskomatic.service e...
Oct 27 12:28:01 spacewalk-server systemd[1]: taskomatic.service failed.


 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms