Re: [Spacewalk-list] syncing SLES15 and SLES15SP1 repos to Spacewalk

[Alan Pittman]

Thanks for the reply and to others that replied earlier. It appears that 
downloading to SMT first is the way to go with this. That is the option that my 
co-worker suggested. I wanted feedback from the list in case there was 
something I wasn't doing correctly.

Alan

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Ethan Bonick
Sent: Thursday, January 16, 2020 2:44 PM
To: spacewalk-list@redhat.com
Cc: Spencer Chan 
Subject: Re: [Spacewalk-list] syncing SLES15 and SLES15SP1 repos to Spacewalk


This email is from an external sender. Don't click links or open attachments 
from unknown sources. Forward suspicious emails as an attachment to 
spam.report...@publix.com<mailto:spam.report...@publix.com>. Protect Yourself. 
Protect Publix. Remain Vigilant.


I have been syncing using SUSE's SMT, now  RMT internally, then syncing from 
those to spacewalk. It seemed like the least amount of headache and I have 
plenty of disk space for another virtual server. Now a few of the SLES 15 
update repos have an issue and SUSE has a fix for their SUSE Manager 
application it does not seemed to have made it to Spacewalk. I've opened a bug 
for that in spacewalk.

https://bugzilla.redhat.com/show_bug.cgi?id=1787614

Ethan

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Alan Pittman
Sent: Thursday, January 16, 2020 7:51 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Cc: Spencer Chan mailto:spencer.c...@publix.com>>
Subject: [Spacewalk-list] syncing SLES15 and SLES15SP1 repos to Spacewalk

Hi,
  Is anyone successfully syncing SLES 15 and SLES 15 SP1 repos from 
updates.suse.com to Spacewalk 2.8 (or 2.9)? If you are, can I compare notes 
with you please? I have been successfully syncing SLES11 and SLES12 repos for 
some time now, but haven't been able to  get a SLES 15 repo to sync. Suse 
support isn't any help. They will only verify the URL and userid/password.

Any help would sure be appreciated.

Alan

Alan Pittman
Publix Super Markets, Inc.
alan.pitt...@publix.com<mailto:alan.pitt...@publix.com>
1-863-686-8754 x46320

Unix is user friendly. It's just very selective about who its friends are.



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] syncing SLES15 and SLES15SP1 repos to Spacewalk

[Alan Pittman]

Hi,
  Is anyone successfully syncing SLES 15 and SLES 15 SP1 repos from 
updates.suse.com to Spacewalk 2.8 (or 2.9)? If you are, can I compare notes 
with you please? I have been successfully syncing SLES11 and SLES12 repos for 
some time now, but haven't been able to  get a SLES 15 repo to sync. Suse 
support isn't any help. They will only verify the URL and userid/password.

Any help would sure be appreciated.

Alan

Alan Pittman
Publix Super Markets, Inc.
alan.pitt...@publix.com
1-863-686-8754 x46320

Unix is user friendly. It's just very selective about who its friends are.



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Upgrading SLES SP3 to SP4

[Alan Pittman]

Daryl,
   Thanks for the in-sight. Looks like I was trying to make this a whole lot 
harder than it needed to be. Got it working without all of the hoops that I was 
trying to jump through.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Daryl Rose
Sent: Tuesday, October 06, 2015 4:11 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4


Alan,



I am far from the expert here on this mailing list.  I had ask the experts on 
this list myself on how to accomplish this task.



What I did was to register a server to SCC, then use that servers credentials 
in the URL of the channel repository.  Actually, registered two servers with 
SCC, one for the SP3 channel, and one for the SP4 channel.



Daryl


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Alan Pittman 
mailto:alan.pitt...@publix.com>>
Sent: Tuesday, October 6, 2015 2:17 PM
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4


Daryl,

  A separate SLES11 topic question for you. How do you sync your SLES11P3  and 
now SP4 channels? I'm downloading SLES11SP3  RPMs to an SMT server and them 
copying them across to my Spacewalk server, running createrepo and finally, 
loading them into the appropriate channel with the spacewalk-repo-sync command. 
I would like to eliminate the SMT server, but not sure how.



Alan



From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Daryl Rose
Sent: Tuesday, October 06, 2015 2:53 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4



Please ignore my last message.  I finally answered my own questions.



I'm not sure why the "test" SLES 11 SP3 severs were showing as being 
up-to-date, but I finally stop/started SW, and they started showing as needing 
updates.



I did an upgrade of one on those test machines from an ISO image.  We decided 
to perform all upgrades via ISO image, and not from SW,  so I wanted to test 
using the method that was agreed on.  After the upgrade was completed, I 
changed the channel to SLES 11 SP4/SLES 11 SP4 Updates.  I issued a "zypper 
ref" to refresh the repositories on the client, and they are now requiring 
updates from the new channels.



Thank you for the help.  It is very much appreciated.



Daryl







From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose mailto:darylr...@outlook.com>>
Sent: Tuesday, October 6, 2015 10:06 AM
To: Robert Paschedag; 
spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4



I have a couple of questions.



1.  The command "zypper dup" say's that it performs a distribution upgrade.  
Are you suggesting that I upgrade this way?

2.  I'm currently testing with a couple of test servers that I have.  I did a 
fresh install of SLES 11 SP3, registered it with my SW server, but it 
registered as "System is up-to-date".



I know this server needs updates.  I can run "zypper lu" and see that it needs 
a number of updates.

Yet, SW still claims that it is up-to-date.  I have a handful of other server, 
SLES 11 SP3, and all registered exactly the same, and all show that they 
require updates.  I can't figure out why these test servers are different.



Thanks.



Daryl







From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Robert Paschedag 
mailto:robert.pasche...@web.de>>
Sent: Tuesday, October 6, 2015 12:14 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Cc: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4



Hi Daryl,

I would just change the channels of the clients from SP3 to SP4 and then run a 
"zypper dup" on the clients.

This is how I upgraded clients from SP2 to SP3.

Regards

Robert



Versendet mit der SolMail-App<http://mail.sol.daum.net?via=mail_sign>

[http://i1.daumcdn.net/mimg/solstudio/resources/facebookLink_studio3.png]<http://mail.sol.daum.net/?via=mail_sign>


SolStudio

We try to shine your life like a gleaming sun with the essential services. Make 
your day even brighter with SolStudio apps.

Read more...<http://mail.sol.daum.net/?via=mail_sign>




- Original Message -
From: Daryl Rose
To: "spacewalk-list@redhat.

Re: [Spacewalk-list] Upgrading SLES SP3 to SP4

[Alan Pittman]

Daryl,
  A separate SLES11 topic question for you. How do you sync your SLES11P3  and 
now SP4 channels? I'm downloading SLES11SP3  RPMs to an SMT server and them 
copying them across to my Spacewalk server, running createrepo and finally, 
loading them into the appropriate channel with the spacewalk-repo-sync command. 
I would like to eliminate the SMT server, but not sure how.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Daryl Rose
Sent: Tuesday, October 06, 2015 2:53 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4


Please ignore my last message.  I finally answered my own questions.



I'm not sure why the "test" SLES 11 SP3 severs were showing as being 
up-to-date, but I finally stop/started SW, and they started showing as needing 
updates.



I did an upgrade of one on those test machines from an ISO image.  We decided 
to perform all upgrades via ISO image, and not from SW,  so I wanted to test 
using the method that was agreed on.  After the upgrade was completed, I 
changed the channel to SLES 11 SP4/SLES 11 SP4 Updates.  I issued a "zypper 
ref" to refresh the repositories on the client, and they are now requiring 
updates from the new channels.



Thank you for the help.  It is very much appreciated.



Daryl




From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose mailto:darylr...@outlook.com>>
Sent: Tuesday, October 6, 2015 10:06 AM
To: Robert Paschedag; 
spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4


I have a couple of questions.



1.  The command "zypper dup" say's that it performs a distribution upgrade.  
Are you suggesting that I upgrade this way?

2.  I'm currently testing with a couple of test servers that I have.  I did a 
fresh install of SLES 11 SP3, registered it with my SW server, but it 
registered as "System is up-to-date".



I know this server needs updates.  I can run "zypper lu" and see that it needs 
a number of updates.
Yet, SW still claims that it is up-to-date.  I have a handful of other server, 
SLES 11 SP3, and all registered exactly the same, and all show that they 
require updates.  I can't figure out why these test servers are different.

Thanks.

Daryl



From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Robert Paschedag 
mailto:robert.pasche...@web.de>>
Sent: Tuesday, October 6, 2015 12:14 AM
To: spacewalk-list@redhat.com
Cc: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4


Hi Daryl,

I would just change the channels of the clients from SP3 to SP4 and then run a 
"zypper dup" on the clients.

This is how I upgraded clients from SP2 to SP3.

Regards

Robert




Versendet mit der SolMail-App
[http://i1.daumcdn.net/mimg/solstudio/resources/facebookLink_studio3.png]

SolStudio
We try to shine your life like a gleaming sun with the essential services. Make 
your day even brighter with SolStudio apps.
Read more...



- Original Message -
From: Daryl Rose
To: "spacewalk-list@redhat.com"
Date: Mon Oct 05 22:46:47 MESZ 2015
Subject: [Spacewalk-list] Upgrading SLES SP3 to SP4

How is the best way to change a SW repository?



We are in the process of upgrading our SLES servers to SP4.  I registered a few 
of the SP3 machines to the SW server.  I took one of those registered SP3 
machines, deleted it from SW, upgraded it to SP4, then attempted to re-register 
using the SP4 activation key.  That didn't work so well.  I had to completely 
clean out all of the rhn and spacewalk packages from the client, re-install 
from the spacewalk repository.  I basically had to go back through all of the 
steps in registering a server to get it to register to the SP4 repositories.



Is there an easier way to change the repository?



Thanks



Daryl
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] your satellite certificate has expired.

[Alan Pittman]

I am running 2.0 and this is what I did:

Got the new cert from here:
https://raw.githubusercontent.com/spacewalkproject/spacewalk/master/branding/setup/spacewalk-public.cert

And put it here:
/usr/share/spacewalk/setup/new-spacewalk-public.cert

Then I ran this command:
rhn-satellite-activate --rhn-cert 
/usr/share/spacewalk/setup/new-spacewalk-public.cert --disconnected

Now the cert message is gone and everything looks normal again.

Alan

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Cliff Perry
Sent: Monday, July 13, 2015 11:38 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] your satellite certificate has expired.

On 13/07/15 16:31, Nicki Clear wrote:
>
> I am running spacewalk 2.0 and the certificate that I am using just expired
> today.
>
> 
> 
>SPACEWALK-001
>Spacewalk Default
> Organization
>2007-07-13 00:00:00
>2015-07-13 00:00:00
>2
>2
>2
>2
> name="virtualization_host_platform">2
>spacewalk
>2
>
> -BEGIN PGP SIGNATURE-
> Version: Crypt::OpenPGP 1.03
>
> iQBGBAARAwAGBQJLqMhgAAoJEJ5yna8GlHkyrL4AoIrXT8ITy6MwGyOr5ev5LsmL
> ZAN9AKCOZ6vxkuSIl1ld5Mu7Hvwz8bgn2g==
> =OoMc
> -END PGP SIGNATURE-
> 
> 
>
> I was following this
> https://www.redhat.com/archives/spacewalk-list/2010-July/msg00042.html
>
> but it just points to the same cert.
>
> Is there another way to get a new satellite certificate?
>
> Thanks,
> Nicki
>
> **
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed. If 
> you have received this email in error please notify the system manager.
>
> This footnote also confirms that this email message has been scanned by 
> Proofpoint PPS and F-Secure for the presence of computer viruses.
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>

Hi please see the contents of this email, which provided link to 
download the new certificate to use:

 Forwarded Message 
Subject: [Spacewalk-devel] Spacewalk certificate expiry
Date: Mon, 13 Jul 2015 16:27:06 +0200
From: Tomáš Kašpárek 
Reply-To: spacewalk-de...@redhat.com
To: spacewalk-list@redhat.com, spacewalk-de...@redhat.com

Hello,

as may of you noticed old Spacewalk certificate is about to expire. If
you're experiencing this, please follow instructions which can be found
on
https://fedorahosted.org/spacewalk/wiki/HowToUpgrade#PerformSpacewalkactivation
(assuming you're running Spacewalk 2.2 and newer, if you're running
older Spacewalk, grab new certificate manually at
https://raw.githubusercontent.com/spacewalkproject/spacewalk/master/branding/setup/spacewalk-public.cert
and proceed with activation).

Best regards,
Tomáš Kašpárek



Regards,
Cliff


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

[Alan Pittman]

Thanks for the replies, but neither suggestion helped. I got it to work with a 
wild shot in the dark. What I did was to  delete the 
/var/cache/rhn/repodata/ sub-directories on the spacewalk server and 
force the Spacewalk application to repopulate them. Exactly what forces the 
re-population, I don’t know, but if I run a yum makecache on the client, it 
initially fails because there isn’t anything in the 
/var/cache/rhn/repodata/ directory. Something triggers Spacewalk to 
rebuild/reload the directory and then the makecache command works for that 
channel. I have to run the makecache multiple times to force all of the data 
for all of the channels to be re-populated.

How the data in the /var/cache/rhn/repodata/ directory got “stale”, I 
don’t know, but at least it’s working now.

Hopefully this makes some sense and is helpful for someone else.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Kobus Bensch
Sent: Tuesday, March 31, 2015 4:42 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI 
reports that there are

