Security patches update procedure
Dear Team ,
I register the system through subscription manager but I am unable to update the security patches.
I would like to know what the procedure ot steps
some results i mention it help for you,
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.08.11 10:46:42 =~=~=~=~=~=~=~=~=~=~=~=
login as: 172 root
root@172.16.165.246's password:
Last login: Fri Aug 11 16:13:30 2017 from 172.17.114.11
]0;root@grnlinux-246:~[?1034h[root@grnlinux-246 ~]# subscription-manager list --available
+-------------------------------------------+
Available Subscriptions
+-------------------------------------------+
ProductName: Red Hat Enterprise Linux Server, Standard (4 sockets) (Up
to 1 guest)
ProductId: RH0125194F3RN
PoolId: 8a85f9894e813307014eb96e93701fd4
Quantity: 1
Multi-Entitlement: No
Expires: 05/11/2018
MachineType: physical
]0;root@grnlinux-246:~[root@grnlinux-246 ~]# subscription-manager config
Usage: subscription-manager config [OPTIONS]
List, set, or remove the configuration parameters in use by this machine.
Options:
-h, --help show this help message and exit
--list list the configuration for this system
--remove=REMOVE remove configuration entry by section.name
--server.hostname=SERVER.HOSTNAME
Section: server, Name: hostname
--server.prefix=SERVER.PREFIX
Section: server, Name: prefix
--server.port=SERVER.PORT
Section: server, Name: port
--server.insecure=SERVER.INSECURE
Section: server, Name: insecure
--server.ssl_verify_depth=SERVER.SSL_VERIFY_DEPTH
Section: server, Name: ssl_verify_depth
--server.ca_cert_dir=SERVER.CA_CERT_DIR
Section: server, Name: ca_cert_dir
--server.proxy_hostname=SERVER.PROXY_HOSTNAME
Section: server, Name: proxy_hostname
--server.proxy_port=SERVER.PROXY_PORT
Section: server, Name: proxy_port
--server.proxy_user=SERVER.PROXY_USER
Section: server, Name: proxy_user
--server.proxy_password=SERVER.PROXY_PASSWORD
Section: server, Name: proxy_password
--server.repo_ca_cert=SERVER.REPO_CA_CERT
Section: server, Name: repo_ca_cert
--rhsm.baseurl=RHSM.BASEURL
Section: rhsm, Name: baseurl
--rhsm.repo_ca_cert=RHSM.REPO_CA_CERT
Section: rhsm, Name: repo_ca_cert
--rhsm.productcertdir=RHSM.PRODUCTCERTDIR
Section: rhsm, Name: productcertdir
--rhsm.entitlementcertdir=RHSM.ENTITLEMENTCERTDIR
Section: rhsm, Name: entitlementcertdir
--rhsm.consumercertdir=RHSM.CONSUMERCERTDIR
Section: rhsm, Name: consumercertdir
--rhsm.proxy_hostname=RHSM.PROXY_HOSTNAME
Section: rhsm, Name: proxy_hostname
--rhsm.insecure=RHSM.INSECURE
Section: rhsm, Name: insecure
--rhsm.ssl_verify_depth=RHSM.SSL_VERIFY_DEPTH
Section: rhsm, Name: ssl_verify_depth
--rhsm.proxy_password=RHSM.PROXY_PASSWORD
Section: rhsm, Name: proxy_password
--rhsm.proxy_port=RHSM.PROXY_PORT
Section: rhsm, Name: proxy_port
--rhsm.prefix=RHSM.PREFIX
Section: rhsm, Name: prefix
--rhsm.port=RHSM.PORT
Section: rhsm, Name: port
--rhsm.proxy_user=RHSM.PROXY_USER
Section: rhsm, Name: proxy_user
--rhsm.hostname=RHSM.HOSTNAME
Section: rhsm, Name: hostname
--rhsm.ca_cert_dir=RHSM.CA_CERT_DIR
Section: rhsm, Name: ca_cert_dir
--rhsmcertd.certfrequency=RHSMCERTD.CERTFREQUENCY
Section: rhsmcertd, Name: certfrequency
--rhsmcertd.healfrequency=RHSMCERTD.HEALFREQUENCY
Section: rhsmcertd, Name: healfrequency
--rhsmcertd.proxy_hostname=RHSMCERTD.PROXY_HOSTNAME
Section: rhsmcertd, Name: proxy_hostname
--rhsmcertd.insecure=RHSMCERTD.INSECURE
Section: rhsmcertd, Name: insecure
--rhsmcertd.ssl_verify_depth=RHSMCERTD.SSL_VERIFY_DEPTH
Section: rhsmcertd, Name: ssl_verify_depth
--rhsmcertd.proxy_password=RHSMCERTD.PROXY_PASSWORD
Section: rhsmcertd, Name: proxy_password
--rhsmcertd.proxy_port=RHSMCERTD.PROXY_PORT
Section: rhsmcertd, Name: proxy_port
--rhsmcertd.prefix=RHSMCERTD.PREFIX
Section: rhsmcertd, Name: prefix
--rhsmcertd.repo_ca_cert=RHSMCERTD.REPO_CA_CERT
Section: rhsmcertd, Name: repo_ca_cert
--rhsmcertd.port=RHSMCERTD.PORT
Section: rhsmcertd, Name: port
--rhsmcertd.proxy_user=RHSMCERTD.PROXY_USER
Section: rhsmcertd, Name: proxy_user
--rhsmcertd.hostname=RHSMCERTD.HOSTNAME
Section: rhsmcertd, Name: hostname
--rhsmcertd.ca_cert_dir=RHSMCERTD.CA_CERT_DIR
Section: rhsmcertd, Name: ca_cert_dir
]0;root@grnlinux-246:~[root@grnlinux-246 ~]# ll /etc/pki/product
total 4
-rw-r--r--. 1 root root 2171 Aug 10 01:08 71.pem
]0;root@grnlinux-246:~[root@grnlinux-246 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 6.2 (Santiago)
]0;root@grnlinux-246:~[root@grnlinux-246 ~]# uname -a
Linux grnlinux-246 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
]0;root@grnlinux-246:~[root@grnlinux-246 ~]# logout
Responses
You posted the same three times ... click on "Edit" under the two posts below, delete the content and provide the output from sudo subscription-manager repos --list-enabled in one of the posts and sudo yum repolist in the other post. It provides the information whether your subscription is properly attached to the operating system and which of the available repositories are enabled there.
Thanks :)
Christian
Hi,
Please look into Formatting Help and try to format your posts.
With code blocks your posts are a lot easier to read and maybe more people are willing to help you.
Thanks,
Jörg
Adding further to Christian reply.....
You could run the command "subscription-manager list" to check if the system is subscribed or not, run "subscription-manager list --available" to see available subscriptions.
If you could see that your system is subscribed then you could find out and enable respective repos as required. To list out all repos matching your subscription, run the command "subscription-manager repos --list" , so to enable "Red Hat Enterprise Linux High Availability (for RHEL 7 Server) (RPMs)" you could run "subscription-manager repos --enable rhel-ha-for-rhel-7-server-rpms".. like this.
Hi Virendra,
Please attach the subscription as I explained it above.
In case there are problems execute these commands :
sudo subscription-manager remove --allsudo subscription-manager unregistersudo subscription-manager clean
Then repeat the commands from my response above :
sudo subscription-manager registersudo subscription-manager refreshsudo subscription-manager attach --auto
Regards,
Christian
Please ask your organization admin if the subscription is entitled to only be used on one physical machine and if it is already attached to another physical system. In this case it cannot work here.
Ask him to how many virtual systems it can be attached and when there is a free option, you can install the system in a virtual machine and then attach the subscription properly inside that VM.
Regards,
Christian
Hi Jan Gerrit,
This shows all available repositories, disabled and enabled ones and as Virendra seems to be a not so experienced user, it might be a bit confusing for him to recognize the differences. Important is (IMHO) that the subscription is attached, then to check which repositories are enabled, then to update the system and after that eventually add additional repositories.
Regards,
Christian
Interesting point ... I have no idea if it's different in RHEL 6, the only description that I can find is
Manually attaching and removing subscriptions through the command line ... but who knows ... :)
Regards,
Christian
Unfortunately I am running out of ideas now. If you have a valid subscription, it simply should work.
Maybe you find something in the Product Documentation for Red Hat Subscription Management ...
Regards,
Christian
Hello Virendra,
Can you open the menu subscriptions on https://access.redhat.com (on top of the start page)? If so does your organization have active subscriptions? If you are not allowed to open the menu, you need to contact your software asset manager (the person responsible to buy Red Hat subscriptions and ask him/her to verify if subscriptions are still available).
Regards,
Jan Gerrit
Jan Gerrit seems to be right, the command is a little bit different on RHEL 6 as you can see in your own output of subscription-manager --help you are providing, so please try out the following :
sudo subscription-manager unsubscribesudo subscription-manager unregistersudo subscription-manager clean
sudo subscription-manager registersudo subscription-manager refreshsudo subscription-manager subscribe --auto
sudo subscription-manager listsudo subscription-manager repos
Good luck !
Christian :)
Virendra, I see that your system is registered but there are no subscriptions attached, so you may need to try manually attaching using the pool id 8a85f9894e813307014eb96e93701fd4 (as per your comments) as shown below:
subscription-manager attach --pool=8a85f9894e813307014eb96e93701fd4
If the pool ID is already being used then you would see a message which confirms that this subscription is already applied on a different system as shown below:
[root@managed1 ~]# subscription-manager attach --pool=8a85f981576we456c15ac67c139e5dae
No subscriptions are available from the pool with ID '8a85f981576we456c15ac67c139e5dae'.
Otherwise, you should a successful message like this:
[root@managed1 ~]# subscription-manager attach --pool=8a85f9815ac3wert112bb88c13d25de1
Successfully attached a subscription for: Red Hat Enterprise Linux Developer Suite
After this if you run the command "subscription-manager list" it should show the status as shown below :
[root@managed1 ~]# subscription-manager list
+-------------------------------------------+
Installed Product Status
+-------------------------------------------+
Product Name: Red Hat Enterprise Linux Server
Product ID: 69
Version: 7.4 Beta
Arch: x86_64
Status: Subscribed
Status Details:
Starts: 03/13/2017
Ends: 03/12/2018
Later, to see the list of enabled repos:
[root@managed1 ~]# subscription-manager repos --list-enabled
+----------------------------------------------------------+
Available Repositories in /etc/yum.repos.d/redhat.repo
+----------------------------------------------------------+
Repo ID: rhel-7-server-rt-beta-rpms
Repo Name: Red Hat Enterprise Linux for Real Time Beta (RHEL 7 Server) (RPMs)
Repo URL: https://cdn.redhat.com/content/beta/rhel/server/7/$basearch/rt/os
Enabled: 1
Repo ID: rhel-7-server-rpms
Repo Name: Red Hat Enterprise Linux 7 Server (RPMs)
Repo URL: https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
Enabled: 1
Repo ID: rhel-7-server-rt-rpms
Repo Name: Red Hat Enterprise Linux for Real Time (RHEL 7 Server) (RPMs)
Repo URL: https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/rt/os
Enabled: 1
At this stage, you should be successful in getting the repos populated, run the command "yum repolist", it should show up the list Later, you could run "yum " command to install or update required packages.
As this is RHEL6.2, not sure why "--auto" parameter is not working, anyways try to attach manually as explained here and check if that helps. Also, whenever you paste command outputs try following "Formating help", so that it gives better readability. All the best!!!
Dear Virendra,
Why do you post the --help messages over and over again ? It doesn't help you or anybody else - the opposite is the case - it prevents other users reading it from being interested. Please note what Jörg Kastning told you earlier and make your posts better readable. Also did you check what I wrote here : https://access.redhat.com/discussions/3155791#comment-1208221 ? Please help us to help you ! :)
Thanks :)
Christian
I could see that there is an error reported while you manually try to attach subscription..
[root@grnlinux-247 ~]# subscription-manager subscribe --pool=8a85f9894e813307014 eb96e93701fd4 Too many content sets for certificate Red Hat Enterprise Linux Server, Standard (4 sockets) (Up to 1 guest). A newer client may be available to address this pro blem. See kbase https://access.redhat.com/knowledge/node/129003 for more informa tion.
You would need to update your subscription-manager package, please refer this Red Hat KB : https://access.redhat.com/solutions/1534943
Once subscription-manager package is update, try out the same steps.. Keep in mind to format your command output messages as Christian said to give better readability. All the best!
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
