Re: [Spacewalk-list] specific repo to a server with kickstart

Hi Jérôme If I understand your question right, you could make the additional repo a Child repo of the Parent repo the Activation Key is associated with. Alternatively, you could create a separate repo with its own Activation Key. The system you're provisioning could then be registered with 2 Ac

[Spacewalk-list] Continuing issues with ubuntu client and Spacewalk 2.9

*Sadly,* *I am still getting the TRACEBACK error regarding diffs. Message from today:* Exception reported from spacewalk Time: Thu Feb 7 04:55:20 2019 Exception type Exception while handling function repodata Request object information: URI: ///XMLRPC/GET-REQ/ubuntu_16_updates/repodata/Packages.

Re: [Spacewalk-list] Cannot sync confluent (debian) repository to Spacewalk repo

I ran my sync with high verbosity hoping that someone can help with my sync failure... 2019/02/07 08:20:45 -04:00 Command: ['/usr/bin/spacewalk-repo-sync', '-vv', '--channel', 'confluent-ubuntu-amd64'] 2019/02/07 08:20:45 -04:00 1817 0.0.0.0: rhnSQL/driver_postgresql.convert_named_query_par

[Spacewalk-list] Yum.pid...

All, I am running Spacewalk 2.8 on Centos 7.x. I have noticed /var/run/yum.pid files being created early morning (around 5.30am) on Centos *6* servers ONLY. I thought it might be the yum-cron service running yum - but it is disabled. I also see in Spacewalk that the time of last checkin coi

Re: [Spacewalk-list] Continuing issues with ubuntu client and Spacewalk 2.9

Am 7. Februar 2019 14:09:23 MEZ schrieb James Krych : >*Sadly,* > >*I am still getting the TRACEBACK error regarding diffs. Message from >today:* >Exception reported from spacewalk >Time: Thu Feb 7 04:55:20 2019 >Exception type >Exception while handling function repodata >Request object informati

Re: [Spacewalk-list] Cannot sync confluent (debian) repository to Spacewalk repo

Am 7. Februar 2019 14:26:03 MEZ schrieb Ihor Lawrin : >I ran my sync with high verbosity hoping that someone can help with my >sync failure... > >2019/02/07 08:20:45 -04:00 Command: ['/usr/bin/spacewalk-repo-sync', >'-vv', '--channel', 'confluent-ubuntu-amd64'] >2019/02/07 08:20:45 -04:00 1817

Re: [Spacewalk-list] Continuing issues with ubuntu client and Spacewalk 2.9

*Syncing the repo again.* *That being done, this is the command I use to stop requesting diffs* #grouper-dev-loader-v:/root: !9949 apt-get update -o Acquire::Pdiffs=false Apt-Spacewalk: Updating sources.list Ign:1 spacewalk://spacewalk.mdc.musc.edu ubuntu_channel InRelease Ign:2 spacewalk://space

Re: [Spacewalk-list] Continuing issues with ubuntu client and Spacewalk 2.9

That looks like it worked. I take it that once the spacewalk packages have been installed, and the system registered, that updates will be pulled from the channels/repos on Spacewalk? James -- -- James W. Krych CCNP, CCNA, Net+, Security+, A+, Linux+ Mobile: 843-847-1446 james.w.kr...@gmail.com

Re: [Spacewalk-list] Continuing issues with ubuntu client and Spacewalk 2.9

Am 7. Februar 2019 17:19:59 MEZ schrieb James Krych : >*Syncing the repo again.* > This does *not* sync the repo! It only gets the metadata *for* the repo onto the client. The repo on the server (the channel) has to be updated. Robert >*That being done, this is the command I use to stop request

Re: [Spacewalk-list] Cannot sync confluent (debian) repository to Spacewalk repo

Looks like the same messages [root@c7spcwlk29tst01 rhn]# cat reposync/confluent-ubuntu-amd64.log | grep "2019/02/07 08:20" 2019/02/07 08:20:45 -04:00 Command: ['/usr/bin/spacewalk-repo-sync', '-vv', '--channel', 'confluent-ubuntu-amd64'] 2019/02/07 08:20:45 -04:00 Sync of channel started

Re: [Spacewalk-list] Continuing issues with ubuntu client and Spacewalk 2.9

Sorry, I failed to show you what I did on the server side: /usr/bin/spacewalk-repo-sync --channel ubuntu_16_security --type deb /usr/bin/spacewalk-repo-sync --channel ubuntu_16_updates --type deb -- -- James W. Krych CCNP, CCNA, Net+, Security+, A+, Linux+ Mobile: 843-847-1446 james.w.kr...@gmai

Re: [Spacewalk-list] Cannot sync confluent (debian) repository to Spacewalk repo

I'm guessing that it might be the way the debian repository is configured on the Confluent site. 1. We're able to sync update/base/security repos. 2. We're also able to sync the "rpm" repo from the Confluent site. Just not able to sync the "deb" version Ihor Lawrin Technical Services Senior Syst

Re: [Spacewalk-list] Cannot sync confluent (debian) repository to Spacewalk repo

I forgot to mention that the Ubuntu client is able to install the Confluent software (using the Confluent install procedure) when it has access to the internet. We want to have the software available via Spacewalk so that we don't have to connect all our clients to the internet. Hope this help

Re: [Spacewalk-list] Cannot sync confluent (debian) repository to Spacewalk repo

Am 7. Februar 2019 18:18:51 MEZ schrieb Ihor Lawrin : >I forgot to mention that the Ubuntu client is able to install the >Confluent software (using the Confluent install procedure) when it has >access to the internet. >We want to have the software available via Spacewalk so that we don't >have to

Re: [Spacewalk-list] SQL error in SSM after update to 2.9

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Doesn't anybody else experience this problem? Is there anybody out there using Spacewalk 2.9 with Oracle? Regards, Christian - -Ursprüngliche Nachricht- Von: spacewalk-list-boun...@redhat.com Im Auftrag von Hailer, Christian Gesendet: Fr