David, Thank you for the recommendation. I will use this command the next time jabber goes down and we will see if this is able to bring up the service.
All, I have some more information. Over the weekend the remote command functionality has stayed up. I have not changed anything other than restarting the services noted in this email list. The only difference between the weekend and a weekday is users logging in and performing remote commands and package management. During the weekend the only user logging in would be my script account that performs 1 remote command every thirty minutes to determine when osad goes down. Any other thoughts as to what might be causing this issue? On Mon, Aug 8, 2011 at 3:00 AM, David Nutter <[email protected]> wrote: > On Fri, Aug 05, 2011 at 08:29:53PM -0600, Jeremy Davis wrote: > > All, > > > > I have verified that this is DB corruption. Is there anyway to resolve > this > > DB corruption issue? > > As a work-around you could try the db_recover tool from > db4-utils. This should at least allow Jabber to open its databases > again, rather than crashing on startup due to the DBs being in an > inconsistent state. > > This probably isn't any better than removing the Jabber DBs though. > > Regards, > > -- > David Nutter Tel: +44 (0)131 650 4888 > BioSS, JCMB, King's Buildings, Mayfield Rd, EH9 3JZ. Scotland, UK > > Biomathematics and Statistics Scotland (BioSS) is formally part of The > James Hutton Institute (JHI), a registered Scottish charity No. SC041796 > and a company limited by guarantee No. SC374831 > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
