On Mon, Mar 12, 2012 at 03:41:42PM -0400, themaster001 wrote:
On Mon, Mar 12, 2012 at 11:27 AM, Jan Pazdziora jpazdzi...@redhat.com wrote:
On Fri, Mar 09, 2012 at 07:09:30AM -0500, themaster001 wrote:
I am trying to remove to a system, my spacewalk system. The web hangs
then I get an error
On Mon, Mar 12, 2012 at 08:26:56PM +, Wojtak, Greg (Superfly) wrote:
I'm trying to set up bare metal provisioning through a spacewalk proxy, but
I'm running into a little trouble. I guess it really all boils down to the
fact that in the kickstart file, all of the URL's reference
Hi,
same error on opensuse 11.4:
File /usr/sbin/rhnreg_ks, line 33, in from up2date_client
import rhnreg File /usr/share/rhn/up2date_client/rhnreg.py, line
14, in import up2dateUtils File
/usr/share/rhn/up2date_client/up2dateUtils.py, line 11, in
import up2dateErrors
That makes sense. I've given it another try and I get to the point in the
kickstart where the filesystems are created, then it pulls down the repo
information.
I get the following error (have to hit Ctrl+Alt+F3 to see it):
WARNING : Failed to get
On Tue, Mar 13, 2012 at 01:28:34PM +, Wojtak, Greg (Superfly) wrote:
That makes sense. I've given it another try and I get to the point in the
kickstart where the filesystems are created, then it pulls down the repo
information.
I get the following error (have to hit Ctrl+Alt+F3 to see
On Tue, Mar 13, 2012 at 3:17 AM, Jan Pazdziora jpazdzi...@redhat.com wrote:
On Mon, Mar 12, 2012 at 03:41:42PM -0400, themaster001 wrote:
On Mon, Mar 12, 2012 at 11:27 AM, Jan Pazdziora jpazdzi...@redhat.com
wrote:
On Fri, Mar 09, 2012 at 07:09:30AM -0500, themaster001 wrote:
I am trying
It does work directly from the spacewalk server.
I probably should have been more clear in my previous email about what I'm
perceiving the problem to be.
The repo name in the URL is having the 'spacewalk' replaced as well. In
this case, the repo is called spacewalk-client. I'm guessing that
Here's the situation:
* Master Spacewalk server is working fine
* Proxy server #1 is also fine, proxied clients are ping-able
* Proxy server #2 seems to be working, but clients are not ping-able.
Here's what I've tested on proxy server #2:
* Clients can register and run rhn_check -vv just
Below is a link to the output of osad -N -v. Any suggestions?
Forgot to mention; I did try blowing away the jabber databases both on
the master and proxy server, restarting osa-dispatcher, etc. but it
didn't help.
___
Spacewalk-list mailing
yea, I'm going to have to do the same thing but from SW 1.0 and oracle express.
On Tue, Mar 13, 2012 at 11:57 AM, Jason M. Nielsen jniel...@myriad.com wrote:
I am looking for recommendations on how to go about a major system upgrade
from:
RHEL5
SW 1.5
Oracle 11g
to:
RHEL6
SW 1.7
On 13.3.2012 17:23, Sean Carolan wrote:
Here's the situation:
* Master Spacewalk server is working fine
* Proxy server #1 is also fine, proxied clients are ping-able
* Proxy server #2 seems to be working, but clients are not ping-able.
Here's what I've tested on proxy server #2:
* Clients
On 13.3.2012 15:38, Wojtak, Greg (Superfly) wrote:
It does work directly from the spacewalk server.
I probably should have been more clear in my previous email about what I'm
perceiving the problem to be.
The repo name in the URL is having the 'spacewalk' replaced as well. In
this case, the
Ralf,
Thanks for this solution. This fixed my issue with the rhnreg_ks command. I
was able to re-register my machine and download and apply the available updates.
Alan
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of y...@hush.com
Sent:
I thought the same thing at first. Satellite at least would black list
your server for checking in too frequently. The best I could come up with
in this case was to set INTERVAL=60 (the minimum) in /etc/sysconfig/rhnsd.
On 2012-03-13 3:55 PM, Sean Carolan scaro...@gmail.com wrote:
I think
Using the FQDN should be fine in our case. What do I need to go about
changing and how do I change it to the fully qualified name? It seems
like the SSL certs will give headaches if I do this because they are all
signed for the short name (spacewalk server was set up incorrectly from
the
On Tue, Mar 13, 2012 at 3:19 PM, Wojtak, Greg (Superfly)
gregwoj...@quickenloans.com wrote:
I thought the same thing at first. Satellite at least would black list
your server for checking in too frequently. The best I could come up with
in this case was to set INTERVAL=60 (the minimum) in
On 13.3.2012 21:17, Wojtak, Greg (Superfly) wrote:
Using the FQDN should be fine in our case. What do I need to go about
changing and how do I change it to the fully qualified name? It seems
like the SSL certs will give headaches if I do this because they are all
signed for the short name
1) Allow Errata to be updated on the server. The workflow for this is
complex as I think we can only call publish() once for each
errata and it is difficult to tell when we are done with a
particular errata.
A good stopgap approach might be simply to save up all the
publishing
18 matches
Mail list logo
