@darkz yu The error that you posted indicates some issue with your "monitor.py" python script. 'NoneType'object has no attribute 'modules' . Please try running that script manually to see if it works or causes the same error? Please make sure that it uses the PYTHONPATH that your ambari agent is using. # python monitor.py . For example the pythonpath i use as following: export PYTHONPATH=/usr/lib/python2.6/site-packages:/usr/lib/python2.6/site-packages/ambari_commons:/usr/lib/python2.6/site-packages:/usr/lib/python2.6/site-packages:/usr/lib/python2.6/site-packages/ambari_commons:/usr/lib/python2.6/site-packages::/usr/lib/python2.6/site-packages:/usr/lib/python2.6/site-packages/ambari_agent:/usr/lib/python2.6/site-packages . ... View more

@Sen Ke Good to know that the issue is resolved and you are able to access the Views via Knox now. It will be also great if you can mark this HCC thread as "Accepted", sothat other HCC users can quickly browse the answered solutions if they hit the same/simialr issue. ... View more

@Akshay Gupta What i see is... sometimes me too get the message and sandbox seems to be stuck there, But actually all it's functionality works well because most of its services like ssh and other are started till that point. "Started cleanup of temporary directories" . So you can continue to work with Ambari and other services .. even if the sandbox seems to be stuck. Sometimes it happens due to lack of resources (like RAM). So i keep the unwanted services in Maintenance Mode (stopped + Maintenance Mode) . ... View more

@Vinay MP The following Link, Describes why it was needed or why this feature was introduced: https://www.python.org/dev/peps/pep-0476/ . CVE-2014-9365 The Python standard library HTTP client modules (such as httplib or urllib) did not perform verification of TLS/SSL certificates when connecting to HTTPS servers. A man-in-the-middle attacker could use this flaw to hijack connections and eavesdrop or modify transferred data. ... View more

@Vinay MP Pleas echeck your python version . Is it "python-2.7.5" or higherif yes then should try to either downgrade the python version to lower than python-2.7.5 else it might causes this issue. [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:579) (OR) Else you will need to following the steps mentioned in the following doc to fix the "certificate verify failed (_ssl.c" issue while using RHEL7: Controlling and troubleshooting certificate verification https://access.redhat.com/articles/2039753#controlling-certificate-verification-7 . . The second option is safe as long as you do not want the certificate verification (or if you are in test environment). Otherwise it is highly discouraged to disable it. The verify=disable, ensures that the HTTPS certificate verification is disabled. You can verify the same using the Sample code mentioned in the above link to see if it works at your end. . With Python 2.7.9 release the default HTTPS behaviour has changed, which is now to always verify the remote HTTPS certificate to which you are initiating a connection. In the Python 2.7.9 release notes you can read more about the changes that made it in this release of Python, and PEP 476 provides the technical details and rationale about this change. ... View more

@Lukasz Szary Good to know that it's working now. It will be great if you can mark this HCC thread as Answered (Accepted) so that other HCC users can easily browse the answered threads when they encounter the similar error. ... View more

@Daniel Nicholas Good to know that the issue is resolved. Basically the setting "enabled=0" will temporarily disable the sandbox.repo as that repo seems to have some issues currently and hence causing 403 error. ... View more

@Juan Vares Good to know that the cluster is created fine now. Regarding the other issue of having old cluster names for few alerts: 14 sep 2017 15:29:38,717 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert nifi_status for an invalid cluster named cordisclu 14 sep 2017 15:29:38,717 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert ambari_agent_disk_usage for an invalid cluster named cordisclu . I think this might have happened, if the alert tables have some alert's targetting to the old cluster id. Please check and share the output of the following Queries on Ambari DB: # psql -U ambari ambari Password for user ambari: bigdata psql (9.2.18) Type "help" for help. ambari=> SELECT cluster_id, definition_name FROM alert_definition WHERE cluster_id NOT IN (SELECT cluster_id FROM cluster_version WHERE state = 'CURRENT'); ambari=> SELECT cluster_id, service_name FROM alert_group WHERE cluster_id NOT IN (SELECT cluster_id FROM cluster_version WHERE state = 'CURRENT'); ambari=> SELECT cluster_id, alert_label, alert_definition_id FROM alert_history WHERE cluster_id NOT IN (SELECT cluster_id FROM cluster_version WHERE state = 'CURRENT'); ambari=> SELECT cluster_id FROM cluster_version WHERE state = 'CURRENT'; . ... View more