Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Am 12. September 2017 05:13:36 MESZ schrieb Andrew Bergman : >I just removed the jabber RPM, reinstalled with a clean slate, ran >spacewalk-setup-jabberd > >Jabberd runs fine using the SSL cert I provided built with the FQDN, >but again, osa-dispatcher fails with same

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

I just removed the jabber RPM, reinstalled with a clean slate, ran spacewalk-setup-jabberd Jabberd runs fine using the SSL cert I provided built with the FQDN, but again, osa-dispatcher fails with same error. Maybe I should reinstall osa-dispatcher? Regards Andrew -Original

[Spacewalk-list] Ubuntu errata and Spacewalk 2.7

Hi, Last week I finished updating our Spacewalk server to 2.7 and rebuilding all our Ubuntu channels and repos. I then tried to reload all the old Ubuntu errata with the same scripts I used in the past (using Philipp Schuler's parseUbuntu.py script to generate an input file for Pedro Andujar's

Re: [Spacewalk-list] bug in channel.software.mergeErrata?

Am 30.08.2017 um 15:33 schrieb Lichtinger, Bernhard: Hello, I see a strange behavior of spacewalk using spacewalk-manage-channel-lifecycle: Everytime I promote a channel all erratas which source and destination channel have in common are removed from the source channel. For example: source

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Okay...thenwhat error do you get, when you try to setup jabberd from scratch (via the setup script) and ".dist" files? -Ursprüngliche Nachricht- Von: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Andrew Bergman Gesendet: Montag, 11.

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Or maybe the best way is really to wipe all and reinstall spacewalk from scratch. You could first extract the list of "clients" currently registered there, setup spacewalk (all should be running then  ), create activation keys and force a re-registration on every client. On every client

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

There is no clients using this - I adopted this spacewalk server which had been built by someone who did not understand Spacewalk/Satellite. It was a glorified yum repository with a pretty front end. Most functionality didn't work and it wasn't even receiving updates properly. I fixed all

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Hmma hard one. What errors do you get on the "client" side? -Ursprüngliche Nachricht- Von: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Andrew Bergman Gesendet: Montag, 11. September 2017 07:43 An: spacewalk-list@redhat.com