[Spacewalk-list] jabberd log files

[r.rigby at leeds.ac.uk]

hi keith,

On Tue, 15 Mar 2011, Hagberg, Keith wrote:

> I have followed the directions and have gotten osa-dispatcher and jabberd working but not until deleting the osad-auth.conf and restarting the osad service.
>
> Also noticed no log files are generated with sqlite, is that normal.
>
> Still looking for a way to do this without having to restart the service on the client.
>
>
> Keith
>

i took some time yesterday evening to have a closer look at the osad 
problems which we had been having, and the information and suggestions on 
the bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=662593

after upgrading to 1.2, there were three main problems we had with 
osad/jabberd:

-db creating lots of log files, database frequently corrupting, and having 
to be re-created. so we switched to sqlite, which has been fine, no 
problems at all.

-clients could be pinged via osad, but would not pick up scheduled tasks. 
i put a hack in to osa_dispatcher.py, which got this working again, 
but don't think this would be a recommended solution.

-clients would not automatically re-connect to osad, if the database had 
been re-created. after switching to sqlite, and being happy that things 
were running o.k., i just ended up removing the osad-auth.conf file, and 
restarting osad on all the clients, and things have been running fine since
then.

the information from the bugzilla seems to have fixed the second and third 
of these for us.

from messages on this list, i don't believe everyone experienced the 
problem with osad clients not picking up the tasks, though some did.
updating the /etc/jabberd/sm.xml file as per this patch:

https://bugzilla.redhat.com/attachment.cgi?id=478869&action=diff

i.e. commenting out all the <module>*roster* lines, seems to have 
fixed this.

and applying this patch:

http://git.fedorahosted.org/git/?p=spacewalk.git;a=blobdiff;f=client/tools/osad/src/osa_dispatcher.py;h=7d96db765f182a0ba2a161132beaffb7e6250073;hp=3595717a3b3318fed76907532bda0edf277e57a7;hb=2ca8629f4d2bd681bd1db48b4672059fb1cdc653;hpb=93d09aa0f827faf2c6a93a8109c1ef2cdebc2deb

to osa_dispatcher.py, and removing our previous hack, seems to allow 
clients to re-connect to osad successfully, without having to remove the 
osad-auth.conf.
to double check this, i deleted, and recreated the database, and 
thankfully, everything seemed to work correctly.

hope this information is of some use.

thanks,

richard