Re: [Spacewalk-list] Oddball question about Spacewalk possibly corrupting yum update

[Robert Paschedag]

Hi Paul,

the clients you pointed to the other repo... These were also systems with X? 
Add there were no errors?

I could only think of possible mismatch of packages within the wrong repos on 
spacewalk (for example CentOS 6 packages within a CentOS 7 Channel... what 
could happen if you accidently made an error when mapping repos to channels.)

Another error could be a broken package within the channel that causes that 
issue. I only had that once, that I had 2 times the same package (with 
identical name and version but different content and size Until now, I 
don't know, how this could happen). The update always downloaded the wrong 
package that broke the update. I had to manually remove that broken package 
from spacewalk.

You're only chance is to run the update manually in verbose mode to see, what 
packages (and versions) get downloaded. Also save the Apache logfile to see, if 
there have been issues.

Then compare this to the list of packages when updating from the non-spacewalk 
repo.

Good luck.

Robert


⁣sent from my mobile device​


 Originale Nachricht 
Von: Paul Greene 
Gesendet: Wed Jun 19 17:59:47 GMT+02:00 2019
An: "spacewalk-list@redhat.com" 
Betreff: [Spacewalk-list] Oddball question about Spacewalk possibly 
corrupting yum update

I built a Spacewalk 2.7 server for managing a couple hundred CentOS 6
workstations, and synced it to a local yum repository.

After a few months I started adding some CentOS 7 systems to the mix, and
also synced to the same local yum repository (same server, different path
to the repositories, of course).

The Spacewalk server always seemed to have an issue getting a successful
full sync with the CentOS 7 local repository after the 7.6 series came out.
I wasn't concerned at first because the systems were configured to go to
the local yum repository anyway (configured in /etc/yum.repos.d).

After the CentOS 7.6 series came out, I started having an issue with any
machine that got the 7.6 updates where the system would freeze and lock up,
requiring a hard reboot to get it usable again. That happened on at least a
daily basis and sometimes multiple times a day. I rolled those users back
to CentOS 7.5 to get them a functioning stable machine again, and didn't
update anybody that was running 7.5. It seemed definitely related to X
windows - I could still go to a command prompt with ctrl-alt-f2 and work
from a command prompt, but X windows wouldn't come back without a hard
reboot. On a couple of servers that didn't need X windows and had the run
level set to multi-user.target, they didn't have an issue - it was only the
workstations that needed X windows.

I have access to another yum repository independent of the Spacewalk
server, and noticed if I updated a workstation to that repository and did
NOT join the machine to the Spacewalk server, they all ran fine with CentOS
7.6. As long as I didn't join them to the Spacewalk server there were no
issues. I tried deleting the CentOS 7 yum repository from the Spacewalk
server, thinking maybe the yum repository on the Spacewalk server had
gotten corrupted and was pushing out some bad files, but that didn't work.

The systems still seem to be looking to the Spacewalk server for updates,
regardless of what is in /etc/yum.repos.d.

Hopefully someone else has seen something like this before. I would either
like to remove any and all yum configurations from the Spacewalk server, if
possible, and just point to the local yum repository for any kind of
updates.

Barring that, I'm interested in updating to Spacewalk 2.9 anyway, and would
build a new 2.9 server, migrate everything over to that, and leave out any
yum repository configuration at all on that new server.

The CentOS 6 systems are fine - no issues at all with updates and/or yum
repositories.

Thanks,

PG




___
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] Oddball question about Spacewalk possibly corrupting yum update

[Paul Greene]

I built a Spacewalk 2.7 server for managing a couple hundred CentOS 6
workstations, and synced it to a local yum repository.

After a few months I started adding some CentOS 7 systems to the mix, and
also synced to the same local yum repository (same server, different path
to the repositories, of course).

The Spacewalk server always seemed to have an issue getting a successful
full sync with the CentOS 7 local repository after the 7.6 series came out.
I wasn't concerned at first because the systems were configured to go to
the local yum repository anyway (configured in /etc/yum.repos.d).

After the CentOS 7.6 series came out, I started having an issue with any
machine that got the 7.6 updates where the system would freeze and lock up,
requiring a hard reboot to get it usable again. That happened on at least a
daily basis and sometimes multiple times a day. I rolled those users back
to CentOS 7.5 to get them a functioning stable machine again, and didn't
update anybody that was running 7.5. It seemed definitely related to X
windows - I could still go to a command prompt with ctrl-alt-f2 and work
from a command prompt, but X windows wouldn't come back without a hard
reboot. On a couple of servers that didn't need X windows and had the run
level set to multi-user.target, they didn't have an issue - it was only the
workstations that needed X windows.

