Ah ok run 'rm -rf /var/jabberd/*' Then restart spacewalk you will be good. This is a known issue osad used jabber under the hood and some times its database goes wrong. Without it you failback to the old mechanism which by default runs rhn_check every 240 minutes. The good news is you don't need the data in the database so you can wipe it out without concern. <div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;">-- Sent from my HP Pre3</div> <hr align="left" style="width:75%">On Feb 5, 2014 20:44, Chris <dmagick@gmail.com> wrote: On 06/02/14 11:32, Paul Robert Marino wrote: > Do you see a spike in CPU utilization of a couple hundred percent by a > java process for a while after you do it No, not really. I see a big spike when tomcat starts, but nothing else takes too long to start up. For completeness, spacewalk-service status does say: osa-dispatcher dead but pid file exists but from what I've seen that's unrelated to my issue, I hope I'm reading that correctly. -- Postgresql & php tutorials http://www.designmagick.com/ _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list