[Spacewalk-list] jabberd log files

[Hagberg, Keith]

I have confirmed this will break osad on the client. The only way to get the client to work after this is to stop osad, delete the osad-auth.conf file and restart osad. 

Is there a way to manage sm.db or not.

Pretty much makes osad useless if you cannot control it.

Keith

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Hagberg, Keith
Sent: Friday, March 11, 2011 1:12 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] jabberd log files

Is doing the following going to hose my clients?

service osa-dispatcher stop
service jabberd stop
rm -rf /var/lib/jabberd/db/*
service jabberd start
service osa-dispatcher start



-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Sander Grendelman
Sent: Friday, March 11, 2011 9:22 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] jabberd log files

On Thu, Mar 10, 2011 at 10:36:09AM -0500, Hagberg, Keith wrote:
> Running Spacewalk 1.3 with osad and jabberd. Noticed that jabberd is eating up disk space in /var/lib/jabbered/db. Here is the tail end of my directory listing
> 
> 
> -rw-r----- 1 jabber jabber  10485760 Mar 10 00:23 log.0000000127
> -rw-r----- 1 jabber jabber  10485760 Mar 10 02:13 log.0000000128
> -rw-r----- 1 jabber jabber  10485760 Mar 10 03:41 log.0000000129
> -rw-r----- 1 jabber jabber  10485760 Mar 10 05:04 log.0000000130
> -rw-r----- 1 jabber jabber  10485760 Mar 10 06:26 log.0000000131
> -rw-r----- 1 jabber jabber  10485760 Mar 10 07:48 log.0000000132
> -rw-r----- 1 jabber jabber  10485760 Mar 10 09:10 log.0000000133
> -rw-r----- 1 jabber jabber  10485760 Mar 10 10:23 log.0000000134
> -rw-r----- 1 jabber jabber 705732608 Mar 10 10:23 sm.db
> 
> Lots of log files and that big sm.db file

Looks like db4 transaction logs, you can check which transactionlogs are
no longer in use by installing the db4-utils package and running:

db_archive -a -h /var/lib/jabberd/db

This should show all the logfiles that are no longer involved in active
transactions.

It should also be quite safe to remove the jabberd database, it will be
regenerated automagically (you can/should make a backup just to be on
the safe side ...).

service osa-dispatcher stop
service jabberd stop
rm -rf /var/lib/jabberd/db/*
service jabberd start
service osa-dispatcher start

Kind regards,

Sander Grendelman.

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list