I had this issue. I fixed it by running a repo sync manually.
On 31/03/2015 05:21, prmari...@gmail.com<mailto:prmari...@gmail.com> wrote:
Try running rhn-profile-sync on the box in question then looking in the GUI 
again. This can happen if some one does a manual update in yum and does not run 
that command afterward.
Its well documented in the install procedure for every red hat errata‎ that you 
have to run that command after a yum update. You may also want to consider 
adding cron.daily job to do this with anacron that should execute it every day 
at a semi randomized time so you won't over laod your spacewalk server and the 
added load to the host while running it is negligible so it should not impact 
the performance of the applications you are running unless the box is already 
severly overloaded to begin with.


Sent from my BlackBerry 10 smartphone.
From: Alan Pittman
Sent: Monday, March 30, 2015 14:07
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Reply To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI 
reports that there are


Hi,
  I'm having an issue with Spacewalk 2.0. I have two RHEL6 x86_64 servers that 
the Spacewalk GUI reports that there are available updates. However, if I run 
yum on these two machines, nothing is reported as being available for updating. 
I've done some Google searches and this has been an issue in the past for some 
individuals and occasionally the problem has been fixed by running yum clean 
all, followed by deleting the /var/cache/yum directory. Then a yum makecache. . 
I tried this and it didn't helped. I have also tried deleting the profile for 
the server and attempting a re-register. That didn't work either.  If anyone 
has any ideas/suggestions, I would like to hear them.

   Some other information that might be beneficial (I think):

   - All updates have been performed using yum. No rpm --install or --upgrade 
has been performed.
   - Since I had deleted and re-registered the client, I didn't think 
rhn-profile-sync would do any good, but I tried it anyhow. It didn't help.
   - a complete shutdown of the Spacewalk server application and it's 
corresponding postgres database was also attempted, again to avail.
   - attempting to update the client from the Spacewalk GUI does not work. The 
schedule task just goes into a pending state and never occurs.

Any suggestions would be appreciated.

Alan

Unix is user friendly. It’s just very selective about who its friends are.











___

Spacewalk-list mailing list

Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>

https://www.redhat.com/mailman/listinfo/spacewalk-list

--
Kobus Bensch
Senior Systems Administrator
Address:  22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD
DDI:  0207 871 3958
Tel:  0207 871 3890
Email:  kobus.ben...@trustpayglobal.com<mailto:kobus.ben...@trustpayglobal.com>
[cid:image001.png@01D06B91.48573890]


Trustpay Global Limited is an authorised Electronic Money Institution regulated 
by the Financial Conduct Authority registration number 900043. Company No 
07427913 Registered in England and Wales with registered address 130 Wood 
Street, London, EC2V 6DL, United Kingdom.

For further details please visit our website at 
www.trustpayglobal.com<http://www.trustpayglobal.com>.

The information in this email and any attachments are confidential and remain 
the property of Trustpay Global Ltd unless agreed by contract. It is intended 
solely for the person to whom or the entity to which it is addressed. If you 
are not the intended recipient you may not use, disclose, copy, distribute, 
print or rely on the content of

[Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

[Alan Pittman]

Hi,
  I'm having an issue with Spacewalk 2.0. I have two RHEL6 x86_64 servers that 
the Spacewalk GUI reports that there are available updates. However, if I run 
yum on these two machines, nothing is reported as being available for updating. 
I've done some Google searches and this has been an issue in the past for some 
individuals and occasionally the problem has been fixed by running yum clean 
all, followed by deleting the /var/cache/yum directory. Then a yum makecache. . 
I tried this and it didn't helped. I have also tried deleting the profile for 
the server and attempting a re-register. That didn't work either.  If anyone 
has any ideas/suggestions, I would like to hear them.

   Some other information that might be beneficial (I think):

   - All updates have been performed using yum. No rpm --install or --upgrade 
has been performed.
   - Since I had deleted and re-registered the client, I didn't think 
rhn-profile-sync would do any good, but I tried it anyhow. It didn't help.
   - a complete shutdown of the Spacewalk server application and it's 
corresponding postgres database was also attempted, again to avail.
   - attempting to update the client from the Spacewalk GUI does not work. The 
schedule task just goes into a pending state and never occurs.

Any suggestions would be appreciated.

Alan

Unix is user friendly. It’s just very selective about who its friends are.





___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] corrupt spacewalk database???

[Alan Pittman]

Hi,
   I am trying to create a kickstart profile. When I complete filling out the 
fields on the profile wizard (on the last screen is the root password), then 
click the finish button, , the screen goes blank and nothing happens. If I look 
in today's postgres log file, I see the following messages:

STATEMENT:  select 'c3p0 ping' from dual
ERROR:  could not read block 0 of relation base/16384/94689: read only 0 of 
8192 bytes
STATEMENT:  insert into RHNKSDATA (org_id, label, comments, active, postLog, 
preLog, kscfg, is_org_default, kernel_params, nonchrootpost, no_base, 
ignore_missing, verboseup2date, partition_data, cobbler_id, update_type, 
ks_type, id) values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, 
$14, $15, $16, 'wizard', $17)
ERROR:  current transaction is aborted, commands ignored until end of 
transaction block


I'm speculating that I have a corrupt database. Can someone confirm? I'm not a 
DBA. 

Thanks,
Alan


Alan Pittman
Publix Super Markets, Inc.
alan.pitt...@publix.com
1-863-686-8754 x46320

Unix is user friendly. It’s very selective about who its friends are.




___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Attempting to create a KVM using kickstart via Spacewalk

[Alan Pittman]

Hi,
 Hopefully everyone had a good holiday. I'm not expecting any replies until 
after the first of the year. :)

 I am trying to set up a Spacewalk kickstart build of a KVM guest and I'm not 
getting verify far. Not knowing what the problem is prevents me from doing a 
successful Google search to find any answers, so I am hoping someone on the 
list can help.

I am using the Quick Start Guide for Spacewalk (kickstart) found on the wiki 
page and referenced the Satellite 5.5 Reference Guide.

I successfully created a kickstart channel and profile and I am trying the use 
koan as suggested towards the end of the instructions. The problem is that once 
koan starts and begins the domain creation,  it disconnects and tells me that I 
have to reconnect to the console. Here's the output:

Starting install...
Retrieving file .treeinfo... | 3.3 kB 00:00 ...
Retrieving file vmlinuz...   | 7.2 MB 00:00 ...
Retrieving file initrd.img...|  57 MB 00:00 ...
Creating domain...   |0 B 00:00
Domain installation still in progress. You can reconnect to
the console to complete the installation process.

So I do reconnect:

[root@srhelvs21 ~]# virsh console sccrxa21-vm
Connected to domain sccrxa21-vm
Escape character is ^]

But then nothing happens. The session is locked. I can't get a response if I 
hit enter or any of the keys. I can't even break out at this point. 

So at this point I'm stuck. I have no idea what's going on, so I don't know if 
I have any configuration issues or what.

In case someone is interested, here's my complete koan script:
#!/bin/bash

/usr/bin/koan --server=pspwks20.publix.com  \
 --virt \
 --virt-name sccrxa23-vm \
 --virt-path /kvm/sccrxa23 \
 --profile=rhel6-64bit-ccrx-ks-profile:1:SpacewalkDefaultOrganization \
 --nogfx

And here is the output that koan generates before it begins the build process:

- looking for Cobbler at http://pspwks20.publix.com:80/cobbler_api
- reading URL: 
http://pspwks20.publix.com/cblr/svc/op/ks/profile/rhel6-64bit-ccrx-ks-profile:1:SpacewalkDefaultOrganization
install_tree: http://pspwks20.publix.com/ks/dist/ccrx-kvm-guest
- ['rpm', '-q', 'virt-install']
- ['rpm', '-q', 'python-virtinst']
libvirtd (pid  5605) is running...
- ['virt-install', '--version']
- ['qemu-img', 'create', '-f', 'raw', '/kvm/sccrxa23/sccrxa23-vm-disk0', '3G']
Formatting '/kvm/sccrxa23/sccrxa23-vm-disk0', fmt=raw size=3221225472
- adding disk: /kvm/sccrxa23/sccrxa23-vm-disk0 of size 3 (driver type=raw)
- ['virt-install', '--connect', 'qemu:///system', '--name', 'sccrxa23-vm', 
'--ram', '512',
 '--vcpus', '1', '--autostart', '--nographics', '--virt-type', 'qemu', 
'--machine', 'pc', '--hvm', 
'--extra-args=ksdevice=link lang= console=ttyS0,115200 text 
ks=http://pspwks20.publix.com/cblr/svc/op/ks/profile/rhel6-64bit-ccrx-ks-profile:1:SpacewalkDefaultOrganization
 serial kssendmac ', 
'--location', 'http://pspwks20.publix.com/ks/dist/ccrx-kvm-guest/',
 '--arch', 'i386', '--os-variant', 'generic26', '--disk', 
'path=/kvm/sccrxa23/sccrxa23-vm-disk0,size=3,format=raw',
 '--network', 'bridge=br0', '--wait', '0', '--noautoconsole']

There are a few things I would like to change, but I can't figure out where to 
make the changes. These options are:
'--arch', 'i386',  - this should be x86_64
 '--os-variant', 'generic26' - this should be rhel6

Any help in pointing me in the right direction would be appreciated.

Alan

Remember, Unix is user friendly. It’s very selective about who its friends are. 





___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Thanks first, for answering all my questions

[Alan Pittman]

Hi,
  Everyone has their own personal preferences, I personally like to set up a 
script, like this:

#!/bin/bash

/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-elrepo --type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-rhn-tools --type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-supplementary --type 
yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-updates --type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-mondo --type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-epel --type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-spacewalk-client 
--type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-fastrack --type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-productivity --type 
yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-vt --type yum
/usr/bin/spacewalk-repo-sync --channel rhel-64bit-server-5-rhev-agent --type yum

And then use crontab to schedule it:

33 03 6,13,20,27 * * /usr/local/bin/sync-5Server-64.sh

Hope this helps a little.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Alexander Dacre
Sent: Monday, October 06, 2014 12:49 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Thanks first, for answering all my questions

Hi,

You can do this via the web interface or spacewalk-repo-sync found in 
spacewalk-utils.

Thanks,

Alex Dacre
Systems Engineer
+44 131 560 1466

From: 
spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Kartik Vashishta
Sent: 06 October 2014 17:47
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Thanks first, for answering all my questions

Next question: How do I schedule all repos to be sync'd?

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] RHEL6 - Spacewalk - MREPO

[Alan Pittman]

Hi,
  I am currently running mrepo three separate RHEL6 x86_64 servers:

mrepo-0.8.8-2.of.el6.noarch

It's been a few years, but I believe I got it from sourceforge.

I use it to download all of the updates (RHEL5 and RHEL6) for my spacewalk 
servers.

I have a copy of the rpm if you would like me to send it to you.

Alan

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Glen Collins
Sent: Tuesday, September 30, 2014 2:58 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] RHEL6 - Spacewalk - MREPO

Hello all.

   I'm running into an issue of using mrepo so I can sync repos' If I install 
mrepo 0.8.7-2.el6 from from the EPEL I get issues running gensystemid:

[root@xxx mrepo-master]# gensystemid -u rhnuser -p rhnpassword -r 6Server 
/var/mrepo/rhel6s-x86_64/
/usr/share/mrepo/up2date_client/up2dateUtils.py:16: DeprecationWarning: the md5 
module is deprecated; use hashlib instead
  import md5
gensystemid: Architecture not supplied, using system architecture x86_64
gensystemid: Release name 6Server is not a known RHN release.
[root@xx mrepo-master]# gensystemid -u rhnuser -p rhnpassword -r 5Server 
/var/mrepo/rhel6s-x86_64/
/usr/share/mrepo/up2date_client/up2dateUtils.py:16: DeprecationWarning: the md5 
module is deprecated; use hashlib instead
  import md5
gensystemid: Architecture not supplied, using system architecture x86_64
Traceback (most recent call last):
  File "/usr/bin/gensystemid", line 270, in 
main()
  File "/usr/bin/gensystemid", line 237, in main
except rpclib.Fault, f:
AttributeError: 'module' object has no attribute 'Fault'

So does anyone know if there is a good update to mrepo for RHEL6? I have also 
tried the GIT version of MREPO and the version from another source using 
mrepo-0.8.8-0.pre1.el6.rft.noarch.rpm and installing 
rhpl-0.221-2.el6.rf.x86_64.rpm. Still no luck any way. I know this is an issue 
with Redhat removing support for RHPL and changes to the underlying 
infrastructure in RHEL6. So if anyone has found a solution to using mrepo with 
RHEL 6.5, can you please post links or whatever you may have?

Thanks!

Glen Collins

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] 500 Error - Internal Server Error when attempting to clone a channel

[Alan Pittman]

More on this issue...

The interesting thing is that if I copy the info from the clone channel link 
and then edit it to look like this:

https://pspwks10/network/software/channels/manage/clone.pxt, then enter this in 
the browser's  URL field, it works, after re-signing on.

In addition, using spacecmd softwarechannel_clone also works. 

There's just an issue with the GUI when you try and click on the clone channel 
link from this location: https:///rhn/channels/manage/Manage.do

Alan

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Alan Pittman
Sent: Thursday, July 31, 2014 8:09 AM
To: 'spacewalk-list@redhat.com'
Cc: Chris Bishop
Subject: [Spacewalk-list] 500 Error - Internal Server Error when attempting to 
clone a channel


Hi all,
  I need some assistance. I'm trying to clone a channel and I'm getting the 
standard "500 Error - Internal Server Error" message on the GUI. Could someone 
tell me what log files I need to look at to determine what's going on? So far, 
I can't seem to find anything that is of any value.

FYI - I'm running Spacewalk 1.9

Alan


