Hello,
I've found the root cause of your problem. Feel free to apply the patch [1]
manually.
As it affects all spacecmd commands, I hope, I didn't break anything else.
Regards,
--
Tomas Lestach
Red Hat Satellite Engineering, Red Hat
[1]
On 05/08/2015 06:52 PM, Matthew Madey wrote:
I'm seeing an issue with packages 300MB and larger being served by
Spacewalk proxies. When I run yum install on a client, it gets to 97% of
the download or so and fails with the below message:
Error Downloading Packages:
somepackage.x86_64:
Hello James,
here're the packages for Spacewalk 2.3 on:
RHEL6: [1]
RHEL7: [2]
If, you'd like to apply them, do:
1. download the rpms to a local directory
2. stop spacewalk services
3. rpm -Fvh *.rpm
in the local directory
(this will freshen the installed packages,
what means it will update only
I’m using Red Hat Satellite 5.7. Each month I clone the distribution channels
so I can have sets of machines at the identical patch level and those patches
can be worked through the testing cycle before being applied in production.
Currently I am doing this manually through the GUI. A mindless,
Hey,
I did a small script which collects all relevant security Errata and posts
them to a Slack channel.
If you are interested, see
http://www.devops-blog.net/spacewalk/spacewalk-errata-integration-for-slack
Best, Phil
___
Spacewalk-list mailing list
Thanks Thomas! I'll pull it down during the day or two and let you know.
Thanks again,
Les
Sent from my Samsung Galaxy S3
-Original Message-
From: Tomas Lestach tlest...@redhat.com
To: spacewalk-list@redhat.com
Sent: Mon, 11 May 2015 9:44 PM
Subject: Re: [Spacewalk-list] spacecmd
Hi,
This is simple to do with the API via channel.software.mergePackages and
channel.software.mergeErrata.
Although I’m used to working with Golang, the below should do half of what you
want. You could easily modify it. Please note it has not been tested.
import xmlrpclib
import getpass
Thanks for the responses. No, there are no other proxies between the
Spacewalk Proxy and client, and I don't have any timeout settings specified
in rhn.conf, yum.conf, or up2date.
If I register the client directly to the Spacewalk server, I'm able to
download the package without an issue.. so the
Hi All!
I'm having an issue with package autoinstall using an activation key.
Using SW 2.3 on CentOS 6.6.
In the activation key setting I have a list of packages to install upon
registration:
During the rhn_reg ks, it pulls in the majority of packages, but misses a
couple out.
Most notably
Stephen, that was exactly it! Thank you!
On Mon, May 11, 2015 at 2:46 PM, Stephen Herr sh...@redhat.com wrote:
Oh, I bet you're running out of space in /tmp and hitting this behavior:
https://bugzilla.redhat.com/show_bug.cgi?id=1158193
Proxy 2.0 and on stores large files in /tmp instead of
I was able to get some more verbose output, which is showing a socket
timeout. (I have tried with and without using SSL to download the package).
[Mon May 11 15:35:04 2015] [error] Exception reported from
spw-proxy.ourcompany.com
[Mon May 11 15:35:04 2015] [error] Time: Mon May 11 15:35:04 2015
Oh, I bet you're running out of space in /tmp and hitting this behavior:
https://bugzilla.redhat.com/show_bug.cgi?id=1158193
Proxy 2.0 and on stores large files in /tmp instead of in-memory, since
people were having problems where they ran out of memory and then the
Out-Of-Memory killer would
Hi,
Am Freitag, 8. Mai 2015, 17:52:29 schrieb Matthew Madey:
I'm seeing an issue with packages 300MB and larger being served by
Spacewalk proxies. When I run yum install on a client, it gets to 97% of
the download or so and fails with the below message:
Error Downloading Packages:
13 matches
Mail list logo