On the contrary, I think upgrading to 1.4 from 1.2 can do nothing but help. I myself was having some annoying issues with jabberd/osad (it mostly worked after some major tweaking), but it seems like my 1.4 install worked right out of the box - and with postgresql as a back end, to boot. I was certain I'd be fighting that beast again, but the clients are picking up scheduled actions just fine.
On 2011-05-10 11:22 AM, "Jason M. Nielsen" <[email protected]> wrote: >So out of desperation as I have been through every document, email list, >bugzilla report I can lay my hands on and had zero luck getting this to >work I wiped jabber from the system and reinstalled: > >rpm --nodeps -e jabberd >mv /etc/jabberd /etc/jabberd.old >rm -f /var/lib/jabberd/db >yum install jabberd >spacewalk-setup-jabberd --macros hostname:leonov.myriad.com --verbose > >Now jabberd starts up. server.pem still looks wrong (that is: >localhost.localdomain) and I now get the following from OSAD: > >2011/05/10 09:13:47 -06:00 19648 0.0.0.0: osad/jabber_lib.__init__ >2011/05/10 09:13:47 -06:00 19648 0.0.0.0: >osad/jabber_lib.connect('ERROR', 'Server did not return a <features /> >stanza') >2011/05/10 09:13:47 -06:00 19648 0.0.0.0: >osad/jabber_lib.print_message('SSLError',) >2011/05/10 09:13:47 -06:00 19648 0.0.0.0: >osad/jabber_lib.print_message('Could not connect to jabber server', >'localhost.localdomain') >2011/05/10 09:13:47 -06:00 19648 0.0.0.0: >osad/jabber_lib.setup_connection('ERROR', 'Traceback (most recent call >last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 254, in >setup_connection\n c = self._get_jabber_client(js)\n File >"/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client\n > c.connect()\n File "/usr/share/rhn/osad/jabber_lib.py", line 584, in >connect\n raise SSLDisabledError\nSSLDisabledError\n') >2011/05/10 09:13:47 -06:00 19648 0.0.0.0: >osad/jabber_lib.setup_connection('Could not connect to any jabber >server',) >2011/05/10 09:13:47 -06:00 19648 0.0.0.0: osad/jabber_lib.main('Unable >to connect to jabber servers, sleeping 10 seconds',) > > >I have exhausted everything I can find on the net and nothing changes >anything. I have uncommented the pem file line etc. It seems obvious Im >missing something but Ill be damned if I can find a shred of useful >information that provides a fix or a howto on what it supposed to be >configured. > >Ive actually been considering trying an upgrade from 1.2 to 1.4 in hopes >it just magically fixes it but somehow I sincerely doubt thats going to >do anything. > >Any help would be greatly appreciated. > >On 05/05/2011 01:30 PM, Kennedy, Ryan wrote: >> The PEM should be generated based on your spacewalk servers >>hostname.domain (I think). That's what mine matches up with anyway. >> >> -----Original Message----- >> From: [email protected] >>[mailto:[email protected]] On Behalf Of Jason M. Nielsen >> Sent: Thursday, May 05, 2011 6:41 AM >> To: [email protected] >> Subject: Re: [Spacewalk-list] Jabberd sm c2s failing >> >> Much appreciated but I have effectively been through all of that >>without success. The errors remain the same. I tried it again this >>morning from the docs you noted just to be sure there were no >>differences and hopefully I have some how not missed any steps. >> >> One thing I did notice is that the PEM file looks to be setup for >>localhost.localdomain. I do not recall when nor how this file was >>generated. >> >> I have not reinstalled jabberd yet. Does that sound like a wise move? >> >> On 05/04/2011 12:26 PM, Kennedy, Ryan wrote: >>>> From all of the documentation I have seen this issue is normally >>>>resolved by rm'ing the jabberd DB files... >>> Take a look at these: >>> http://osdir.com/ml/spacewalk-list/2010-02/msg00097.html >>> https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD >>> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Jason M. >>> Nielsen >>> Sent: Wednesday, May 04, 2011 11:02 AM >>> To: [email protected] >>> Subject: [Spacewalk-list] Jabberd sm c2s failing >>> >>> Im having issues getting OSAD to work and I think its related to >>>jabberd not starting properly. "sm" will not start at all and I can >>>find no logs any place as to why. "c2s" starts for a while then dies. >>>See logs below. >>> Looking for suggestions as Ive been beating my head on this wall off >>>an on for over a month but it always ends up on a back burner or in the >>>freezer. Thanks! >>> >>> OSA Dispatcher fails but apparently due to it being unable to connect >>>to jabberd. >>> >>> SW 1.2 >>> RHEL 5.6 >>> spacewalk-setup-jabberd-1.3.1-1.el5 >>> jabberd-2.2.11-2.el5 >>> jabberd-selinux-1.5.1-1.el5 >>> >>> >>> May 4 11:51:07 leonov jabberd/router[27504]: starting up May 4 >>>11:51:07 leonov jabberd/router[27504]: process id is 27504, written to >>>/var/lib/jabberd/pid/router.pid May 4 11:51:07 leonov >>>jabberd/router[27504]: loaded user table (1 users) May 4 11:51:07 >>>leonov jabberd/router[27504]: loaded filters (0 rules) May 4 11:51:07 >>>leonov jabberd/router[27504]: [0.0.0.0, port=5347] listening for >>>incoming connections May 4 11:51:08 leonov jabberd/c2s[27540]: >>>starting up May 4 11:51:08 leonov jabberd/c2s[27540]: process id is >>>27540, written to /var/lib/jabberd/pid/c2s.pid May 4 11:51:08 leonov >>>jabberd/c2s[27540]: modules search path: >>> /usr/lib64/jabberd >>> May 4 11:51:08 leonov jabberd/c2s[27540]: loading 'db' authreg module >>>May 4 11:51:08 leonov jabberd/c2s[27540]: initialized auth module 'db' >>> May 4 11:51:08 leonov jabberd/c2s[27540]: [leonov] configured; >>>realm=, registration enabled May 4 11:51:08 leonov jabberd/c2s[27540]: >>>attempting connection to router at 127.0.0.1, port=5347 May 4 11:51:08 >>>leonov jabberd/router[27504]: [127.0.0.1, port=55231] connect May 4 >>>11:51:08 leonov jabberd/c2s[27540]: error from router: >>> Authentication failed ((null)) >>> May 4 11:51:08 leonov jabberd/router[27504]: [127.0.0.1, port=55231] >>> disconnect May 4 11:51:08 leonov jabberd/c2s[27540]: connection to >>>router closed May 4 11:51:08 leonov jabberd/c2s[27540]: attempting >>>reconnect (3 left) PAML EMAIL DISCLAIMER: >>> Information contained in this message may be privileged and >>>confidential. >>> If the reader of this message is not the intended recipient, be >>> notified that any dissemination, distribution or copying of this >>> communication is strictly prohibited. If this communication is >>> received in error, please notify the sender immediately by replying to >>> the message and deleting from your computer. Thank you >>> >>> >>> _______________________________________________ >>> 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 >> _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
