Jiri – thanks very much!
When I compare my /var/cache/rhn/repodata for centos 7 and centos 6 they are
way different.
Here you can see the difference in size and the filelists, other and primary
files all have the same “packages=0”
[cid:image002.png@01D3167D.66154770]
So basically (on the
Alright, good points. Could you please verify that data in
"/var/cache/rhn/repodata/" on server-side are correct for given channel?
Jiri
Dne 16.8.2017 v 16:12 Ron Skantz napsal(a):
Some additional information - I have also registered another client
and it is showing the same symptoms.
Jiri,
Thanks for the response.
Ok yea, I forgot to mention what I had tried:
Yes I have run “yum clean all”, “yum clean metadata” and I have also tried
deleting the entire /var/yum/cache/* on the client along with deleting and
registering the client – but this one channel still shows zero.
Hi Ron,
it's usually a good thing to run "yum clean all" after registering a
client, just to make sure the repository cache is flushed. "yum clean
all" should do the thing, if not try to delete it manually in
/var/cache/yum/. Next run of "yum repolist" should display package
numbers
When I do a "yum repolist" from a recently registered client it shows the
status of 0 packages for one of the repo channels that on the Spacwalk host
shows: 6706 packages.
Why would a single channel show no packages?
If you have access to redhat docs then maybe you have been blessed with the
Hi!
for the "books"
I used following sollution:
#cd /etc/httpd/conf.d
#vi aa-spacewalk-25-client-fix.conf
and inserted:
#
# Workaround to deal with older (yum|dnf)-rhn-plugin issue where the
plugin sends
# mildly-malformed HTTP headers, in a way that strict RFC compliance
rejects with
# a
Hi!
This will be the 2.6 client, there is nothing newer than the 2.5.5-1 in
the SpaceWalk 2.5 repo.?
I'll have first a look at the "HttpUnsafe..."Parameter, I do not like to
mix that Versions, eventhough Ih would have to establish a new channel
etc.
Cheers
Matthias
Hello,
update of yum-rhn-plugin package on your clients should resolve your
problems.
Additionally putting [1] into /etc/httpd/conf.d/aa-spacewalk-server.conf
can serve as temporary workaround.
Tomas
[1] -
I ran into this just a couple of hours ago. While this applies to Apache 2.4,
the HTTPProtocolOptions unsafe config worked for my Spacewalk 2.3 instance
running on CentOS 6 with Apache 2.2.
https://bugzilla.redhat.com/show_bug.cgi?id=1445428#c2
Cody Skidmore
Fuqua School of Business
Duke
Hi!
We have a SpaceWalk 2.5 with several proxy running, all on CentOS 6.9
After patching the first two Proxies this week, the clients which are
attached to this updated proxies doesnt receiving any updates anymore
Simply getting:
root@lvasp-uimvmgmt ~]# yum repolist
Loaded plugins:
10 matches
Mail list logo
