Siddharth Wagle created AMBARI-13193:
----------------------------------------

             Summary: Metrics Monitor Start fails after manually enabling 
kerberos
                 Key: AMBARI-13193
                 URL: https://issues.apache.org/jira/browse/AMBARI-13193
             Project: Ambari
          Issue Type: Bug
          Components: ambari-metrics
    Affects Versions: 2.1.2
            Reporter: Siddharth Wagle
            Assignee: Siddharth Wagle
             Fix For: 2.1.2


This was encountered while trying to enable security manually.
Installed and Configured kdc, prepared JCE and then at the UI selected manual 
kerberos, downloaded csv file. Executed kerberos-setup.sh so that creation of 
principals and key tabs will be taken care. Proceed through the wizard to 
complete kerberization. But start services fails at Metrics monitor start with 
the below error:
{code}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
 line 58, in <module>
    AmsMonitor().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 219, in execute
    method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
 line 40, in start
    action = 'start'
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
line 89, in thunk
    return fn(*args, **kwargs)
  File 
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py",
 line 83, in ams_service
    user=params.ams_user
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 154, in __init__
    self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 152, in run
    self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 118, in run_action
    provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 258, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 70, in inner
    result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 92, in checked_call
    tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 140, in _call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 291, in _call
    raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 
'/usr/sbin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf/ 
start' returned 255. psutil build directory is not empty, continuing...
Verifying Python version compatibility...
Using python  /usr/bin/python2.6
Checking for previously running Metric Monitor...
Starting ambari-metrics-monitor
Verifying ambari-metrics-monitor process status...
ERROR: ambari-metrics-monitor start failed. For more details, see 
/var/log/ambari-metrics-monitor/ambari-metrics-monitor.out:
====================
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/resource_monitoring/main.py", line 27, 
in <module>
    from core.controller import Controller
  File 
"/usr/lib/python2.6/site-packages/resource_monitoring/core/controller.py", line 
28, in <module>
    from metric_collector import MetricsCollector
  File 
"/usr/lib/python2.6/site-packages/resource_monitoring/core/metric_collector.py",
 line 23, in <module>
    from host_info import HostInfo
  File 
"/usr/lib/python2.6/site-packages/resource_monitoring/core/host_info.py", line 
22, in <module>
    import psutil
ImportError: No module named psutil
====================
Monitor out at: /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out

{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to