Alan Pittman
Publix Super Markets, Inc.
alan.pitt...@publix.com
1-863-686-8754 x46320

Unix is user friendly. It's very selective about who its friends are.



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] 500 Error - Internal Server Error when attempting to clone a channel

[Alan Pittman]

Hi all,
  I need some assistance. I'm trying to clone a channel and I'm getting the 
standard "500 Error - Internal Server Error" message on the GUI. Could someone 
tell me what log files I need to look at to determine what's going on? So far, 
I can't seem to find anything that is of any value.

FYI - I'm running Spacewalk 1.9

Alan


Alan Pittman
Publix Super Markets, Inc.
alan.pitt...@publix.com
1-863-686-8754 x46320

Unix is user friendly. It's very selective about who its friends are.



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] [BULK] Re: Incorrect timezone in new 2.1 date / time picker.

[Alan Pittman]

Just an FYI (for anyone that cares) -
   "There's only one other GMT-0500 timezone choice available (Indiana), where 
they don't observe DST" - actually, yes they do. They (the state of Indiana) 
adopted DST in 2005 and implemented it in 2006.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Duncan Mac-Vicar P.
Sent: Friday, March 28, 2014 12:17 PM
To: Ron Helzer
Cc: spacewalk-list@redhat.com; spacewalk-devel
Subject: [BULK] Re: [Spacewalk-list] Incorrect timezone in new 2.1 date / time 
picker.
Importance: Low

On 28/03/14 17:05, Ron Helzer wrote:
There's only one other GMT-0500 timezone choice available (Indiana), where they 
don't observe DST... That, in conjunction with the fact that there were no DST 
issues pre-2.1, would suggest to me that the GMT-0500 (Eastern) setting should 
account for EDT/EST change.

Are you suggesting I'm supposed to change the preference twice a year to 
manually account for DST?

No, I am just trying to understand where the issue can come from, as I don't 
think anything changed at all.

In 2.0 the date picker fragment got the timezone from the DatePicker bean 
(picker.calendar.timeZone)
https://github.com/spacewalkproject/spacewalk/blob/SPACEWALK-2.0/java/code/webapp/WEB-INF/pages/common/fragments/date-picker.jsp
 (line 60)

In 2.1, the JSP tag gets the timezone from the DatePicker bean in the same way
https://github.com/spacewalkproject/spacewalk/blob/SPACEWALK-2.1/java/code/src/com/redhat/rhn/frontend/taglibs/DateTimePickerTag.java
 (line 225)

Then the time passed to the server on submit does not carry the timezone, so it 
is always relative to the one it was shown to you.
(I am not saying there is not a problem, but I can't see how it would be new if 
there is).

CCing -devel in case anyone sees something I am missing.


--

Duncan Mac-Vicar P. - http://www.suse.com/



SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 
16746 (AG Nürnberg)

Maxfeldstraße 5, 90409 Nürnberg, Germany


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Test apache page works but how can I get my Spacewalk login page to work

[Alan Pittman]

When I installed spacewalk, I used yum and selected this package for 
installation:

# yum install spacewalk-postgresql

Yum, in turn, thru dependencies, installed all of the packages listed below, 
plus others that are not listed. Even though I'm only up to version 1.9, the 
list of packages should be similar.

[root@taeps001 ~]# rpm -q -a | grep space
spacewalk-postgresql-1.9.2-1.el6.noarch
spacewalk-search-1.9.5-1.el6.noarch
spacewalk-backend-config-files-tool-1.9.49-1.el6.noarch
spacewalk-jpp-workaround-1.0.4-1.el6.noarch
spacewalk-admin-1.9.10-1.el6.noarch
spacewalk-backend-xmlrpc-1.9.49-1.el6.noarch
spacewalk-pxt-1.9.22-1.el6.noarch
spacewalk-schema-1.9.38-1.el6.noarch
spacecmd-1.9.4-1.el6.noarch
spacewalk-monitoring-selinux-1.9.1-1.el6.noarch
spacewalk-grail-1.9.22-1.el6.noarch
spacewalk-backend-libs-1.9.49-1.el6.noarch
spacewalk-backend-tools-1.9.49-1.el6.noarch
spacewalk-remote-utils-2.0.1-1.el6sat.noarch
spacewalk-backend-sql-postgresql-1.9.49-1.el6.noarch
spacewalk-setup-jabberd-1.9.1-1.el6.noarch
spacewalk-backend-server-1.9.49-1.el6.noarch
spacewalk-selinux-1.9.1-1.el6.noarch
spacewalk-backend-iss-1.9.49-1.el6.noarch
spacewalk-repo-1.9-1.el6.noarch
spacewalk-base-1.9.22-1.el6.noarch
spacewalk-config-1.9.8-1.el6.noarch
spacewalk-java-lib-1.9.84-1.el6.noarch
spacewalk-slf4j-1.6.1-6.el6.noarch
spacewalk-backend-sql-1.9.49-1.el6.noarch
spacewalk-setup-1.9.6-1.el6.noarch
spacewalk-backend-package-push-server-1.9.49-1.el6.noarch
spacewalk-doc-indexes-1.1.1-1.el6.noarch
spacewalk-taskomatic-1.9.84-1.el6.noarch
spacewalk-backend-config-files-common-1.9.49-1.el6.noarch
spacewalk-backend-config-files-1.9.49-1.el6.noarch
spacewalk-java-1.9.84-1.el6.noarch
spacewalk-certs-tools-2.0.1-2.el6sat.noarch
spacewalk-java-postgresql-1.9.84-1.el6.noarch
spacewalk-html-1.9.22-1.el6.noarch
spacewalk-backend-xml-export-libs-1.9.49-1.el6.noarch
spacewalk-base-minimal-1.9.22-1.el6.noarch
spacewalk-sniglets-1.9.22-1.el6.noarch
spacewalk-backend-app-1.9.49-1.el6.noarch
spacewalk-java-config-1.9.84-1.el6.noarch
spacewalk-backend-iss-export-1.9.49-1.el6.noarch
spacewalk-common-1.9.2-1.el6.noarch
spacewalk-branding-1.9.6-1.el6.noarch
spacewalk-monitoring-1.9.5-1.el6.noarch
spacewalk-backend-1.9.49-1.el6.noarch
spacewalk-backend-applet-1.9.49-1.el6.noarch

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of J.W. slone
Sent: Wednesday, October 30, 2013 9:47 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Test apache page works but how can I get my Spacewalk 
login page to work

1. nslookup works with my IP address
2.spacewalk-service  restart works without errors
3. /usr/sbin only has
A) spacewalk-service
B)spacewalk-start-helper
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] How do you start spcewalk from the commandline

[Alan Pittman]

The following spacewalk command are located in /usr/sbin:

[root@taeps001 tmp]# cd /usr/sbin
[root@taeps001 sbin]# ll space*
-rwxr-xr-x 1 root root 7129 Feb 26  2013 spacewalk-channel
-rwxr-xr-x 1 root root  537 Jan  4  2013 spacewalk-monitoring-selinux-enable
-rwxr-xr-x 1 root root 1549 Feb 12  2013 spacewalk-selinux-enable
-rwxr-xr-x 1 root root 4364 Feb 27  2013 spacewalk-service
-rwxr-xr-x 1 root root 1300 Feb 27  2013 spacewalk-startup-helper

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of J.W. slone
Sent: Wednesday, October 30, 2013 11:55 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] How do you start spcewalk from the commandline

now I get command not found error when I run the command
spacewalk-service start

On Wednesday, October 30, 2013 8:27 AM, Milan Zazrivec 
mailto:mzazri...@redhat.com>> wrote:
> I do not recall how to start spacewalk from the commandline

spacewalk-service start | stop | restart  ...

-MZ


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] How do you start spcewalk from the commandline

[Alan Pittman]

Try this: spacewalk-service start

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of J.W. slone
Sent: Wednesday, October 30, 2013 10:04 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] How do you start spcewalk from the commandline

I do not recall how to start spacewalk from the commandline
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Software Channels

[Alan Pittman]

I did create channel names, but they didn’t copy and paste from my Spacewalk 
GUI.

Parent channel name:   centos-x86_64-server-5
Child channel name:   centos-x86_64-server-5-updates

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Alan Pittman
Sent: Monday, October 21, 2013 12:04 PM
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Software Channels

Jens,
  Here’s how I set up my CentOS x86_64 channel:

I created a parent channel first:
Channel Name*:

Channel Label*:

centos-64bit-server-5

Parent Channel:

None


The I created a child channel:

Channel Name*:

Channel Label*:

centos-64bit-server-5-updates

Parent Channel:

centos-x86_64-server-5

Architecture:

x86_64


Then created a repository for the child channel:

Repository Label*

Repository URL*


Label:  centos-64bit-server-5-updates-repo
URL: http://mirror.centos.org/centos/5/updates/x86_64/

Then back in the child channel, I selected the repository link and click on the 
box for the repo to connect the repo to the channel.

Hopefully this helps.

Alan


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jens Neu
Sent: Monday, October 21, 2013 11:47 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Software Channels


> I have installed SPW 2.0 on Centos 6.4 64bit.
>
> I have created my first Software Channel with repository, but when I
> update the Repo, instead of the packages going in to the channel, it
> is being listed as Packages in no channels.
>

> Surely it should be listed in the centos-6-x86_64-base channel.
>
> Can anybody help please?

I would say you did not link the channel to the repo correctly.
Maybe you should just delete everything and have a look at

spacewalk-common-channels

-> /usr/bin/spacewalk-common-channels -u admin -p pass -a x86_64 'centos6*'

regards
Jens

www.biotronik.com<http://www.biotronik.com>


[Image removed by sender.]

BIOTRONIK - Celebrating 50 years of excellence

Founded in 1963 with the development of the first German pacemaker, BIOTRONIK 
has brought innovations and the highest quality standards to the cardiac rhythm 
management and vascular intervention fields in more than 100 countries around 
the world. We’ve developed advanced technologies such as BIOTRONIK Home 
Monitoring®, Closed Loop Stimulation (CLS) and Orsiro, the industry's first 
hybrid drug eluting stent. BIOTRONIK also offers the broadest portfolio of 
cardiac devices with ProMRI®, an advanced technology that gives patients access 
to magnetic resonance (MR) scanning.

BIOTRONIK SE & Co. KG
Woermannkehre 1, 12359 Berlin, Germany
Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501

Vertreten durch ihre Komplementärin:
BIOTRONIK MT SE
Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 118866 B
Geschäftsführende Direktoren: Christoph Böhmer, Dr. Lothar Krings

This e-mail and the information it contains including attachments are 
confidential and meant only for use by the intended recipient(s); disclosure or 
copying is strictly prohibited. If you are not addressed, but in the possession 
of this e-mail, please notify the sender immediately and delete the document.
<>___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Software Channels

[Alan Pittman]

Jens,
  Here’s how I set up my CentOS x86_64 channel:

I created a parent channel first:
Channel Name*:


Channel Label*:

centos-64bit-server-5

Parent Channel:

None


The I created a child channel:

Channel Name*:


Channel Label*:

centos-64bit-server-5-updates

Parent Channel:

centos-x86_64-server-5

Architecture:

x86_64


Then created a repository for the child channel:

Repository Label*


Repository URL*



Label:  centos-64bit-server-5-updates-repo
URL: http://mirror.centos.org/centos/5/updates/x86_64/

Then back in the child channel, I selected the repository link and click on the 
box for the repo to connect the repo to the channel.

Hopefully this helps.

Alan


From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jens Neu
Sent: Monday, October 21, 2013 11:47 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Software Channels


> I have installed SPW 2.0 on Centos 6.4 64bit.
>
> I have created my first Software Channel with repository, but when I
> update the Repo, instead of the packages going in to the channel, it
> is being listed as Packages in no channels.
>

> Surely it should be listed in the centos-6-x86_64-base channel.
>
> Can anybody help please?

I would say you did not link the channel to the repo correctly.
Maybe you should just delete everything and have a look at

spacewalk-common-channels

-> /usr/bin/spacewalk-common-channels -u admin -p pass -a x86_64 'centos6*'

regards
Jens

www.biotronik.com


[Image removed by sender.]

BIOTRONIK - Celebrating 50 years of excellence

Founded in 1963 with the development of the first German pacemaker, BIOTRONIK 
has brought innovations and the highest quality standards to the cardiac rhythm 
management and vascular intervention fields in more than 100 countries around 
the world. We’ve developed advanced technologies such as BIOTRONIK Home 
Monitoring®, Closed Loop Stimulation (CLS) and Orsiro, the industry's first 
hybrid drug eluting stent. BIOTRONIK also offers the broadest portfolio of 
cardiac devices with ProMRI®, an advanced technology that gives patients access 
to magnetic resonance (MR) scanning.

BIOTRONIK SE & Co. KG
Woermannkehre 1, 12359 Berlin, Germany
Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501

Vertreten durch ihre Komplementärin:
BIOTRONIK MT SE
Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 118866 B
Geschäftsführende Direktoren: Christoph Böhmer, Dr. Lothar Krings

This e-mail and the information it contains including attachments are 
confidential and meant only for use by the intended recipient(s); disclosure or 
copying is strictly prohibited. If you are not addressed, but in the possession 
of this e-mail, please notify the sender immediately and delete the document.
<>___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Swalk 2.0 rhnreg_ks = "No module named hardware_hal"

[Alan Pittman]

Lee,
   I think this has been asked. Are you running the 32bit or 64bit version of 
CentOS 6.4?

I've got a RHEL 6.4 running 64bit and its registered with my Spacewalk server. 
The hitch may be that I'm still at Spacewalk 1.8. Just migrated there from 1.7 
about a month ago.

