[Spacewalk-list] Starting osa-dispatcher hangs

[Vincent Moutoussamy]

On 11/13/2013 09:45 PM, Justin Edmands wrote:
> On Wed, Nov 13, 2013 at 3:28 PM, Will Cladek <will.cladek at nrl.navy.mil 
> <mailto:will.cladek at nrl.navy.mil>> wrote:
>
>     No firewall or selinux currently running.
>
>     All directories in /var/lib/jabberd have proper ownership and
>     permissions.  But as I mentioned before, the db directory is
>     completely empty.  Is there something I can do to
>     reinstall/reinitialize just the jabberd component?
>
>
>     On 11/13/2013 3:08 PM, Justin Edmands wrote:
>
>         Things to check:
>         1 - firewall / selinux
>
>         2 - Permissions on the /var/lib/jabberd/db to be jabber:jabber
>
>         [root at spacewalk1 ~]# ll /var/lib/jabberd/db
>         total 29564
>         -rw-r----- 1 jabber jabber   184320 Nov 13 13:03 authreg.db
>         -rw-r----- 1 jabber jabber    24576 Nov 13 03:16 __db.001
>         -rw-r----- 1 jabber jabber   204800 Nov 13 15:04 __db.002
>         -rw-r----- 1 jabber jabber   270336 Nov 13 15:04 __db.003
>         -rw-r----- 1 jabber jabber    98304 Nov 13 15:04 __db.004
>         -rw-r----- 1 jabber jabber   753664 Nov 13 15:04 __db.005
>         -rw-r----- 1 jabber jabber    57344 Nov 13 15:04 __db.006
>         -rw-r----- 1 jabber jabber 10485760 Nov 13 07:07 log.0000000001
>         -rw-r----- 1 jabber jabber 10485760 Nov 13 11:45 log.0000000002
>         -rw-r----- 1 jabber jabber 10485760 Nov 13 15:04 log.0000000003
>         -rw-r----- 1 jabber jabber   380928 Nov 13 14:56 sm.db
>         [root at spacewalk1 ~]# ll /var/lib/jabberd
>         total 16
>         drwx------ 2 jabber jabber 4096 Nov 13 11:45 db
>         drwx------ 3 jabber jabber 4096 Apr 26  2013 db.bak
>         drwx------ 2 jabber jabber 4096 Jan 25  2013 log
>         drwx------ 2 jabber jabber 4096 Nov 13 03:16 pid
>
>
>
>
>
>         _______________________________________________
>         Spacewalk-list mailing list
>         Spacewalk-list at redhat.com <mailto:Spacewalk-list at redhat.com>
>         https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>     _______________________________________________
>     Spacewalk-list mailing list
>     Spacewalk-list at redhat.com <mailto:Spacewalk-list at redhat.com>
>     https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> I remove the contents in my jabberd folder pretty frequently. It will 
> regenerate them on a successful startup.
>
> A lot of very helpful info here:
>
> https://fedorahosted.org/spacewalk/wiki/OsadHowTo
>
> Although you are in search of a simple fix, don't overlook even a 
> single line in that posting. It is all very important.
>
>
> /etc/jabberd folder has a good bit of files to look through. the .xml 
> files need to properly point to your server, IP, etc.
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
Hi,

I'm just curious because this workaround helped me 3 or 4 times and I 
was wondering why we need to delete the jabberd database and restart 
jabberd "blindly" for this kind of issue.
Is there any knowned root causes ?

the wiki said :

Berkeley DB corruption

There is an intermittent problem with the interaction between jabberd 
and the Berkeley database it uses by default. Occasionally (not seen 
much any more), the database will become "wedged" and the osads on the 
clients will not pick up scheduled actions. Pings, however, still work. 
When/if this occurs, the only known solution is to restart jabberd - 
this will automatically remove the files in /var/lib/jabberd/.

Do you have more details about this ?

Thanks,

Regards,

-- 
Vincent Moutoussamy
SUSE Technical Support Engineer - France
Tel : +33 (0) 1 55 62 50 29 Mob : +33 (0) 6 07 19 77 98
Email : vmoutoussamy at suse.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20131114/33c99e7d/attachment.htm>