1 of 1 people found this helpful
I would leave the offline catalog as it is. Not that it will not work if we convert to online, but just to avoid any confusions and problems.
Yes, create a new online catalog, and use the same repository path which you had configured for offline, This way you will not end up in downloading payloads that are already present in your repositry path.
Hope this helps.
Thankyou for the info, I will try it out and update how it goes.
I am getting the following warning messages when I am trying to update my catalog online
Error while downloading payload for hotfix : Windows6.1-2008-R2-SP1-KB2632503-x64.msu-MSWU-586-en-WINDOWS WEB SERVER 2008 R2 (X64)-SP1, com.bmc.sa.patchfeed.FeedException: Maximum retries completed. Failed to download http://download.microsoft.com/download/7/E/F/7EF75D39-F8B4-4401-8F8C-A2AB52673D0D/Windows6.1-KB2632503-x64.msu
I can manually download the patches by clicking the link from these warning messages on the same app server.
Also similar problem with Online Linux Catalog Update
Error while downloading payload for rpm : yum-updateonboot-1.1.16-21.el5.noarch.rpm, com.bmc.sa.patchfeed.FeedException: Error occurred while logging to RHN.
I can access RHN site with the user and password I have for RHN from my app server and download the RPM's
Do you have a proxy setting up in your browser from which you are able to access ?
If not , what is in the app server log?
Yes I have a proxy setup on the browser and I ave configured the proxy in application in Patch configuration.
I created an online catalog for SQL 2008 after configuring proxy in patch configuration in application.
But when I try to update Windows or Linux Catlog I am getting this error.
After couple of tries windows patch catlog update is resolved, new patches are downloaded and catlog is updated.
When trying to update Liinux (Redhat 5 x86) Patch catalog update, I am seeing the following error and catalog update fails
"Error while updating feed: Either service is Unavailable or credentials are Invalid. Failed to connect to RHN xml rpc server"
I can manually log in to the server using the RHN credentials which I have.
1 of 1 people found this helpful
If you have selected the correct proxy settings, it should work. What is the type of proxy u have?
Can u paste ur global patch config?
Also, where have u specified the rhn credentials
In global config?
Sent from my iPhone
I am using NTLMv2 proxy and the same proxy configuration for Windows Patch Update works.
I have specified RH credentials in Catalog and forgot to update it in GLobal config, which I have done now.
Now when I am trying to update the redhat catalog I can see the following warning messages in appserver.log
[25 Feb 2012 21:11:38,071] [PSU-Thread-14] [WARN] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] Cookie rejected: "$Version=0; JSESSIONID=672BB4261285C0D9D9F0E857FDAB7229; $Path=/rhn". Illegal path attribute "/rhn". Path of origin: "/rpc/api"
[25 Feb 2012 21:11:38,086] [PSU-Thread-18] [WARN] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] Cookie rejected: "$Version=0; JSESSIONID=82DA696DE9C2AD0A6CDBE66F9AD9208C; $Path=/rhn". Illegal path attribute "/rhn". Path of origin: "/rpc/api"
[25 Feb 2012 21:11:38,086] [PSU-Thread-15] [INFO] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] Response content length is not known
[25 Feb 2012 21:11:38,118] [PSU-Thread-20] [INFO] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] Response content length is not known
And in CUJ Result window following warning messages are shown and job fails
Error occurred while fetching the meta data for errata advisory - RHEA-2012:0298, Caught exception while executing method "errata.listPackages": Failed to parse servers response: Expected methodResponse element, got HTML
I have attached the screenshot Catlog update Job window below, In filter I have set download by ERRATA
Check your proxy logs, it can be the case that the proxy is blocking rhn network for some security reasons .
I got this working after some troubleshooting on proxy and patch global configuration. Now Online catalog works both for windows and linux.
What was the problem ? Specially with Patch Global Config ?
Rohit, Sorry for delay in reply. The Problem was with proxy, we are using NTLM-v2 and this is what I had configured in Patch global configuration. But as there were other issues also and while troubleshhoting somehow the proxy was changed to NTLM during troubleshooting.
Debug was enabled for troubleshooting and there I identified the the problem, I reconfigured the patch global configuration with correct setting and it worked like a charm
Thanks for your help, it is appreciated.