Since the question was asked, the situation has changed. As soon as Hortonworks and Cloudera merged, NiFi became supported by Cloudera. Shortly after the integrations with CDH were also completed, so that NiFi is now a fully supported and integrated component. Please look into the documentation for the latest info at any time, but in general Cloudera Manager is now able to install NiFi. ... View more

You can put this option blank..if you are using SMTP, than no need. ... View more

Even I got the same problem while running cloudera in machine.Restarting cloudera-scm-server fixed the issue and I was able to view admin console in web UI.I think the problem is occuring by changing the network connectivity from wireless to wired or vise versa.This will automaticallly changes our machines public IP adrees so ssh may fail. ... View more

Hi,   I am facing the same issue where, cloudera agent is exiting because it is unable to find the supervisord.conf file. The conf file is not getting created.    Error see in cloudera-scm-agent.log file   [24/May/2018 14:19:31 +0000] 10889 MainThread agent INFO Re-using pre-existing directory: /run/cloudera-scm-agent /supervisor/include [24/May/2018 14:19:31 +0000] 10889 MainThread agent ERROR Failed to connect to previous supervisor.  Traceback (most recent call last): File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 2110, in find_or_start_supervisor self.get_supervisor_process_info() File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 2254, in get_supervisor_process_info self.identifier = self.supervisor_client.supervisor.getIdentification() File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1587, in __request verbose=self.__verbose File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/xmlrpc.py", line 460, in request self.connection.request('POST', handler, request_body, self.headers) File "/usr/lib64/python2.7/httplib.py", line 1017, in request self._send_request(method, url, body, headers) File "/usr/lib64/python2.7/httplib.py", line 1051, in _send_request self.endheaders(body) File "/usr/lib64/python2.7/httplib.py", line 1013, in endheaders self._send_output(message_body) File "/usr/lib64/python2.7/httplib.py", line 864, in _send_output self.send(msg) File "/usr/lib64/python2.7/httplib.py", line 826, in send self.connect() File "/usr/lib64/python2.7/httplib.py", line 807, in connect self.timeout, self.source_address) File "/usr/lib64/python2.7/socket.py", line 571, in create_connection raise err error: [Errno 111] Connection refused [24/May/2018 14:19:31 +0000] 10889 Dummy-1 daemonize WARNING Stopping daemon. [24/May/2018 14:19:31 +0000] 10889 Dummy-1 agent INFO Stopping agent... [24/May/2018 14:19:31 +0000] 10889 Dummy-1 agent INFO No extant cgroups; unmounting any cgroup roots   The cloudera manager and agent version is 5.12.0   We did have a server failure and after the reboot of the server, the agent does not start.   Ran the below the command: /usr/lib64/cmf/agent/build/env/bin/python /usr/lib64/cmf/agent/build/env/bin/cmf-agent --package_dir /usr/lib64/cmf/service --agent_dir /var/run/cloudera-scm-agent --lib_dir /var/lib/cloudera-scm-agent --logfile /var/log/cloudera-scm-agent/cloudera-scm-agent.log --comm_name cmf-agent --pidfile /var/run/cloudera-scm-agent/cloudera-scm-agent.pid   Output: [24/May/2018 14:27:45 +0000] 11274 MainThread agent INFO SCM Agent Version: 5.12.0 [24/May/2018 14:27:45 +0000] 11274 MainThread agent WARNING Expected mode 0751 for /run/cloudera-scm-agent but was 0755 [24/May/2018 14:27:45 +0000] 11274 MainThread agent INFO Re-using pre-existing directory: /run/cloudera-scm-agent [24/May/2018 14:27:45 +0000] 11274 MainThread agent INFO Not starting a new session. [24/May/2018 14:27:45 +0000] 11274 MainThread agent INFO Adding env vars that start with CMF_AGENT_ [24/May/2018 14:27:45 +0000] 11274 MainThread agent INFO Logging to /var/log/cloudera-scm-agent/cloudera-scm-agent.log Traceback (most recent call last): File "/usr/lib64/cmf/agent/build/env/bin/cmf-agent", line 12, in <module> load_entry_point('cmf==5.12.0', 'console_scripts', 'cmf-agent')() File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 3095, in main main_impl() File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 3078, in main_impl agent.start() File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 804, in start self.find_or_start_supervisor() File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 2151, in find_or_start_supervisor if not mount_tmpfs(process_dir, self.args.clear_agent_dir, self.sudo): File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/tmpfs.py", line 62, in mount_tmpfs if os.path.samefile(p.mountpoint, path) and p.fstype == "tmpfs" and "noexec" not in p.opts: File "/usr/lib64/cmf/agent/build/env/lib64/python2.7/posixpath.py", line 162, in samefile s1 = os.stat(f1) OSError: [Errno 2] No such file or directory: 'net:[4026532100]'   Please may you help on this? Is the issue fixed in v5.12.2? ... View more

I got the same problem when I put the Java files in my home directory. It only worked after I put the Java files in the /usr/java directory. ... View more

Great! Glad you figured it out! ... View more

@michalis I removed the salt :normal while enabling kerberos using cloudera manager and it imported the kdc successfully..     Thanks @bgooley and @michalis  for the support and helping me to solve this tricky one.       ... View more

Change the directories below for Service Monitor since the procedure is the same as for the Host Monitor.   You can salvage the contents of the Host Monitor by using the LDBStoreTool Java Class to repair the corrupted LDB:   Make sure the Host Monitor is stopped completely (it should be since it is unable to open this LDB). Backup the /var/lib/cloudera-host-monitor directory with tar or cp. Run the LDBStoreTool Java class to try and bring the corrupt database to a consistent state (please adjust the directory to the one reported in the exception): java -cp "/usr/share/cmf/lib/*" com.cloudera.cmon.tstore.leveldb.tool.LDBStoreTool repair --directory /var/lib/cloudera-host-monitor/subject_record/subject_ts/partitions/subject_ts_2017-10-30T18:03:04.415Z [ main] log INFO Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog [ main] CMONConfiguration INFO Config: jar:file:/usr/share/cmf/common_jars/firehose-5.12.1.jar!/cmon.conf [ main] ConfigUtil WARN Could not find configuration file cmon-cm-auth.conf [ main] LDBResourceManager INFO Max file descriptors: 4096 [ main] LDBResourceManager INFO Setting maximum open fds to: 2048 Running repair command Success   Start the Host Monitor and it should start now.   If the LDBStoreTool Java class is unable to repair the corrupt LDB then you will have to purge the /var/lib/cloudera-host-monitor directory similar to steps noted above by Michalis.   ... View more