When I try and load the login page for spacewalk I get a black page. I just
updated yum from about june of this year. I was on version 1.9 of
spacewalk. The OS is now centos 6.5

Here are some logs
cat postgresql-Mon.log

2013-12-02 07:59:32.893 EST ERROR:  schema "logging" does not exist
2013-12-02 07:59:32.893 EST STATEMENT:  SELECT logging.clear_log_id()
2013-12-02 07:59:49.028 EST ERROR:  schema "logging" does not exist
2013-12-02 07:59:49.028 EST STATEMENT:  select * from
logging.clear_log_id() as result
2013-12-02 07:59:49.033 EST ERROR:  current transaction is aborted,
commands ignored until end of transaction block
2013-12-02 07:59:49.033 EST STATEMENT:  select 'c3p0 ping' from dual
2013-12-02 07:59:49.068 EST ERROR:  schema "logging" does not exist
2013-12-02 07:59:49.068 EST STATEMENT:  select * from
logging.clear_log_id() as result
2013-12-02 07:59:49.068 EST ERROR:  current transaction is aborted,
commands ignored until end of transaction block
2013-12-02 07:59:49.068 EST STATEMENT:  select 'c3p0 ping' from dual
2013-12-02 07:59:50.026 EST ERROR:  current transaction is aborted,
commands ignored until end of transaction block
2013-12-02 07:59:50.026 EST STATEMENT:  select roleimpl0_.id as id194_,
roleimpl0_.name as name194_, roleimpl0_.label as label194_,
roleimpl0_.created as created194_, roleimpl0_.modified as modified194_ from
RHNUSERGROUPTYPE roleimpl0_ where roleimpl0_.label=$1
2013-12-02 07:59:50.026 EST ERROR:  current transaction is aborted,
commands ignored until end of transaction block
2013-12-02 07:59:50.026 EST STATEMENT:  select 'c3p0 ping' from dual
2013-12-02 08:01:14.426 EST ERROR:  schema "logging" does not exist
2013-12-02 08:01:14.426 EST STATEMENT:  SELECT logging.clear_log_id()
2013-12-02 08:05:28.151 EST ERROR:  schema "logging" does not exist
2013-12-02 08:05:28.151 EST STATEMENT:  SELECT logging.clear_log_id()


[root@space ~]# tail /var/log/messages
Dec  2 07:11:42 space wrapper[2386]: JVM did not exit on request, terminated
Dec  2 07:11:42 space wrapper[2386]: JVM exited in response to signal
SIGKILL (9).
Dec  2 07:11:42 space wrapper[2386]: There were 5 failed launches in a row,
each lasting less than 300 seconds.  Giving up.
Dec  2 07:11:42 space wrapper[2386]:   There may be a configuration
problem: please check the logs.
Dec  2 07:11:42 space wrapper[2386]: <-- Wrapper Stopped
Dec  2 07:56:04 space jabberd/c2s[1716]: [9] [::ffff:216.105.159.21,
port=56046] connect
Dec  2 07:56:13 space jabberd/c2s[1716]: [9] legacy authentication
succeeded: host=, username=rhn-dispatcher-sat, resource=superclient, TLS
negotiated
Dec  2 07:56:13 space jabberd/c2s[1716]: [9] requesting session: jid=
[email protected]/superclient
Dec  2 07:56:13 space jabberd/c2s[1716]: [7] [::ffff:216.105.159.21,
port=55789] disconnect jid=
[email protected]/superclient, packets: 719
Dec  2 07:56:13 space jabberd/sm[1709]: session replaced: jid=
[email protected]/superclient


-- 
Zach Underwood  (RHCE,RHCSA,RHCT,UACA)
My website <http://zachunderwood.me/>
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to