Anyone have a fix for this? We are running RHEL5.8 and Spacewalk 1.7.
The fix is referenced in the bugzilla. But since you are running
RHEL 5.8, I suggest you open a support ticket with Red Hat to have the
issue properly triaged and addressed.
Thanks, I'll get that submitted today.
I'm seeing an odd result in the Duplicates by IP address list:
1.0.0.1 (2 systems) Compare Systems
host1.domain.com 7/30/12 5:48:47 PM GMT
host2.domain.com 7/30/12 5:49:53 PM GMT
I've tried deleting both of these systems and re-registering them
repeatedly, every time they
I've tried deleting both of these systems and re-registering them
repeatedly, every time they keep coming back with this duplicate IP,
even though 1.0.0.1 is not configured anywhere that I can see.
/sbin/ifconfig doesn't show this ip address, nor can I find it in the
I'm digging up this old thread to ask - is the jabber bug where osad
can't communicate through a proxy server fixed in Spacewalk 1.7? In
other words, if I upgrade both the master spacewalk server and all
proxies to 1.7 do you think it will work?
Just one final question on this; do you know if
On Fri, Jun 15, 2012 at 7:51 AM, Wojtak, Greg (Superfly)
gregwoj...@quickenloans.com wrote:
I can offer some encouragement at least and say that I have been running
Spacewalk in a VM since 0.6. The only thing I'd say is to make sure the
VM is sized appropriately.
Thanks, guys. All helpful
We are planning to move our spacewalk installation from a physical
server onto a VMware guest. The primary reasons for doing this are
portability and snapshots.
Has anyone else moved a Spacewalk installation from one server to
another? Any gotchas or things to look out for? Also if you have
I had a little trepidation at doing the migration, but I followed the
steps closely, made sure I had backups and dumps of the database, and it
went very smoothly.
Thank you. This was the confirmation I was looking for.
___
Spacewalk-list mailing
Has anyone attempted this? When we first installed Spacewalk the
postgres support was not stable so we went with Oracle XE instead, but
the situation seems to have improved.
Might there be a migration script or other process for migrating from
Oracle XE to PostgreSQL?
thanks
Sean
That one is 2 years old release. The bug was fixed one year ago. The
trouble is that release was not made for those 2 years.
Ok, so in other words we probably need to apply the patch, unless
maybe someone at Red Hat already has a patched version?
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.
Thanks, Greg. We'll use this workaround until the jabber bug is fixed.
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
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 Thu, Feb 16, 2012 at 6:47 PM, Jeremy Davis jdavis4...@gmail.com wrote:
Yes, that is the correct cert. You also need to make sure you download that
cert to the client and change the /etc/sysconfig/rhn/osad.conf to point to
that downloaded cert from the proxy server.
Ok, so here are the
-TRUSTED-SSL-CERT
On 02/17/2012 09:18 AM, Sean Carolan wrote:
On Thu, Feb 16, 2012 at 6:47 PM, Jeremy Davisjdavis4...@gmail.com
wrote:
Yes, that is the correct cert. You also need to make sure you download
that
cert to the client and change the /etc/sysconfig/rhn/osad.conf to point
On Thu, Feb 16, 2012 at 4:53 PM, Jeremy Davis jdavis4...@gmail.com wrote:
If a server is connecting to a Spacewalk Proxy server you will need to use
the SSL Cert that was generated for that proxy server. This Cert will be in
the same location as the app server but on the proxy server.
How is
On Fri, Feb 17, 2012 at 2:11 PM, Wojtak, Greg (Superfly)
gregwoj...@quickenloans.com wrote:
server.pem and RHN-ORG-TRUSTED-SSL-CERT are two different things.
server.pem is for jabberd. the CN in server.pem should be your spacewalk
proxy's fqdn. RHN-ORG-TRUSTED-SSL-CERT should be identical to
Maybe one of you have already solved this in the past. We have a
master Spacewalk server which is working just fine. All clients are
able to contact the jabber server and receive push updates, etc. Our
proxy server is registered with the master server and is also working
ok for the most part.
18 matches
Mail list logo
