Hi,@bgooley ! Thx for reply. the main trouble is that we cant pass "Install agents" step due to the error: " Monitor-HostMonitor throttling_logger ERROR Timed out waiting for worker process collecting filesystem usage to complete. This may occur if the host has an NFS or other remote filesystem that is not responding to requests in a timely fashion. Current nodev filesystems: /dev/shm,/run,/sys/fs/cgroup,/run/cloudera-scm-agent/process,/run/cloudera-scm-agent/process,/run/user/1001,/run/user/1003,/run/user/0"  - which I found in "Details". And there are no errors anymore, only this one. If I open up CM and go to the Hosts tab then there are no hostst added, except that one, on which CM is installed. Which additional information can I provide to solve the issue?     ... View more

   Hi! Yes, ntp works properly (I know about similary problems if ntp dont working, but looks like this error not about ntp).  We tried to restart agents and cm server (include host restart) and even try to install different version (6.1.1) of CM and agents on different hosts, but no luck. And yes, we did "df -h" on the hosts: this shows filesystems used by host. There no errors or some "strange things" in output of the command. We dont use NFS or any other network mounted FS. And I tried as example change directory to nodev fs /run/cloudera-scm-agent/process and do  "ls -la" which returns ''." and ".." whitout any delays as expected. Thus, I think, this FS used by cm-agent works properly.     At the end, if we install agent on the same host as Cloudera Manager, then it is ok, no errors about "nodev" filesystems or any other. ... View more

Hi! Thanks for the answer! We're using cloudera hadoop about two years and installed it many times, but run into the trouble for the first time. Hostnames are resolved correctly (we have own dns with forward and reverse zones) and there is no firewall rules on any host at all. Selinux is disabled. Moreover, i can telnet to CM host by its hostname from agents hosts on port 7182, but still watch this annoying error. We can't run host inspector, because hosts cant pass the "Install agents" step due to this error. Now we have no idea what the problem is and what to do. ... View more

Hi! We have the same problem! In log details we found error: " Monitor-HostMonitor throttling_logger ERROR Timed out waiting for worker process collecting filesystem usage to complete. This may occur if the host has an NFS or other remote filesystem that is not responding to requests in a timely fashion. Current nodev filesystems: /dev/shm,/run,/sys/fs/cgroup,/run/cloudera-scm-agent/process,/run/cloudera-scm-agent/process,/run/user/1001,/run/user/1003,/run/user/0"    At the moment we tried to install Cloudera manager 6.2.0 and 6.1.1, but result the same. Agent host has no problems with connectivity to Manager host (Checked it by command "telnlet <Cloudera manager machine ip address or name>  7182" which was successfully connected. Also command "ss -anp" showed "established" connection on both hosts.)  ... View more

Could someone explain me, what does exactly mean this portion of the error:     2019-06-19 14:58:20,944 DEBUG org.apache.hadoop.security.UserGroupInformation: PrivilegedAction as:hbase (auth:SIMPLE) from:org.apache.hadoop.hbase.thrift.ThriftHttpServlet.doKerberosAuth(ThriftHttpServlet.java:162) 2019-06-19 14:58:20,950 DEBUG org.apache.hadoop.security.UserGroupInformation: PrivilegedActionException as:hbase (auth:SIMPLE) cause:org.apache.hadoop.hbase.thrift.HttpAuthenticationException: Kerberos authentication failed: 2019-06-19 14:58:20,951 INFO org.apache.hadoop.hbase.thrift.ThriftHttpServlet: Failed to authenticate with hbase kerberos principal 2019-06-19 14:58:20,951 ERROR org.apache.hadoop.hbase.thrift.ThriftHttpServlet: Kerberos Authentication failed   Who present his identity (credentials?) to whom here? Hbase server to Thrift server or vice versa? Or Thrift cant authenticate to kerberos itself (and why)? Which service uses the hbase principal here and why it couldn't get its credentials?   Would appericate any help! ... View more

Hi! We have the same error in our cluster. I found out that if you uncheck property "Enable HBase Thrift Http Server" in hbase configuration, this error disappear, but then u cannot use the "doAs" feature of thrift server and all users who can access Hue have the same privileges in hbase as user hue (by which Hue server connects to thrift server and hence hbase server). We are still looking for a solution of the problem. Version of our cluster is 6.1.1. ... View more