Re: [Spacewalk-list] Pre-check before applyng packages

Am 13. März 2018 00:41:12 MEZ schrieb "Yakin, Francis" : >Is there any way that Spacewalk can do pre-check before applying any >packages on the clients. > >See my screen shot. > >Thanks > > >Francis Yakin | IT System Admin | direct: 510-749-2027 >500 Wind River Way,

Re: [Spacewalk-list] Upgrade/install packages in spacewalk

Just a quick one... How many clients are we talking about here ? By design, RH doesn't recommend or will pickup the actions instantly as if you would have 10k+ clients, it will trash down SW... That's why you have the checking interval by default 240 min and minimum is 60 min... I would not

Re: [Spacewalk-list] Spacewalk and AD/SSSD Based User Authentication

Try to go trough the SW/FreeIPA documentation (https://github.com/spacewalkproject/spacewalk/wiki/SpacewalkAndIPA) DON'T COPY PASTE, read, understand and skip the parts of ipa installation and config as you already have sssd up and running so that should be sufficient. Take a backup before you

Re: [Spacewalk-list] Spacewalk and AD/SSSD Based User Authentication

SW 2.7 on RHEL 7.4 The HTTPD conf files are either commented out, or in the case of auth_kerb.conf, empty. This is a completely out of the box setup and the only documentation I’ve been able to find on this on RH’s portal mentions just the config changes I made. Nothing to do with the files

Re: [Spacewalk-list] Upgrade/install packages in spacewalk

Here is the screenshot Francis -Original Message- From: Yakin, Francis Sent: Monday, March 12, 2018 11:25 AM To: spacewalk-list@redhat.com; Robert Paschedag Subject: RE: [Spacewalk-list] Upgrade/install packages in spacewalk Here is the screenshot As you can see that "This action

Re: [Spacewalk-list] Upgrade/install packages in spacewalk

Here is the screenshot As you can see that "This action scheduled after 3/12/18 11:06:00 AM PDT" But, the client picked up this action on 3/12/18 aa:09 AM Why the client picked up 3 mins after 11:06 AM? Can we bypass the scheduling and apply the actions immediately? Thanks Francis

Re: [Spacewalk-list] Spacewalk and AD/SSSD Based User Authentication

Spacewalk version and OS please... Also log entries except the tomcat would be helpful. What's the content of following: /etc/httpd/conf.d/intercept_form_submit.conf /etc/httpd/conf.d/ authnz_pam.conf /etc/httpd/conf.d/ auth_kerb.conf I don't think that you need to create the user if you

Re: [Spacewalk-list] osa-dispatcher fails to start

Can you provide the entries after a "/etc/init.d/osa-dispatcher restart" from /var/log/rhn/osa-dispatcher.log ? /Alex From: "Daryl Rose" To: spacewalk-list@redhat.com Sent: Monday, March 12, 2018 4:28:18 PM Subject: Re: [Spacewalk-list] osa-dispatcher fails to

Re: [Spacewalk-list] Upgrade/install packages in spacewalk

>>The picture doesn't tell very much. If osad is installed on the client, then >>there is something broken here. >>Try to stop osad on the client, remove /etc/sysconfig/rhn/osad-auth and start >>it again. >>Check in SW GUI that the osad status is "online" and try to ping it from >>there. Then

[Spacewalk-list] spacewalk-remote-utils RPM

Greetings. Is the spacewalk-remote-utils RPM still getting updates? I checked over at koji, but the latest one is from August 2017 (7u3). If not, is there another source for the files under /usr/share/rhn/channel-data? ___ Spacewalk-list mailing list

[Spacewalk-list] Spacewalk and AD/SSSD Based User Authentication

Hi! I'm looking to potentially use SSSD and Active Directory to authenticate our users to Spacewalk. The Spacewalk server is already on the domain and we authenticate just fine via SSH using AD. I added the following to the rhn.conf file: pam_auth_service = spacewalk-satellite Created the

Re: [Spacewalk-list] osa-dispatcher fails to start

I'm sorry, I just realized that I should have provided more information. 1. This is a RHEL 6.8 server 2. SW v2.6. Also, we use a signed cert and the certificate expired January. I inquired on this list and I was told that I only needed to update the cert for the website portion of the

[Spacewalk-list] osa-dispatcher fails to start

osa-dispatcher is down and won't start. I get the following error when trying to start it: Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Traceback caught:',) Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',) ERROR: unhandled exception occurred: (can't