hwasilicon.blogg.se

Rhn satellite patch management
Rhn satellite patch management













We use the default Library life cycle environment.įrom what I gathered online, I can either go to each server and do yum update, or do it from the UI, and the server will be patched. Both products have content views that include the product repos, repos sync’ed, published and promoted once, so on v1 now. What we have currently (Configured by vendor):Ģ products for our RH6 and RH7 servers, those servers are hosting some applications our business needs. Life cycle environments, content views, and most importantly, what exactly are we supposed to do each time we need to install patches? I have read as much as I can about satellite to get us through this, but it still make no sense to me. We have RH Satellite in place and we want to use it to install updates on our small Linux environment (100 servers). Root:homevm:~:# scp /var/I am sorry if this has been asked before. Root:homevm:~:# openssl x509 -in /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT -noout -dates Subject= /C=US/ST=CA/L=SanFrancisco/O=/OU=/CN=

rhn satellite patch management

Root:homevm:~:# openssl x509 -in /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT -noout -subject Copy RHN certificate from satellite server to client, make sure the cert has not expired and the CN matches server name. OSA is picky on SSL certificte verification, make sure the right CA cert is deployed on client, and the serverURL on up2date should match with the CN on the server certificate.ġ. Client : Make sure the deploy and run options are enabled –Įxtra steps in case you encounter SSL certificate issues –

rhn satellite patch management rhn satellite patch management

Client : Install and enable osad (OSA daemon).ģ. Osa-dispatcher 0:off 1:off 2:on 3:on 4:on 5:on 6:offĢ. Root:homevm:~:# chkconfig osa-dispatcher -list Root:homevm:~:# chkconfig osa-dispatcher on Root:homevm:~:# service osa-dispatcher status

rhn satellite patch management

For instance, if a remote command is set to be executed on client or a patch is waiting to be applied, rhn_check has to wait at least for 60 minutes to pick up the task.įor real time command execution or patch or configuration deployment, the following steps have to be performed on server and client – Redhat satellite or Spacewalk – real time push to clients.īy default, a client waits for a set of interval (minutes) configured in /etc/sysconfig/rhn/rhnsd to pull scheduled tasks from satellite server.















Rhn satellite patch management