My server has this version:

[root@l47rhelt2 ~]# rpm -q -a | grep pygobj
pygobject2-2.20.0-5.el6.x86_64
[root@l47rhelt2 ~]#

This error shows up on the Red Hat support site. The suggested fix is:

Resolution

Download appropriate version of package 'pygobject2' from RHN and install it.

Root Cause

If rhn-client-tools dependent package 'pygobject2' is missing, you get this 
error

Sorry if this isn't much help, but I thought I would let you know that Red Hat 
Support has seen this issue before.

Alan


-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Dimitri Yioulos
Sent: Tuesday, August 06, 2013 4:12 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Swalk 2.0 rhnreg_ks = "No module named 
hardware_hal"

Afaik, there is no hardware_hal package.  There is a hal 
package, though, and I believe it's installed by default, 
though the OP might wan to check.  Then, of course, it's 
worth making sure that python is installed.

Dimitri


On Tuesday 06 August 2013 3:41:59 pm Thomas Foster wrote:
> That's a python error it looks likesee if you have
> hardware_hal installed..
>
> On Tue, Aug 6, 2013 at 2:50 PM, Lee Roth 
 wrote:
> > Spacewalk V2.0 on Centos6.4
> >
> > Trying to register a Centos6.4 client to the Spacewalk
> > server; the command rhnreg_ks does not work.
> >
> > A suggestion that I read somewhere that the package
> > "pygobject2" might be missing, but it is not.
> >
> > On the client:
> >
> > # /usr/sbin/rhnreg_ks --help
> > Traceback (most recent call last):
> >   File "/usr/sbin/rhnreg_ks", line 33, in 
> > from up2date_client import rhnreg
> >   File "/usr/share/rhn/up2date_client/rhnreg.py", line
> > 21, in  import hardware
> >   File "/usr/share/rhn/up2date_client/hardware.py",
> > line 45, in  from hardware_hal import
> > check_hal_dbus_status, get_hal_computer, read_hal
> > ImportError: No module named hardware_hal
> > # rpm -qa | grep pygobject2
> > pygobject2-2.20.0-5.el6.i686
> > #
> >
> > Any suggestion?
> >
> > Thanks!
> >
> > Lee
> >
> >
> >
> > ___
> > Spacewalk-list mailing list
> > Spacewalk-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] ya-errata-import: EPELerrata support added

[Alan Pittman]

Franky,
   I downloaded you latest version of ya-errata-import and tried running on my 
test server. First problem I discovered is that I had to install 
perl-XML-Simple. Not a big deal. After that I ran it again. Now I'm getting the 
following:


INFO: Setting the OS variant to Redhat, if this is wrong please remove the 
--redhat option
INFO: Server is running API version 11.1
INFO: API version is supported
INFO: Authentication successful
INFO: User has administrator access to this server
INFO: Checking if channel rhel-32bit-server-6-optional-fastrack exists on 
taeps001.publix.com
INFO: Determining architecture for channel rhel-32bit-server-6-optional-fastrack
INFO: Scanning channel rhel-32bit-server-6-optional-fastrack
INFO: Loading errata
INFO: Getting erratas from date 2013-01-12 07:43:29 till now
Can't call method "call" on an undefined value at 
/usr/local/sbin/ya-errata-import.pl line 310.

If I move the old version of the perl program back into place, it runs just 
fine. Did I miss something? 

Alan


-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Franky Van Liedekerke
Sent: Tuesday, February 12, 2013 4:40 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] ya-errata-import: EPELerrata support added

Hi all,

I though this might interest some people: I added EPEL errata support 
to my errata import script called 'ya-errata-import', also with optional 
data range import (as for redhat errata).
To be more generic, I changed the following 3 parameters:

- from: --redhat-startfromprevious to: --startfromprevious
- from: --redhat-startdate to: --startdate
- from: --redhat-enddate to: --enddate

Find it here, together with an example shell file for epel import:

https://github.com/liedekef/spacewalk_scripts/

Enjoy, and feedback is welcome!

Franky

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Scheduled update fails

[Alan Pittman]

Jeremy wrote:

  1.  The yum cache on the client side hasn't been refreshed yet so it's using 
old data when trying to do the updates. You should be able to fix this by 
running "yum clean all" on the client and trying the update again (or yum 
check-update on the client)
Personally,
   I have found that sometimes, yum clean all, isn't enough. I've also had 
to delete the /var/cache/yum sub-directory, then run yum makecache.

Alan


From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jeremy Maes
Sent: Thursday, January 31, 2013 8:21 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Scheduled update fails

Op 30/01/2013 16:39, Pietro Leone Pola Falletti di Villafalletto schreef:
Hallo, I have other info, I installed another server and spacewalk tells me 
that there are some packages to update:

tzdata-2012j-1.el6.noarch tzdata-2012i-2.el6.noarch

xorg-x11-server-common-1.10.6-1.0.1.el6.centos.x86_64 
xorg-x11-server-common-1.10.6-1.el6.centos.x86_64

xorg-x11-server-Xorg-1.10.6-1.0.1.el6.centos.x86_64 
xorg-x11-server-Xorg-1.10.6-1.el6.centos.x86_64

xulrunner-10.0.12-1.el6.centos.x86_64 xulrunner-10.0.11-1.el6.centos.x86_64

But yum on the server sees one package only:

yum check-update
Loaded plugins: fastestmirror, rhnplugin, security
This system is receiving updates from RHN Classic or RHN Satellite.
Loading mirror speeds from cached hostfile

xulrunner.x86_64   10.0.12-1.el6.centos   
centos6-x86_64

Any idea?

Thanks, Pietro.
There's two possible causes I think:

  1.  The yum cache on the client side hasn't been refreshed yet so it's using 
old data when trying to do the updates. You should be avble to fix this by 
running "yum clean all" on the client and trying the update again (or yum 
check-update on the client)
  2.  The repository cache on the spacewalk server side hasn't been rebuilt. 
Normally this gets rebuilt automatically after a little time (usually max 1 
min), and is triggered by the taskomatic deamon. You can check the last repo 
change and rebuild dates in the webinterface by going to Channels > Software 
Channels > channelname you want and looking at the "Last Modified" and "Last 
Repo Build" times. They should be fairly close to each other.

If they haven't been rebuilt chances are the taskomatic daemon has crashed due 
to a bug and needs a restart.

Regards,
Jeremy
On 01/30/2013 09:23 AM, Pietro Leone Pola Falletti di Villafalletto wrote:

Hallo, any idea? I found an old bug, but the solution does not work.

Thanks, Pietro.

On 01/29/2013 05:44 PM, Pietro Leone Pola Falletti di Villafalletto wrote:

Hallo, I see several systems that need update, but when I schedule an
update it fails with this error:

Error while executing packages action: empty transaction [[6]]

On the servers yum does not find any update needed, spacewalk see three
packages.

Any idea?

Thanks, Pietro.


 DISCLAIMER 
http://www.schaubroeck.be/maildisclaimer.htm
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Patch/update selection saving and re-applying

[Alan Pittman]

Hi,
  I plan to do pretty much the same thing. The way I was thinking of doing it 
was by cloning the channels and patch/update from the clones. That way the 
channel stays static between the QA and the prod. The primary/original channel 
can continue to stay in sync with RHN (or CentOS in your case).

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Pieter Thysebaert
Sent: Tuesday, January 08, 2013 7:49 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Patch/update selection saving and re-applying

Hi,



I'm looking into setting up SpaceWalk as a way of managing at least the 
updates/patches applied to our CentOS systems.


In particular, I'm wondering whether it is feasible to "save" a selection of 
updates to install, and push thosed updates to a system some day in the future.

To be more precise: let's say we have QA and production machines. Assume we go 
through this cycle

  1. yum update on QA machine
  2. test on QA machine
  3. if OK, do same thing on production machine

Of course, some time may pass between the actions on the QA machine and the 
production machine so that "yum update" on the QA machine on one day, and then 
"yum update" on the production machine on a later day may result in different 
updates and patches (later versions) being installed on the production machine.

What would be the recommended way to keep the production machine at the same 
patchlevel as the QA machine?
Is there functionality in Spacewalk to update a machine to the same 
version/update/patchlevel as another reference machine (ie the QA machine)?
Can I save the updates applied to the QA machine, and then only update the 
production machine using this "selection" somehow?


Thanks!
Pieter
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Need URL

[Alan Pittman]

Here's what I did for openSUSE 12.2 32-bit:

1. created a normal ia-32 (32 bit) channel
 Channel name:   opensuse12.1-i586-updates
 Channel label: opensuse12.1-32bit-updates
 Channel summary:  opensuse12.1 32bit update channel

2. created a repository that looked like this:
 Label:   opensuse12.2-32bit-updates-repo
 URL:http://download.opensuse.org/update/12.2/

3. connected the repository to the channel.

4. To populate the channel, I run the following from cron:
/usr/bin/spacewalk-repo-sync --channel opensuse12.1-32bit-updates --type yum

Just be aware, openSUSE places all architectures in the same repository, so you 
will get errors about architecture mis-matches.

Alan

Unix is user friendly--it's just picky who its friends are.



-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of themaster001
Sent: Monday, January 07, 2013 1:53 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Need URL

Guys,

The laptop I had all my notes for spacewalk died the harddrive click
of death, I been looking on Google and I can't find URL that explain
how to setup and create an openSUSE channel on Spacewalk. So if anyone
one has a good link you can share, please.

Thanks,

Chuck Payne

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] converting from get_errata.pl to eva-direct-errata-sync.pl

[Alan Pittman]

Franky,
  I downloaded your script earlier today. On the first attempt, I was having 
the same issue, but then I decided to run separately against each child channel 
 and it seems to be working.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Franky Van Liedekerke
Sent: Friday, December 21, 2012 4:02 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] converting from get_errata.pl to 
eva-direct-errata-sync.pl

Maybe you can try my errata script: 
https://github.com/liedekef/spacewalk_scripts . It had been working for many 
months at the company I'm working now, for a combo of redhat and centos 
channels, land using a proxy. It's easy to use and gets the job done.


Franky
Alan Pittman mailto:alan.pitt...@publix.com>> schreef:

Based on the reply below, I decided to spend all day Thursday adding the 
additional RHEL channels and sync-ing them up. Then I re-ran the 
eva-direct-errata-sync.pl program/script. After letting it run all night (or 
however long it took), I logged on to the GUI and went to the errata screen. 
Selected "all" and nothing was displayed. See the attached jpeg.



When I ran the errata-sync script, I redirected all of standard out to a file 
in /tmp. Reviewing the file showed hundreds of messages like this:



checking if RHSA-2012:1483 exists on the destination host

Getting details for RHSA-2012:1483

getting RHSA-2012:1483 from the source

Getting details for RHSA-2012:1483

Skipping errata RHSA-2012:1483 because none of its packages could be found in 
the destination channels



Based on your reply, it makes sense that the older errata would and should be 
skipped. However, using the errata listed above (RHSA-2012:1483), I did some 
research. When I look up this one on the Red Hat Customer Portal, it’s for 
Thunderbird. Specifically for packages:



RHEL Optional Productivity Applications (v. 5 server)
IA-32:


thunderbird-10.0.11-1.el5_8.i386.rpm


x86_64:

thunderbird-10.0.11-1.el5_8.x86_64.rpm


Red Hat Enterprise Linux Server (v. 6)



SRPMS:

thunderbird-10.0.11-1.el6_3.src.rpm

MD5: ff2af052f366c47bc2dc85a678be69fa
SHA-256: fcab1a66282f61f1c7d70ef0a1510c26192efe336fd00a32f7dba384b1551b4b



IA-32:

thunderbird-10.0.11-1.el6_3.i686.rpm

MD5: 086fd6f439cf7c5b72ce26569c36fa0f
SHA-256: fc22b80774490a0ee135dd3d955faa402fd4b93379c915706009acfc7e3b173b

thunderbird-debuginfo-10.0.11-1.el6_3.i686.rpm


I then looked up thunderbird in the GUI and found the same rpms (see the 
Thunderbird gif image). So, I guess I’m not understanding standing. Is there 
something I’m missing? Is there some additional debugging options/parameters 
that I can turn on (I’m not a perl expert) that might help me debug this 
problem?


Alan









-Original Message-
From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paul Robert Marino
Sent: Wednesday, December 19, 2012 5:29 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] converting from get_errata.pl to 
eva-direct-errata-sync.pl



well these are a common question

first when you go int errata are you looking at the all or relevant

page which is the default

go into ERRATA -> All to see them all

if you just go into ERRATA  you are viewing the Relevant page which

only shows you erratas that apply to systems that have not been

patched yet.



this message

"

Skipping errata RHSA-2007:0153 because none of its packages could be

found in the destination channels

"

there are no rpms in any of the channels that match the rpms in any of

the repos that match the ones in the errata

in this case its an errata from 2007 which has probably long since

been deprecated by a newer errata  and  Redhat only keeps a few

previous versions of an rpm in RHN so your spacewalk server probably

had any of those rpms and never will. so  eva-direct-errata-sync.pl

does not publish them because essentially they are useless. its also a

safety in case your repos are out of sync with RHN; because

eva-direct-errata-sync.pl will not update an already published errata.





On Wed, Dec 19, 2012 at 2:03 PM, Alan Pittman 
mailto:alan.pitt...@publix.com>> wrote:

> Hi,

> I am in the processing of setting up a new Spacewalk server for my RHEL

> machines. My current server is scheduled to be retired sometime in 2013. I

> am running RHEL6.3 and using Spacewalk 1.7. On my current machine, I run

> get_errata.pl. It works, but it’s really slow. On my new machine, I would

