[Spacewalk-list] Starting osa-dispatcher hangs
Will Cladek
will.cladek at nrl.navy.mil
Thu Nov 14 17:03:51 UTC 2013
Well, contrary to that page, it appears that /usr/bin/jabberd, /usr/bin/resolver, and /etc/jabberd/resolver.xml are not supposed to exist.
A clean reinstall of jabberd caused that component to start working again. So after that I did a fresh "spacewalk-setup --disconnected --external-db" which reconfigured jabber properly, and everything seems to work now.
On 11/14/2013 7:46 AM, Will Cladek wrote:
> I looked through the "Key Files for jabberd" section, and here's one possible problem: /usr/bin/jabberd, /usr/bin/resolver, and /etc/jabberd/resolver.xml do not exist. (All other files haven't changed in months.) jabberd *is* installed from the epel repo. Doing a "yum reinstall jabberd" doesn't help.
>
> Are these missing files the likely culprit for why restarting jabberd with an empty /var/lib/jabberd/db/ doesn't regenerate its contents?
>
> -Will
>
> On 11/13/2013 3: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 <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 <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
>>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
More information about the Spacewalk-list
mailing list