I have access to another yum repository independent of the Spacewalk
server, and noticed if I updated a workstation to that repository and did
NOT join the machine to the Spacewalk server, they all ran fine with CentOS
7.6. As long as I didn't join them to the Spacewalk server there were no
issues. I tried deleting the CentOS 7 yum repository from the Spacewalk
server, thinking maybe the yum repository on the Spacewalk server had
gotten corrupted and was pushing out some bad files, but that didn't work.

The systems still seem to be looking to the Spacewalk server for updates,
regardless of what is in /etc/yum.repos.d.

Hopefully someone else has seen something like this before. I would either
like to remove any and all yum configurations from the Spacewalk server, if
possible, and just point to the local yum repository for any kind of
updates.

Barring that, I'm interested in updating to Spacewalk 2.9 anyway, and would
build a new 2.9 server, migrate everything over to that, and leave out any
yum repository configuration at all on that new server.

The CentOS 6 systems are fine - no issues at all with updates and/or yum
repositories.

Thanks,

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

Re: [Spacewalk-list] [External] Re: setting up master and slave spacewalk server for different locations

[Mukherjee, Debayan]

Hi Michael,



Thanks for the information, still confused ☹.

Can we initiate the patching for the slave's client servers from master server?

How does it work, any reference?





Thanks!



Regards,

Debayan Mukherjee



-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Michael Mraka
Sent: Wednesday, June 19, 2019 4:43 PM
To: spacewalk-list@redhat.com
Cc: Lingayya, Shanker 
Subject: [External] Re: [Spacewalk-list] setting up master and slave spacewalk 
server for different locations



This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links 
and attachments.



Mukherjee, Debayan:

> Hi Team,

>

> Can we set up a master server in a location and slave in some other?

> We have an infrastructure which is scattered all over the globe and to speed 
> up the patchup process through network a spacewalk slave server also will be 
> needed in that particular location. Is it possible? (below is the image) , if 
> anyone has the process then it will be of great help.



https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_documentation_en-2Dus_red-5Fhat-5Fsatellite_5.8_html_installation-5Fguide_chap-2Dsynchronization-5Fbetween-5Fmultiple-5Fsatellites=DwIGaQ=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU=kjYgKXRvPKJ-1Spwl9FaKBV5WMz2rUyGBr-Fiqe550E=rC3mQ6gJslvPixUW2w94J4DOXHUGjyMLbSMIoTND4YA=gUOi5_nqKY30CUr83vzcaJ9j0meTiBV-fWqFkho2x5s=



> Will the slave be working as same as the master spacewalk server and support 
> all the Linux distros?



Yes.



> [cid:image001.png@01D526B9.99B6D8C0]

> Thanks!

>

> Regards,

> Debayan Mukherjee



Regards,



--

Michael Mráka

System Management Engineering, Red Hat



___

Spacewalk-list mailing list

Spacewalk-list@redhat.com

https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_mailman_listinfo_spacewalk-2Dlist=DwIGaQ=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU=kjYgKXRvPKJ-1Spwl9FaKBV5WMz2rUyGBr-Fiqe550E=rC3mQ6gJslvPixUW2w94J4DOXHUGjyMLbSMIoTND4YA=JYTUn3nGDpSbumoE3BnIQ-zfM7ruRy5feuf2zqv-4-Q=



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy. Your privacy is important to us. Accenture uses your personal data only 
in compliance with data protection laws. For further information on how 
Accenture processes your personal data, please see our privacy statement at 
https://www.accenture.com/us-en/privacy-policy.
__

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

Re: [Spacewalk-list] setting up master and slave spacewalk server for different locations

[Michael Mraka]

Mukherjee, Debayan:
> Hi Team,
> 
> Can we set up a master server in a location and slave in some other?
> We have an infrastructure which is scattered all over the globe and to speed 
> up the patchup process through network a spacewalk slave server also will be 
> needed in that particular location. Is it possible? (below is the image) , if 
> anyone has the process then it will be of great help.

https://access.redhat.com/documentation/en-us/red_hat_satellite/5.8/html/installation_guide/chap-synchronization_between_multiple_satellites

> Will the slave be working as same as the master spacewalk server and support 
> all the Linux distros?

Yes.

> [cid:image001.png@01D526B9.99B6D8C0]
> Thanks!
> 
> Regards,
> Debayan Mukherjee

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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