> like to use eva-direct-errata-sync.pl.

>



> I just completed a test run with eva-direct and it seemed to run to

> completion, but it never loaded anything into Spacewalk. At least, when I

> logon and click on Errata, nothing appears. Reviewing the output I see allot

[Spacewalk-list] converting from get_errata.pl to eva-direct-errata-sync.pl

[Alan Pittman]

Hi,
 I am in the processing of setting up a new Spacewalk server for my RHEL 
machines. My current server is scheduled to be retired sometime in 2013. I am 
running RHEL6.3 and using Spacewalk 1.7. On my current machine, I run 
get_errata.pl. It works, but it's really slow. On my new machine, I would like 
to use eva-direct-errata-sync.pl.

 I just completed a test run with eva-direct and it seemed to run to 
completion, but it never loaded anything into Spacewalk. At least, when I logon 
and click on Errata, nothing appears. Reviewing the output I see allot of the 
following:

checking if RHSA-2007:0153 exists on the destination host
Getting details for RHSA-2007:0153
getting RHSA-2007:0153 from the source
Getting details for RHSA-2007:0153
Skipping errata RHSA-2007:0153 because none of its packages could be found in 
the destination channels
checking if RHSA-2007:0157 exists on the destination host
Getting details for RHSA-2007:0157
getting RHSA-2007:0157 from the source
Getting details for RHSA-2007:0157
getting details for package xorg-x11-apps
getting details for package xorg-x11-apps
Skipping errata RHSA-2007:0157 because none of its packages could be found in 
the destination channels
checking if RHSA-2007:0123 exists on the destination host
Getting details for RHSA-2007:0123
getting RHSA-2007:0123 from the source
Getting details for RHSA-2007:0123
Skipping errata RHSA-2007:0123 because none of its packages could be found in 
the destination channels

Here's the script and the options that I used:

#/bin/bash

/usr/bin/perl /usr/local/sbin/eva-direct-errata-sync.pl \
--sourceuser=AA \
--destinationuser= \
--sourcepassword=XX \
--destinationpassword=ZZ \
--sourcechannel=rhel-i386-server-5 \
--destinationchannel=rhel-i386-server-5 \
--sourceserver=rhn.redhat.com \
--destinationserver=localhost \
--recursive \
--verbose

Here's my Spacewalk channel structure:
   Parent:
   Channel name: rhel-i386-server-5   Channel Label: rhel-32bit-server-5
  Children:
   Channel name: rhel-i386-server-5-rhn-tools 
Channel label:  rhel-32bit-server-5-rhn-tools
   Channel name: rhel-i386-server-5-spacewalk-client-1.7  Channel label:  
rhel-32bit-server-5-spacewalk-client-1.7
   Channel name: rhel-i386-server-5-supplementary Channel 
label:  rhel-32bit-server-5-supplementary
   Channel name: rhel-i386-server-5-updates   
Channel label:  rhel-32bit-server-5-updates

The same structure exists for RHEL5-x86_64 and both RHEL6 channels.

I use mrepo to get the packages and I use spacewalk-repo-sync to load them. 
Here's an example:

/usr/bin/spacewalk-repo-sync --channel rhel-32bit-server-5-rhn-tools --type yum

In the channels I have the following number of packages:
rhel-i386-server-5-rhn-tools 233
rhel-i386-server-5-spacewalk-client-1.7  21
rhel-i386-server-5-supplementary 93
rhel-i386-server-5-updates   2559

If anyone has any suggestions as to what I can look at to determine what's 
wrong, I would appreciate it.

Alan


Alan Pittman
Publix Super Markets, Inc
863-686-8754 x46320
alan.pitt...@publix.com

Unix is user-friendly. It's just very selective about who its friends are.



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Firewall requires internal Mirroring EPEL and spacewalk repos

[Alan Pittman]

Here's the URLs that I use when syncing EPEL:

http://mirror.metrocast.net/fedora/epel/5/i386/
http://mirror.metrocast.net/fedora/epel/5/x86_64

http://mirror.metrocast.net/fedora/epel/6/i386/
http://mirror.metrocast.net/fedora/epel/6/x86_64/

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paul Robert Marino
Sent: Wednesday, August 22, 2012 2:43 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Firewall requires internal Mirroring EPEL and 
spacewalk repos

Well the important thing if you want to register existing clients is to install 
the packages in the spacewalk client repo,  EPEL is not required for this.

after you do that you just need to run rhnreg_ks with the activation key for 
the appropriate base channel and the server url

If you dont intend to run osad you will need to run rhnsd instead which does 
check ins with the spacewalk server at regular intervals. The big difference 
betwean the two is osad keeps an active encrypted connection to a jabber 
instance running on the spacewalk server so they can communicate in real time, 
and rhnsd runs rhn_check every few minutes to check if any thing needs to be 
executed via the XML RPC API via https.

As far as what url to use for mirroring EPEL just look at a box that already 
has EPEL configured in yum and copy url in the mirrorlist and or baseurl fields 
from /etc/yum.repos.d/epel.repo.


On Wed, Aug 22, 2012 at 2:00 PM, Boyd, Robert 
mailto:robert.b...@peoplefluent.com>> wrote:
I see your point - I'm just not sure how this actually will work.   I'm still 
learning how things tie together.   If I want to  have Spacewalk mirror EPEL 
and Spacewalk Client, what are the URLs I would use to create repositories in 
Spacewalk?   And then what does the yum repo link look like to be able to 
install the client software on a new client?   Surely someone has had to do 
this before for an environment where the clients aren't allowed to face the 
Internet directly.

Or I suppose I could create a sub-directory under http://spacewalkhost/pub  
with the specific rpms linked into it and pull them down that way.   What I'm 
looking for is the most reasonable way to make it work with the least amount of 
ongoing maintenance required to keep it up to date.

Thanks,
Robert

From: 
spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com]
 On Behalf Of Paul Robert Marino
Sent: Tuesday, August 21, 2012 7:36 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Firewall requires internal Mirroring EPEL and 
spacewalk repos


Keep in mind as long as you don't use osad its all https so I don't see the 
point.
On Aug 21, 2012 7:29 PM, "Paul Robert Marino" 
mailto:prmari...@gmail.com>> wrote:

Well yea but why not just have spacewalk directly mirror epel and cut out the 
middle man
On Aug 21, 2012 7:01 PM, "Boyd, Robert" 
mailto:robert.b...@peoplefluent.com>> wrote:
It appears that due to firewalling and such I'll need to build an internal yum 
repo mirror of EPEL and spacewalk repos.   I have mrepo running on my spacewalk 
master server.   Can I easily tell mrepo to mirror those 2 so I can serve them 
internally from there?

And, question #2 - if I have spacewalk proxy servers running, can I use them as 
repo mirrors too with what's already installed on them, or will I need to 
install mrepo or figure out using createrepo to do that?

Thanks for any tips you might think of for doing this.

Robert Boyd
Senior Systems Engineer
Phone: 919-645-2972
Mobile: 919-306-4681
Peoplefluent
434 Fayetteville Street
Raleigh, NC  27601

robert.b...@peoplefluent.com

[Description: Description: Description: cid:image001.png@01CC344B.23823870]



This email message is for the sole use of the intended recipient(s) and may 
contain confidential information. Any unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, please 
contact the sender by reply email and destroy all copies of the original 
message.


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

<>___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Repository URL?

[Alan Pittman]

Nick,
  Unfortunately, Spacewalk won’t/can’t connect to RHN. What mrepo will do is 
connect(logon) to RHN and pull all of the RPMs and place them in a series on 
directories. With the appropriate options, mrepo will then create a local 
repository which then can be used to populate the Spacewalk database.

Follow the steps to install mrepo (if you haven’t already) and run the 
gensystemid script (should be one of the steps in the install doc). Once that’s 
done, you’ll have to create or update the mrepo.conf file. Here’s a portion of 
mine so that you have an idea what to configure:

root@taeps001 etc]# cat ./mrepo.conf
### Configuration file for mrepo

### The [main] section allows to override mrepo's default settings
### The mrepo-example.conf gives an overview of all the possible settings
[main]
srcdir = /clonefs
wwwdir = /var/www/mrepo
confdir = /etc/mrepo.conf.d
arch = i386 x86_64

mailto = root@localhost
smtp-server = localhost

rhnlogin = :

### Any other section is considered a definition for a distribution
### You can put distribution sections in /etc/mrepo.conf.d/
### Examples can be found in the documentation at:
### /usr/share/doc/mrepo-0.8.7/dists/.

[5Server-x86_64]
name = Red Hat Enterprise Server ($release) ($arch)
release = 5
arch = x86_64
metadata = repomd repoview
iso = /clonefs/5Server-x86_64/rhel-server-5.7-x86_64-dvd.iso

### Additional repositories
updates = rhns:///rhel-$arch-server-5
# vt = rhns:///rhel-$arch-server-$repo-5
supplementary = rhns:///rhel-$arch-server-$repo-5
# fastrack = rhns:///rhel-$arch-server-$repo-5
# hts = rhns:///rhel-$arch-server-$repo-5
rhn-tools = rhns:///$repo-rhel-$arch-server-5

### RPMforge repository
# rpmforge = 
rsync://apt.sw.be/pub/freshrpms/pub/dag/redhat/el$release/en/$arch/RPMS.dag/
#rpmforge = ftp://apt.sw.be/pub/dag/pub/redhat/el$release/en/$arch/RPMS.dag/
rpmforge = http://apt.sw.be/redhat/el$release/en/$arch/RPMS.dag/

### EPEL repository
# EPEL = http://mirror.chpc.utah.edu/pub/epel/$release/$arch/
EPEL = http://mirror.metrocast.net/fedora/epel/5/x86_64/

### ELrepo repository
elrepo = http://elrepo.org/linux/elrepo/el5/$arch/
#elrepo-testing = http://elrepo.org/linux/testing/el5/$arch/

### OpenVZ repositories
#ovzkernel = http://download.openvz.org/kernel/rhel5/
#ovztemplate = http://download.openvz.org/template/
#ovzutils = http://download.openvz.org/utils/

### Fedora EPEL packages (incompatible with RPMforge)
#epel = http://download.fedora.redhat.com/pub/epel/$release/$arch/

### Custom repository for your own RPM packages
mondo = http://www.mondorescue.org/ftp/rhel/5/x86_64
spacewalk = http://spacewalk.redhat.com/yum/1.7/RHEL/5/x86_64


From: fn...@yahoo.com [mailto:fn...@yahoo.com]
Sent: Friday, August 03, 2012 9:07 AM
To: Alan Pittman; 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Repository URL?

Hi Alan,

Thank you very much for your very helpful reply!!

My purpose is to patch all of our RHEL5x/6x systems, so I need to "connect to 
RHN and download all of the available RPMS and populate your Spacewalk 
repository" as you said. Please correct me if I am wrong here.

I've just installed mrepo, but still don't understand the whole picture. With 
mrepor's help, can Spacewalk connect directly to the RHN servers? What URL 
should be used in the Repository URL? Yes, I have RHN userid and password.

Have a nice day!

Nick

________
From: Alan Pittman mailto:alan.pitt...@publix.com>>
To: "'fn...@yahoo.com'" mailto:fn...@yahoo.com>>; 
"'spacewalk-list@redhat.com'" 
mailto:spacewalk-list@redhat.com>>
Sent: Thursday, August 2, 2012 9:42:35 PM
Subject: RE: [Spacewalk-list] Repository URL?

Nick,
   When I click on the link, the browser takes me to the repodata 
sub-directory. When I tried backing up a couple of levels, I never saw any RPMs.

Can I assume that you want to connect to RHN and download all of the available 
RPMS and populate your Spacewalk repository? If so, you’ll have to download and 
install a utility called mrepo because Spacewalk doesn’t have the ability to 
connect directly to the RHN servers.

Also,  must also have a valid RHN userid and password for mrepo to connect.

aep


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of 
fn...@yahoo.com<mailto:fn...@yahoo.com>
Sent: Thursday, August 02, 2012 5:01 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Repository URL?

Hi, I am now trying to create my first Repository for RHEL 6 (64bit) systems. 
Can I use the following link as Repository URL in  Spacewalk's Create New 
Repository page?

ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/x86_64/Debuginfo/repodata/

If it's not the right one, where can I find it?

Thank  you in advance!

Nick

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Repository URL?

[Alan Pittman]

Nick,
   When I click on the link, the browser takes me to the repodata 
sub-directory. When I tried backing up a couple of levels, I never saw any RPMs.

Can I assume that you want to connect to RHN and download all of the available 
RPMS and populate your Spacewalk repository? If so, you'll have to download and 
install a utility called mrepo because Spacewalk doesn't have the ability to 
connect directly to the RHN servers.

Also,  must also have a valid RHN userid and password for mrepo to connect.

aep


From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of fn...@yahoo.com
Sent: Thursday, August 02, 2012 5:01 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Repository URL?

Hi, I am now trying to create my first Repository for RHEL 6 (64bit) systems. 
Can I use the following link as Repository URL in  Spacewalk's Create New 
Repository page?

ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/x86_64/Debuginfo/repodata/

If it's not the right one, where can I find it?

Thank  you in advance!

Nick
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Install spacewalk - first issue

[Alan Pittman]

Well, maybe, maybe not. It depends on how the firewall is set up.

I'm making the assumption that you are running Red Hat EL6.

If the firewall rules are all IP based, you may have access to the RHN 
locations and not anything else. Here's all of the locations related to RHN and 
their IP addresses:


xmlrpc.rhn.redhat.com:443 - 209.132.183.44

xmlrpc.rhn.redhat.com:80 - 209.132.183.44

