I'm wondering if anyone can help me with a rather strange error that's preventing Taskomatic to start up on a brand new Spacewalk-2.4 install on a CentOS-7 server.
The only non-standard thing I'm doing is I'm running PostgreSQL 9.4 (from the PG yum repo) locally on the machine instead of the 9.2 version that's included by default in CentOS 7. All other services start without problems as verified by "spacewalk-service status". The error I'm seeing is a Java error that is originating from /usr/share/java/xerces-j2.jar and is supposedly cast when it receives a malformed XML file to process. The error is in question is "[Fatal Error] :1:50: White spaces are required between publicId and systemId." Here is the whole contents of /var/log/rhn/rhn_taskomatic.log STATUS | wrapper | 2016/05/30 09:43:30 | --> Wrapper Started as Daemon STATUS | wrapper | 2016/05/30 09:43:30 | Launching a JVM... INFO | jvm 1 | 2016/05/30 09:43:30 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1 | 2016/05/30 09:43:30 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1 | 2016/05/30 09:43:30 | INFO | jvm 1 | 2016/05/30 09:43:30 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. INFO | jvm 1 | 2016/05/30 09:43:34 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. INFO | jvm 1 | 2016/05/30 09:43:38 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. INFO | jvm 1 | 2016/05/30 09:43:42 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. INFO | jvm 1 | 2016/05/30 09:43:46 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. INFO | jvm 1 | 2016/05/30 09:43:50 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. INFO | jvm 1 | 2016/05/30 09:43:54 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. INFO | jvm 1 | 2016/05/30 09:43:58 | [Fatal Error] :1:50: White spaces are required between publicId and systemId. ERROR | wrapper | 2016/05/30 09:43:59 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2016/05/30 09:43:59 | JVM did not exit on request, terminated INFO | wrapper | 2016/05/30 09:43:59 | JVM exited on its own while waiting to kill the application. STATUS | wrapper | 2016/05/30 09:44:00 | JVM exited in response to signal SIGKILL (9). Red Hat seems to have a solution to this error, but it's locked behind their paywall. https://access.redhat.com/solutions/171133 -- *Arnar "Addi" Gunnarsson* // [email protected]
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
