I need to make a correction. It seems that spacewalk-repo-sync might not be the cause of this issue.Yesterday, I performed a couple of manual repo syncs and OSAD stayed up and running but when I came in this morning it was down again. In order to get the clients back up and going I have to perform the following.
service jabberd stop service osa-dispatcher stop rm -f /var/lib/jabberd/db/* service jabberd start service osa-dispatcher start These steps seem to get osad back up and going until the next morning. Is there any solution to this problem? I have added the patch noted on the following bugzilla. It seems to be the same issue. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=662593 Thank you for your time and have a great day! Kind regards, JD ---- [email protected] wrote: > Hello All, > > I am currently having issues with OSAD when I am performing > spacewalk-repo-sync with a custom script that provides a channel and performs > a sync of each channel within a list of channels. This runs every 10 minutes. > It seems that after a while this script causes issues with OSAD. > > To test this idea I left this script off for 48 hours and osad stayed up and > running. When I turned on this script after about 24 hours the osa service > wouldn't send remote commands to the client (Ping from the Web UI still > worked). After turning off the custom script it seems everything is back up > and going. > > Is there a suggested way to be able to continually update the channels with > new content but still be able to have the OSAD functionality? > > Thank you for your time and have a great day! > > Kind regards, > JD > > _______________________________________________ > 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