rhn.redhat.com:443 - 209.132.183.42

rhn.redhat.com:80 - 209.132.183.42

content-xmlrpc.rhn.redhat.com:443 - 184.26.116.218

content-xmlrpc.rhn.redhat.com:80 - 184.26.116.218

content-web.rhn.redhat.com:443 - 23.11.106.169

content-web.rhn.redhat.com:80 - 23.11.106.169



The spacewalk server is at the following address:



spacewalk.redhat.com - 209.132.183.81. Port is 80



So, it's possible that the firewall is not allowing outbound access to this 
address.

This is just a shot in the dark.





Alan


From: fn...@yahoo.com [mailto:fn...@yahoo.com]
Sent: Friday, July 27, 2012 4:04 PM
To: Alan Pittman; 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Install spacewalk - first issue

Firewall should be taken into account. Before running rpm, I did 'yum update' 
without problem. Does this mean there is no firewall issue? Here is the output 
summary of 'yum update':

-
# yum update
Install  1 Package(s)
Upgrade  13 Package(s)
Total download size: 57 M
Is this ok [y/N]: y

Installed:  kernel.x86_64 0:2.6.32-279.2.1.el6
Updated:  bind-libs.x86_64 32:9.8.2-0.10.rc1.el6_3.1   bind-utils.x86_64 
32:9.8.2-0.10.rc1.el6_3.1   glibc.x86_64 0:2.12-1.80.el6_3.3   
glibc-common.x86_64 0:2.12-1.80.el6_3.3   kernel-firmware.noarch 
0:2.6.32-279.2.1.el6   kpartx.x86_64 0:0.4.9-56.el6_3.1   net-snmp.x86_64 
1:5.5-41.el6_3.1   net-snmp-libs.x86_64 1:5.5-41.el6_3.1   
net-snmp-utils.x86_64 1:5.5-41.el6_3.1   nscd.x86_64 0:2.12-1.80.el6_3.3   
perf.x86_64 0:2.6.32-279.2.1.el6   tzdata.noarch 0:2012c-3.el6   
tzdata-java.noarch 0:2012c-3.el6
Complete!
-

Thank you!

Nick

____
From: Alan Pittman mailto:alan.pitt...@publix.com>>
To: "'fn...@yahoo.com'" mailto:fn...@yahoo.com>>; 
"'spacewalk-list@redhat.com'" 
mailto:spacewalk-list@redhat.com>>
Sent: Friday, July 27, 2012 3:28:47 PM
Subject: RE: [Spacewalk-list] Install spacewalk - first issue

Just out of curiosity, is this machine behind a firewall and/or a proxy server?

Alan

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of 
fn...@yahoo.com<mailto:fn...@yahoo.com>
Sent: Friday, July 27, 2012 3:07 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Install spacewalk - first issue

wget not working either.

Nick


From: Brian Collins mailto:bri...@sedata.com>>
To: "'spacewalk-list@redhat.com'" 
mailto:spacewalk-list@redhat.com>>
Sent: Friday, July 27, 2012 2:34:17 PM
Subject: Re: [Spacewalk-list] Install spacewalk - first issue

> Hi, I started installing spacewalk and got my first issue. Please help and 
> thank
> you in advance. Here is the issue:
>
> # rpm -Uvh
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm
> Retrieving
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm
> error: open of  failed: No such file or directory
>  <>
> # yum -y install
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm
> Loaded plugins: product-id, rhnplugin, security, subscription-manager
> Updating certificate-based repositories.
> Unable to read consumer identity
> Setting up Install Process
> spacewalk-repo-1.7-
> 5.el6.noarch.rpm  
>| 1.7 kB 00:00
> Cannot open:
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm. Skipping.
> Error: Nothing to do
[]
Just for gits and shiggles, what happens when you try this:
# wget 
http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-5.el6.noarch.rpm
# yum localinstall spacewalk-repo-1.7-5.el6.noarch.rpm



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Install spacewalk - first issue

[Alan Pittman]

Just out of curiosity, is this machine behind a firewall and/or a proxy server?

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of fn...@yahoo.com
Sent: Friday, July 27, 2012 3:07 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Install spacewalk - first issue

wget not working either.

Nick


From: Brian Collins mailto:bri...@sedata.com>>
To: "'spacewalk-list@redhat.com'" 
mailto:spacewalk-list@redhat.com>>
Sent: Friday, July 27, 2012 2:34:17 PM
Subject: Re: [Spacewalk-list] Install spacewalk - first issue

> Hi, I started installing spacewalk and got my first issue. Please help and 
> thank
> you in advance. Here is the issue:
>
> # rpm -Uvh
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm
> Retrieving
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm
> error: open of  failed: No such file or directory
>  <>
> # yum -y install
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm
> Loaded plugins: product-id, rhnplugin, security, subscription-manager
> Updating certificate-based repositories.
> Unable to read consumer identity
> Setting up Install Process
> spacewalk-repo-1.7-
> 5.el6.noarch.rpm  
>| 1.7 kB 00:00
> Cannot open:
> http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-
> 5.el6.noarch.rpm. Skipping.
> Error: Nothing to do
[]
Just for gits and shiggles, what happens when you try this:
# wget 
http://spacewalk.redhat.com/yum/1.7/RHEL/6/x86_64/spacewalk-repo-1.7-5.el6.noarch.rpm
# yum localinstall spacewalk-repo-1.7-5.el6.noarch.rpm



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Register Suse Systems

[Alan Pittman]

Thanks Michael for the clarification, you are correct. The plugin is general 
for libzypp. So, yes, yast should work. It's just a habit for me to always use 
the zypper from the command line.

You may have already done this, but here's something to double check...

Logon to the Spacewalk GUI and verify that your SuSE system is actually 
subscribed to the desired channel (and child channel, if you followed my 
example).

Alan


-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Michael Calmer
Sent: Thursday, June 14, 2012 8:01 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Register Suse Systems

Hi,

this plugin is general for libzypp. This means also yast can access spacewalk 
after it is installed. It is not limted to zypper commandline tool.

About the error: Are you sure, that mirror process on spacewalk of the suse 
repos is finished and the metadata are already created?

Missing metadata could be a reason why yast display this message.

Am Donnerstag, 14. Juni 2012, 13:31:07 schrieb Alan Pittman:
> If all of the Spacewalk client components installed correctly, there is a 
zipper plug-in. So instead of using yast, you issue the following from the 
command line:
> 
> # zypper ref  <- refreshes the local repo
> # zypper lu<- lists any and all available updates
> # zypper up   <- applies the updates.
> 
> FYI - zypper is similar to Red Hat's yum command.
> 
> Alan
> 
> From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-
boun...@redhat.com] On Behalf Of trum...@gmail.com
> Sent: Wednesday, June 13, 2012 4:38 PM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] Register Suse Systems
> 
> On , Alan Pittman mailto:alan.pitt...@publix.com>> 
wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> > Here's how I manage opensuse, hopefully this helps. This is an answer to 
similar question a while back.
> >
> >
> >
> > Hi Chuck,
> >
> >   I use Spacewalk to manage a couple of opensuse 12.1 machines.
> >
> >
> >
> > Here's what I've got setup, using 32bit as the example:
> >
> > Parent Channel:
> >
> >
> >
> > Channel Name: opensuse12.1-i586
> >
> > Channel Label:opensuse12.1-32bit
> >
> > Parent Channel:   (none)
> >
> > Yum Repository Checksum Type:   sha1
> >
> > Architecture: IA-32
> >
> >
> >
> > Update channel (note: I have two child channels, just showing the update 
channel here):
> >
> >
> >
> > Channel Name: opensuse12.1-i586-updates
> >
> > Channel Label:opensuse12.1-32bit-updates
> >
> > Parent Channel:   opensuse12.1-i586
> >
> > Yum Repository Checksum Type:   sha1
> >
> > Architecture: IA-32
> >
> > Summary:opensuse12.1 32bit update channel
> >
> >
> >
> > Repo for the update channel:
> >
> >
> >
> > Repo label: opensuse12.1-32bit-updates-repo
> >
> > Repo URL:
> > http://download.opensuse.org/update/12.1/
> >
> >
> >
> > To sync the channel, I created a script that I schedule via cron:
> >
> > [root@taeps001 ~]# cat /usr/local/bin/sync-opensuse12-32.sh
> >
> > #!/bin/bash
> >
> > /usr/bin/spacewalk-repo-sync --channel opensuse12.1-32bit-updates --type 
yum
> >
> >
> >
> > When the sync runs, I get a log of messages that look like this:
> >
> >
> >
> > Package arch x86_64 incompatible with channel opensuse12.1-32bit-updates
> >
> >
> >
> > You need not worry about them, opensuse places both i586 and x86_64 rpms 
in the same remote repository. Spacewalk will receive them, but since I'm are 
trying to sync a 32 bit channel (ia-32), the x86_64 packages just exist in 
"limbo".
> > Going to "Manage Software Packages" and in the Channel field, select 
"packages with no channels", the x86_64 packages will display.
> >
> >
> >
> >
> > If you create an opensuse x86_64 channel and run a sync, these "limbo" 
packages get pushed into the x86_64 channel. At least, that what it appears to 
do.
> >
> >
> >
> > On the opensuse machine, I just followed these procedures:
> > https://fedorahosted.org/spacewalk/wiki/RegisteringClients.
> >
> > The machines don't have internet access, so I manually downloaded the 
spacewalk-client packages and installed them.
> >
> > The opensuse client packages can be found here: 
baseurl=http://download.opensuse.org/reposi

Re: [Spacewalk-list] Register Suse Systems

[Alan Pittman]

If all of the Spacewalk client components installed correctly, there is a 
zipper plug-in. So instead of using yast, you issue the following from the 
command line:

# zypper ref  <- refreshes the local repo
# zypper lu<- lists any and all available updates
# zypper up   <- applies the updates.

FYI - zypper is similar to Red Hat's yum command.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of trum...@gmail.com
Sent: Wednesday, June 13, 2012 4:38 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Register Suse Systems

On , Alan Pittman mailto:alan.pitt...@publix.com>> 
wrote:
>
>
>
>
>
>
>
>
> Here's how I manage opensuse, hopefully this helps. This is an answer to 
> similar question a while back.
>
>
>
> Hi Chuck,
>
>   I use Spacewalk to manage a couple of opensuse 12.1 machines.
>
>
>
> Here's what I've got setup, using 32bit as the example:
>
> Parent Channel:
>
>
>
> Channel Name: opensuse12.1-i586
>
> Channel Label:opensuse12.1-32bit
>
> Parent Channel:   (none)
>
> Yum Repository Checksum Type:   sha1
>
> Architecture: IA-32
>
>
>
> Update channel (note: I have two child channels, just showing the update 
> channel here):
>
>
>
> Channel Name: opensuse12.1-i586-updates
>
> Channel Label:opensuse12.1-32bit-updates
>
> Parent Channel:   opensuse12.1-i586
>
> Yum Repository Checksum Type:   sha1
>
> Architecture: IA-32
>
> Summary:opensuse12.1 32bit update channel
>
>
>
> Repo for the update channel:
>
>
>
> Repo label: opensuse12.1-32bit-updates-repo
>
> Repo URL:
> http://download.opensuse.org/update/12.1/
>
>
>
> To sync the channel, I created a script that I schedule via cron:
>
> [root@taeps001 ~]# cat /usr/local/bin/sync-opensuse12-32.sh
>
> #!/bin/bash
>
> /usr/bin/spacewalk-repo-sync --channel opensuse12.1-32bit-updates --type yum
>
>
>
> When the sync runs, I get a log of messages that look like this:
>
>
>
> Package arch x86_64 incompatible with channel opensuse12.1-32bit-updates
>
>
>
> You need not worry about them, opensuse places both i586 and x86_64 rpms in 
> the same remote repository. Spacewalk will receive them, but since I'm are 
> trying to sync a 32 bit channel (ia-32), the x86_64 packages just exist in 
> "limbo".
> Going to "Manage Software Packages" and in the Channel field, select 
> "packages with no channels", the x86_64 packages will display.
>
>
>
>
> If you create an opensuse x86_64 channel and run a sync, these "limbo" 
> packages get pushed into the x86_64 channel. At least, that what it appears 
> to do.
>
>
>
> On the opensuse machine, I just followed these procedures:
> https://fedorahosted.org/spacewalk/wiki/RegisteringClients.
>
> The machines don't have internet access, so I manually downloaded the 
> spacewalk-client packages and installed them.
>
> The opensuse client packages can be found here: 
> baseurl=http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/1.7/openSUSE_12.1/
>
>
>
> Hope this helps.
>
>
>
> Alan
>
>
>
>
>
> From: 
> spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
> [mailto:spacewalk-list-boun...@redhat.com]
> On Behalf Of trum...@gmail.com<mailto:trum...@gmail.com>
>
> Sent: Wednesday, June 13, 2012 3:29 PM
>
> To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
>
> Subject: [Spacewalk-list] Register Suse Systems
>
>
>
> Can someone point me to instructions on how to configure a suse system to use 
> spacewalk?
>
>
>
>
>
>
Thanks Alan,
How do you set the suse system to use spacewalk for update? I was able to get 
the suse system to register with spacewalk server. but if I bring up yast it 
complains about update repo not being defined?
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Register Suse Systems

[Alan Pittman]

Here's how I manage opensuse, hopefully this helps. This is an answer to 
similar question a while back.



Hi Chuck,

  I use Spacewalk to manage a couple of opensuse 12.1 machines.



Here's what I've got setup, using 32bit as the example:

Parent Channel:



Channel Name: opensuse12.1-i586

