@Joshva Peter If this helped answering your query then it will be great if you mark this thread as "Answered" by clicking on the "Accepted" link, that way it will be helpful for HCC users to quickly find the answered threads. ... View more

@david garcia You are getting the error: Caused by: java.security.cert.CertificateException: No name matching master1.xxx.yyyy.net found Please check the Certificate CN (Common Name) that you used to create the certificate. It should be the same as hostname teing used in the URL while accessing the service component. If the CN in the certificate is not the same as the hostname of the component, you will get the error "java.security.cert.CertificateException: No name matching <host_name> found", where , "host_name" is the host name you used as part of the URL in your client application. (Here client is hive view) . Please not that, you cannot change the CN in an already created certificate. So you will need to create a new certificate with the correct hostname of the service. ... View more

@Hovo Khachikyan Looks like some N/W configuration issue at your end which might be blocking access to few specific sites Or the mirrorlist is not connecting from your side. I can access the same repo without any issue locally: Example: [root@standalone1 tmp]# wget "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os" --2017-07-17 13:34:17-- http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os Resolving mirrorlist.centos.org (mirrorlist.centos.org)... 85.236.43.108, 212.69.166.138, 216.176.179.218, ... Connecting to mirrorlist.centos.org (mirrorlist.centos.org)|85.236.43.108|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 493 [text/plain] Saving to: ‘index.html?release=6&arch=x86_64&repo=os’ 100%[==================================================================================================================================================================================================>] 493 --.-K/s in 0s 2017-07-17 13:34:17 (54.8 MB/s) - ‘index.html?release=6&arch=x86_64&repo=os’ saved [493/493] . . [root@standalone1 tmp]# cat index.html\?release\=6\&arch\=x86_64\&repo\=os http://mirror.oss.ou.edu/centos/6.9/os/x86_64/ http://centos.firehosted.com/6.9/os/x86_64/ http://mirrors.ocf.berkeley.edu/centos/6.9/os/x86_64/ http://mirror.ancl.hawaii.edu/linux/centos/6.9/os/x86_64/ http://lug.mtu.edu/centos/6.9/os/x86_64/ http://centos.host-engine.com/6.9/os/x86_64/ http://mirror.millry.co/CentOS/6.9/os/x86_64/ http://mirror.teklinks.com/centos/6.9/os/x86_64/ http://centos.mirrors.tds.net/pub/linux/centos/6.9/os/x86_64/ http://mirrors.cmich.edu/centos/6.9/os/x86_64/ . ... View more

@Rohit Sharma If all those stale alerts are coming from any particular host then you will need to check the hostname which is causing the stale alert. # curl -i -H "X-Requested-By: ambari"-u admin:admin -X GET http://AMBARI_SERVER_HOST:8080/api/v1/hosts . Please list all the hosts using the above curl command (or by opening the mentioned URL in the browser, Where you have logged in to ambari UI) and then match the hosts list to findout if by mistake any unwanted host is being registered. Some times old host can have the ambari-agent.ini entry to point to ambari server. . ... View more