Channel Label:opensuse12.1-32bit

Parent Channel:   (none)

Yum Repository Checksum Type:   sha1

Architecture: IA-32



Update channel (note: I have two child channels, just showing the update 
channel here):



Channel Name: opensuse12.1-i586-updates

Channel Label:opensuse12.1-32bit-updates

Parent Channel:   opensuse12.1-i586

Yum Repository Checksum Type:   sha1

Architecture: IA-32

Summary:opensuse12.1 32bit update channel

Repo for the update channel:



Repo label: opensuse12.1-32bit-updates-repo

Repo URL: http://download.opensuse.org/update/12.1/



To sync the channel, I created a script that I schedule via cron:

[root@taeps001 ~]# cat /usr/local/bin/sync-opensuse12-32.sh

#!/bin/bash

/usr/bin/spacewalk-repo-sync --channel opensuse12.1-32bit-updates --type yum



When the sync runs, I get a log of messages that look like this:



Package arch x86_64 incompatible with channel opensuse12.1-32bit-updates



You need not worry about them, opensuse places both i586 and x86_64 rpms in the 
same remote repository. Spacewalk will receive them, but since I'm are trying 
to sync a 32 bit channel (ia-32), the x86_64 packages just exist in "limbo". 
Going to "Manage Software Packages" and in the Channel field, select "packages 
with no channels", the x86_64 packages will display.



If you create an opensuse x86_64 channel and run a sync, these "limbo" packages 
get pushed into the x86_64 channel. At least, that what it appears to do.

On the opensuse machine, I just followed these procedures: 
https://fedorahosted.org/spacewalk/wiki/RegisteringClients.

The machines don't have internet access, so I manually downloaded the 
spacewalk-client packages and installed them.

The opensuse client packages can be found here: 
baseurl=http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/1.7/openSUSE_12.1/



Hope this helps.



Alan




From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of trum...@gmail.com
Sent: Wednesday, June 13, 2012 3:29 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Register Suse Systems

Can someone point me to instructions on how to configure a suse system to use 
spacewalk?
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 1.7 for RHEL 4/5/6

[Alan Pittman]

Hi,
  Yes, I am using Spacewalk 1.7 to manage updates to seven RHEL5 servers. I'm 
currently not using the Kickstart function, just using it as a manager for 
updates.
I use the mrepo utility (found on sourceforge) to download the updates from RHN 
and then I use the repo-sync function to update Spacewalk.

Alan

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paul Saini
Sent: Thursday, May 24, 2012 9:47 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk 1.7 for RHEL 4/5/6

Hi, new member to the community. On Spacewalk site comparing Sattelite to 
itself, they do not list RHEL 5/6 as supported for spacewalk. Is there a member 
running Spacewalk to manage, monitor, and support RHEL 5 and 6 (entitled with 
RHN) systems?

Cheers!
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] [spacewalk-list] openSUSE

[Alan Pittman]

Hi Chuck,
  I use Spacewalk to manage a couple of opensuse 12.1 machines.

Here's what I've got setup, using 32bit as the example:
Parent Channel:

Channel Name:   opensuse12.1-i586
Channel Label:  opensuse12.1-32bit
Parent Channel: (none)
Yum Repository Checksum Type:   sha1
Architecture:   IA-32

Update channel (note: I have two child channels, just showing the update 
channel here):

Channel Name:   opensuse12.1-i586-updates
Channel Label:  opensuse12.1-32bit-updates
Parent Channel: opensuse12.1-i586
Yum Repository Checksum Type:   sha1
Architecture:   IA-32
Summary:opensuse12.1 32bit update channel
 
Repo for the update channel:

Repo label: opensuse12.1-32bit-updates-repo
Repo URL: http://download.opensuse.org/update/12.1/

To sync the channel, I created a script that I schedule via cron:
[root@taeps001 ~]# cat /usr/local/bin/sync-opensuse12-32.sh
#!/bin/bash
/usr/bin/spacewalk-repo-sync --channel opensuse12.1-32bit-updates --type yum

When the sync runs, I get a log of messages that look like this:

Package arch x86_64 incompatible with channel opensuse12.1-32bit-updates

You need not worry about them, opensuse places both i586 and x86_64 rpms in the 
same remote repository. Spacewalk will receive them, but since I'm are trying 
to sync a 32 bit channel (ia-32), the x86_64 packages just exist in "limbo". 
Going to "Manage Software Packages" and in the Channel field, select "packages 
with no channels", the x86_64 packages will display. 

If you create an opensuse x86_64 channel and run a sync, these "limbo" packages 
get pushed into the x86_64 channel. At least, that what it appears to do.
 
On the opensuse machine, I just followed these procedures: 
https://fedorahosted.org/spacewalk/wiki/RegisteringClients.
The machines don't have internet access, so I manually downloaded the 
spacewalk-client packages and installed them.
The opensuse client packages can be found here: 
baseurl=http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/1.7/openSUSE_12.1/

Hope this helps.

Alan  

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of themaster001
Sent: Wednesday, March 14, 2012 9:24 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] [spacewalk-list] openSUSE

Guys,

I am looking on how to set up openSUSE on my spacewalk server. I have
googled and I found the SuSE product base on spacewalk, but I want to
set up openSUSE on spacewalk.

Also, how stable is Debian, is there a good how to on it.

Thanks,

Chuck

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] spacewalk-client 1.7, opensuse12.1

[Alan Pittman]

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: Tuesday, March 13, 2012 5:56 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] spacewalk-client 1.7, opensuse12.1

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

  File "/usr/share/rhn/up2date_client/up2dateErrors.py", line 188, in 

class SSLCertificateVerifyFailedError(RepoError, Error):

TypeError: Error when calling the metaclass bases

duplicate base class Error

Problem lies within up2dateErrors.py (rhn-client-tools-1.7.14-2.1.noarch.rpm).
Changing
class SSLCertificateVerifyFailedError(RepoError, Error)
back to
class SSLCertificateVerifyFailedError(RepoError)

seems to work (line 188 in the file).

("Error" (parameter?) was added here: 
http://git.fedorahosted.org/git/?p=spacewalk.git;a=commitdiff;h=9b28ded9de35b00d05457c877b8e8bb9d68a37de)

Don't know much about python, so can't exactly tell what is happening, but 
until it's fixed this seems like a usable solution.

Regards
Ralf
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] spacewalk-client 1.7, opensuse12.1

[Alan Pittman]

Hi,
  I'm trying to register an opensuse12.1 (i586) system to a Spacewalk 1.7 
server. When I run the rhnreg_ks command, I get the following traceback:

taepw01:~ # rhnreg_ks --serverUrl=http://taeps001.publix.com/XMLRPC 
--activationkey=1-d6968a41ae47529f7f24ebd1b8dc6cca

Traceback (most recent call last):
  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
  File "/usr/share/rhn/up2date_client/up2dateErrors.py", line 188, in 
class SSLCertificateVerifyFailedError(RepoError, Error):
TypeError: Error when calling the metaclass bases
duplicate base class Error

I've tried searching with Google and can't seem to determine what the issue is. 
My best guess is that this
might be python related, but not sure.

Here are the packages that I have installed:

rhn-client-tools-1.7.14-2.1.noarch
rhn-setup-1.7.14-2.1.noarch
rhnsd-4.9.15-2.1.i586
rhnlib-2.5.51-1.1.noarch
rhn-check-1.7.14-2.1.noarch
yum-3.2.25-11.1.2.i586
zypp-plugin-spacewalk-0.6-2.1.i586

Thanks for any help you can provide.

Alan







___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] duplicate key value during Spacewalk 1.6 to 1.7, using postgresql

[Alan Pittman]

Jan,
  Thanks for the help. I'll restore and try it again.

aep

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jan Pazdziora
Sent: Thursday, March 08, 2012 8:49 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] duplicate key value during Spacewalk 1.6 to 1.7, 
using postgresql

On Thu, Mar 08, 2012 at 01:03:56PM +0000, Alan Pittman wrote:
> Thanks for the reply. As you requested, I renamed the 
> 111-rhnPackageKey-data.sql and then created a new version of the file with 
> the information you supplied below. When I rerun the 
> /usr/bin/spacewalk-schema-upgrade, I get the following message: 
> 
> [root@taeps001 ~]# /usr/bin/spacewalk-schema-upgrade
> Unknown schema name [(0 rows)] found.
> [root@taeps001 ~]#
> 
> What am I doing wrong?

Your previous schema upgrade failed, so the schema upgrade script
cannot determine what version to start the upgrade from.

Your best best is to just restore the database backup and run the
schema upgrade fully, from 1.6 to 1.7.

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] duplicate key value during Spacewalk 1.6 to 1.7, using postgresql

[Alan Pittman]

Thanks for the reply. As you requested, I renamed the 
111-rhnPackageKey-data.sql and then created a new version of the file with the 
information you supplied below. When I rerun the 
/usr/bin/spacewalk-schema-upgrade, I get the following message: 

[root@taeps001 ~]# /usr/bin/spacewalk-schema-upgrade
Unknown schema name [(0 rows)] found.
[root@taeps001 ~]#

What am I doing wrong?

Here's the content of the new 111 file:

[root@taeps001 ~]# cd 
/etc/sysconfig/rhn/schema-upgrade/spacewalk-schema-1.6-to-spacewalk-schema-1.7
[root@taeps001 spacewalk-schema-1.6-to-spacewalk-schema-1.7]# ll 111*
-rw-r--r-- 1 root root 1080 Mar  8 07:49 111-rhnPackageKey-data.sql
-rw-r--r-- 1 root root 1256 Mar  8 07:49 111-rhnPackageKey-data.sql.x
[root@taeps001 spacewalk-schema-1.6-to-spacewalk-schema-1.7]# cat 
./111-rhnPackageKey-data.sql
-- Fedora 16, 17, 18
update rhnPackageKey set provider_id = lookup_package_provider('Fedora')
where key_id in ('067f00b6a82ba4b7', '50e94c991aca3465', '0983129322b3b81a');

-- Fedora 16
insert into rhnPackageKey (id, key_id, key_type_id, provider_id)
select sequence_nextval('rhn_pkey_id_seq'), '067f00b6a82ba4b7', 
lookup_package_key_type('gpg'), lookup_package_provider('Fedora')
from dual
where not exists ( select 1 from rhnPackageKey where key_id = 
'067f00b6a82ba4b7' );
-- Fedora 17
insert into rhnPackageKey (id, key_id, key_type_id, provider_id)
select sequence_nextval('rhn_pkey_id_seq'), '50e94c991aca3465', 
lookup_package_key_type('gpg'), lookup_package_provider('Fedora')
from dual
where not exists ( select 1 from rhnPackageKey where key_id = 
'50e94c991aca3465' );
-- Fedora 18
insert into rhnPackageKey (id, key_id, key_type_id, provider_id)
select sequence_nextval('rhn_pkey_id_seq'), '0983129322b3b81a', 
lookup_package_key_type('gpg'), lookup_package_provider('Fedora')
from dual
where not exists ( select 1 from rhnPackageKey where key_id = 
'0983129322b3b81a' );

[root@taeps001 spacewalk-schema-1.6-to-spacewalk-schema-1.7]#

Alan



-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jan Pazdziora
Sent: Thursday, March 08, 2012 5:41 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] duplicate key value during Spacewalk 1.6 to 1.7, 
using postgresql

On Wed, Mar 07, 2012 at 08:54:24PM +, Alan Pittman wrote:
> Hi,
>   I'm upgrading Spacewalk w/postgresql on a RHEL6, x86_64 server. All went 
> well until I ran the schema update. Got the following  error message:
> 
>  ?column? 
>  
> 
>  
> spacewalk-schema-1.6-to-spacewalk-schema-1.7/110-create_pxt_session.sql.postgresql
> (1 row)
> 
> CREATE FUNCTION
> COMMIT
> ?column? 
> -
>  spacewalk-schema-1.6-to-spacewalk-schema-1.7/111-rhnPackageKey-data.sql
> (1 row)
> 
> psql:/var/log/spacewalk/schema-upgrade/20120307-154732-script.sql:5090: 
> ERROR:  duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
> 
> This is just the bottom of the schema-upgrade log file. If you want to see 
> the whole file, let me know and I'll send it. Just trying to conserve space 
> here.
> 

Can you replace the 111-rhnPackageKey-data.sql file with

-- Fedora 16, 17, 18
update rhnPackageKey set provider_id = lookup_package_provider('Fedora')
where key_id in ('067f00b6a82ba4b7', '50e94c991aca3465', '0983129322b3b81a');

-- Fedora 16
insert into rhnPackageKey (id, key_id, key_type_id, provider_id)
select sequence_nextval('rhn_pkey_id_seq'), '067f00b6a82ba4b7', 
lookup_package_key_type('gpg'), lookup_package_provider('Fedora')
from dual
where not exists ( select 1 from rhnPackageKey where key_id = 
'067f00b6a82ba4b7' );
-- Fedora 17
insert into rhnPackageKey (id, key_id, key_type_id, provider_id)
select sequence_nextval('rhn_pkey_id_seq'), '50e94c991aca3465', 
lookup_package_key_type('gpg'), lookup_package_provider('Fedora')
from dual
where not exists ( select 1 from rhnPackageKey where key_id = 
'50e94c991aca3465' );
-- Fedora 18
insert into rhnPackageKey (id, key_id, key_type_id, provider_id)
select sequence_nextval('rhn_pkey_id_seq'), '0983129322b3b81a', 
lookup_package_key_type('gpg'), lookup_package_provider('Fedora')
from dual
where not exists ( select 1 from rhnPackageKey where key_id = 
'0983129322b3b81a' );

and start the schema upgrade anew?

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] duplicate key value during Spacewalk 1.6 to 1.7, using postgresql

[Alan Pittman]

Hi,
  I'm upgrading Spacewalk w/postgresql on a RHEL6, x86_64 server. All went well 
until I ran the schema update. Got the following  error message:

 ?column?   
   

 
spacewalk-schema-1.6-to-spacewalk-schema-1.7/110-create_pxt_session.sql.postgresql
(1 row)

CREATE FUNCTION
COMMIT
?column? 
-
 spacewalk-schema-1.6-to-spacewalk-schema-1.7/111-rhnPackageKey-data.sql
(1 row)

psql:/var/log/spacewalk/schema-upgrade/20120307-154732-script.sql:5090: ERROR:  
duplicate key value violates unique constraint "rhn_pkey_keyid_uq"

This is just the bottom of the schema-upgrade log file. If you want to see the 
whole file, let me know and I'll send it. Just trying to conserve space here.

Alan

Alan Pittman 
Publix Super Markets, Inc. 
863-686-8754 ext. 46320 
alan.pitt...@publix.com 

"Unix is user-friendly. It's just very selective about who its friends are."




___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Fedora 16 client not getting updates from Spacewalk 1.6

[Alan Pittman]

Jonathan,
   Thanks for the reply.

 Unfortunately, I have tried that and it does not work.

The steps that I have taken are:

# yum clean all
# cd /var/cache/yum
# rm -Rf ./*
# yum makecache
# yum check-update

With the /etc/yum/repos.d/fedora-updates.repo turned off (enable=0), I don't 
receive any messages stating that there are RPMs to receive and apply. If I 
turn fedora-updates.repo on, the I get a list.

Whatever the problem is, it just recently occurred. Up until approximately a 
week ago, I was able to update F16 from Spacewalk without any issues.

I even tried removing the spacewalk-client RPMs, re-installing them and 
re-registering the client. Still no luck.

Alan




From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jonathan DeHaan
Sent: Friday, February 03, 2012 11:23 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Fedora 16 client not getting updates from 
Spacewalk 1.6

If you run 'rm -rf /var/cache/yum/i686/16/*' on the client, does that fix it?

I haven't upgraded to SW 1.6, but on 1.5, the yum cache for yum-rhn-plugin is 
not properly cleared by 'yum clean all', and it may take some time for the 
client to update it's cache of the available packages from SW.

Jonathan

On 02/03/2012 09:58 AM, Alan Pittman wrote:
Hi.
I've encountered an interesting issue with Spacewalk 1.6 and Fedora16. If I run 
yum check-update, the F16 client doesn't see the available packages in the 
Spacewalk repository. If I logon to the Spacewalk GUI, Spacewalk will report 
that there are available RPMs for updating.

If I activate the fedora-updates.repo and run yum check-update, updated 
packages are seen and reported as available for download and applying.

I'm confused. I'm not seeing anything in any log files that would give me an 
indication that there is a problem. Of course, I may not be looking in the 
correct locations.


Configuration:

On the client side:
Client server: Fedora16
Spacewalk packages:

rhnsd-4.9.14-1.fc16.i686
rhn-check-1.7.8-1.fc16.noarch
rhn-setup-1.7.8-1.fc16.noarch
rhnlib-2.5.51-1.fc16.noarch
rhn-client-tools-1.7.8-1.fc16.noarch
yum-rhn-plugin-1.6.16-1.fc16.noarch
m2crypto-0.21.1-5.fc16.i686

Spacewalk Server:  RHEL6.2
Spacewalk database:  Postgresql

postgresql-server-8.4.9-1.el6_1.1.x86_64
spacewalk-backend-sql-postgresql-1.6.66-1.el6.noarch
postgresql-jdbc-8.4.701-3.el6.x86_64
postgresql-docs-8.4.9-1.el6_1.1.x86_64
spacewalk-java-postgresql-1.6.102-1.el6.noarch
spacewalk-postgresql-1.5.1-1.el6.noarch
postgresql-8.4.9-1.el6_1.1.x86_64
postgresql-libs-8.4.9-1.el6_1.1.x86_64
postgresql-devel-8.4.9-1.el6_1.1.x86_64
postgresql-odbc-08.04.0200-1.el6.x86_64

Spacewalk packages:

spacewalk-branding-1.6.4-1.el6.noarch
spacewalk-backend-sql-1.6.66-1.el6.noarch
spacewalk-search-1.6.8-1.el6.noarch
spacewalk-html-1.6.38-1.el6.noarch
spacewalk-backend-config-files-common-1.6.66-1.el6.noarch
spacewalk-backend-config-files-tool-1.6.66-1.el6.noarch
spacewalk-backend-tools-1.6.66-1.el6.noarch
spacewalk-java-lib-1.6.102-1.el6.noarch
spacewalk-sniglets-1.6.38-1.el6.noarch
spacewalk-config-1.6.4-1.el6.noarch
spacewalk-selinux-1.6.2-1.el6.noarch
spacewalk-remote-utils-1.6.8-1.el6.noarch
spacewalk-certs-tools-1.6.7-1.el6.noarch
spacewalk-backend-xmlrpc-1.6.66-1.el6.noarch
spacewalk-setup-1.6.5-1.el6.noarch
spacewalk-backend-iss-export-1.6.66-1.el6.noarch
spacewalk-common-1.5.1-1.el6.noarch
spacewalk-admin-1.6.3-1.el6.noarch
spacewalk-backend-sql-postgresql-1.6.66-1.el6.noarch
spacewalk-monitoring-selinux-1.6.2-1.el6.noarch
spacewalk-monitoring-1.4.1-1.el6.noarch
spacewalk-backend-iss-1.6.66-1.el6.noarch
spacewalk-pxt-1.6.38-1.el6.noarch
spacewalk-taskomatic-1.6.102-1.el6.noarch
spacewalk-backend-1.6.66-1.el6.noarch
spacewalk-backend-xp-1.6.66-1.el6.noarch
spacewalk-base-minimal-1.6.38-1.el6.noarch
spacewalk-backend-server-1.6.66-1.el6.noarch
spacecmd-1.6.11-1.el6.noarch
spacewalk-doc-indexes-1.1.1-1.el6.noarch
spacewalk-java-postgresql-1.6.102-1.el6.noarch
spacewalk-grail-1.6.38-1.el6.noarch
spacewalk-postgresql-1.5.1-1.el6.noarch
spacewalk-setup-jabberd-1.6.5-1.el6.noarch
spacewalk-backend-applet-1.6.66-1.el6.noarch
spacewalk-base-1.6.38-1.el6.noarch
spacewalk-java-1.6.102-1.el6.noarch
spacewalk-backend-libs-1.6.66-1.el6.noarch
spacewalk-schema-1.6.42-1.el6.noarch
spacewalk-java-config-1.6.102-1.el6.noarch
spacewalk-backend-xml-export-libs-1.6.66-1.el6.noarch
spacewalk-backend-config-files-1.6.66-1.el6.noarch
spacewalk-jpp-workaround-1.0.1-1.el6.noarch
spacewalk-backend-app-1.6.66-1.el6.noarch
spacewalk-backend-package-push-server-1.6.66-1.el6.noarch
perl-XML-NamespaceSupport-1.10-3.el6.noarch
spacewalk-slf4j-1.6.1-1.el6.noarch



Alan

Alan Pittman
Publix Super Markets, Inc.
863-686-8754 ext. 46320
alan.pitt...@publix.com<mailto:alan.pitt...@publix.com>

"Unix is user-friendly. It's just very selective about who its friends are."







___

[Spacewalk-list] Fedora 16 client not getting updates from Spacewalk 1.6

[Alan Pittman]

Hi.
 I've encountered an interesting issue with Spacewalk 1.6 and Fedora16. If I 
run yum check-update, the F16 client doesn't see the available packages in the 
Spacewalk repository. If I logon to the Spacewalk GUI, Spacewalk will report 
that there are available RPMs for updating.

 If I activate the fedora-updates.repo and run yum check-update, updated 
packages are seen and reported as available for download and applying.

I'm confused. I'm not seeing anything in any log files that would give me an 
indication that there is a problem. Of course, I may not be looking in the 
correct locations.


Configuration:

On the client side:
Client server: Fedora16
Spacewalk packages:

rhnsd-4.9.14-1.fc16.i686
rhn-check-1.7.8-1.fc16.noarch
rhn-setup-1.7.8-1.fc16.noarch
rhnlib-2.5.51-1.fc16.noarch
rhn-client-tools-1.7.8-1.fc16.noarch
yum-rhn-plugin-1.6.16-1.fc16.noarch
m2crypto-0.21.1-5.fc16.i686

Spacewalk Server:  RHEL6.2
Spacewalk database:  Postgresql

postgresql-server-8.4.9-1.el6_1.1.x86_64
spacewalk-backend-sql-postgresql-1.6.66-1.el6.noarch
postgresql-jdbc-8.4.701-3.el6.x86_64
postgresql-docs-8.4.9-1.el6_1.1.x86_64
spacewalk-java-postgresql-1.6.102-1.el6.noarch
spacewalk-postgresql-1.5.1-1.el6.noarch
postgresql-8.4.9-1.el6_1.1.x86_64
postgresql-libs-8.4.9-1.el6_1.1.x86_64
postgresql-devel-8.4.9-1.el6_1.1.x86_64
postgresql-odbc-08.04.0200-1.el6.x86_64

Spacewalk packages:

spacewalk-branding-1.6.4-1.el6.noarch
spacewalk-backend-sql-1.6.66-1.el6.noarch
spacewalk-search-1.6.8-1.el6.noarch
spacewalk-html-1.6.38-1.el6.noarch
spacewalk-backend-config-files-common-1.6.66-1.el6.noarch
spacewalk-backend-config-files-tool-1.6.66-1.el6.noarch
spacewalk-backend-tools-1.6.66-1.el6.noarch
spacewalk-java-lib-1.6.102-1.el6.noarch
spacewalk-sniglets-1.6.38-1.el6.noarch
spacewalk-config-1.6.4-1.el6.noarch
spacewalk-selinux-1.6.2-1.el6.noarch
spacewalk-remote-utils-1.6.8-1.el6.noarch
spacewalk-certs-tools-1.6.7-1.el6.noarch
spacewalk-backend-xmlrpc-1.6.66-1.el6.noarch
spacewalk-setup-1.6.5-1.el6.noarch
spacewalk-backend-iss-export-1.6.66-1.el6.noarch
spacewalk-common-1.5.1-1.el6.noarch
spacewalk-admin-1.6.3-1.el6.noarch
spacewalk-backend-sql-postgresql-1.6.66-1.el6.noarch
spacewalk-monitoring-selinux-1.6.2-1.el6.noarch
spacewalk-monitoring-1.4.1-1.el6.noarch
spacewalk-backend-iss-1.6.66-1.el6.noarch
spacewalk-pxt-1.6.38-1.el6.noarch
spacewalk-taskomatic-1.6.102-1.el6.noarch
spacewalk-backend-1.6.66-1.el6.noarch
spacewalk-backend-xp-1.6.66-1.el6.noarch
spacewalk-base-minimal-1.6.38-1.el6.noarch
spacewalk-backend-server-1.6.66-1.el6.noarch
spacecmd-1.6.11-1.el6.noarch
spacewalk-doc-indexes-1.1.1-1.el6.noarch
spacewalk-java-postgresql-1.6.102-1.el6.noarch
spacewalk-grail-1.6.38-1.el6.noarch
spacewalk-postgresql-1.5.1-1.el6.noarch
spacewalk-setup-jabberd-1.6.5-1.el6.noarch
spacewalk-backend-applet-1.6.66-1.el6.noarch
spacewalk-base-1.6.38-1.el6.noarch
spacewalk-java-1.6.102-1.el6.noarch
spacewalk-backend-libs-1.6.66-1.el6.noarch
spacewalk-schema-1.6.42-1.el6.noarch
spacewalk-java-config-1.6.102-1.el6.noarch
spacewalk-backend-xml-export-libs-1.6.66-1.el6.noarch
spacewalk-backend-config-files-1.6.66-1.el6.noarch
spacewalk-jpp-workaround-1.0.1-1.el6.noarch
spacewalk-backend-app-1.6.66-1.el6.noarch
spacewalk-backend-package-push-server-1.6.66-1.el6.noarch
perl-XML-NamespaceSupport-1.10-3.el6.noarch
spacewalk-slf4j-1.6.1-1.el6.noarch



Alan

Alan Pittman
Publix Super Markets, Inc.
863-686-8754 ext. 46320
alan.pitt...@publix.com

"Unix is user-friendly. It's just very selective about who its friends are."




___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] invalid byte sequence error

[Alan Pittman]

CC,
  I had the same issue. Did a Google search and found this:

https://www.redhat.com/archives/spacewalk-list/2011-July/msg00200.html

It appeared to fix the problem. I haven't tried applying the RPMs in question 
so I don't know if there are any
side effects.

Alan 

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Colin Coe
Sent: Thursday, December 15, 2011 5:22 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] invalid byte sequence error

Hi all

I'm seeing this error in the output from spacewalk-repo-sync.

---
Repo http://benwas1p.scada.horizonpower.com.au/mrepo/rhel5s-x86_64/RPMS.updates
has 12322 packages.
1/1 : redhat-logos-4.9.16-1-0.noarch
invalid byte sequence for encoding "UTF8": 0xa9
HINT:  This error can also happen if the byte sequence does not match
the encoding expected by the server, which is controlled by
"client_encoding".
---

Any ideas how I resolve it?

Thanks

CC

-- 
RHCE#805007969328369

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list