Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0.

Richi — Tue, 21 Apr 2026 13:49:59 GMT

Hello, I am confused for why my CM is showing error and no results of any charts. It was working fine till yesterday and today morning it stopped unexpectedly. The error I am getting is:

Request to the Service Monitor failed. This may cause slow page responses. View the status of the Service Monitor.

Request to the Host Monitor failed. This may cause slow page responses. View the status of the Host Monitor.

I have assigned 8GB of RAM and 2 processors to my VM.

My Cloudera configuration shows:

Cloudera QuickStart
- ZooKeeper: Service zookeeper has 1 Server. Cloudera suggests at least 3 Servers for ZooKeeper.
  Suppress...
- HDFS: Service hdfs has 1 DataNode. Cloudera suggests at least 3 DataNodes for HDFS.
  Suppress...
- HDFS: Java Heap Size of NameNode in Bytes
  Suppress...
  Java Heap Size of NameNode in Bytes is recommended to be at least 1GB for every million HDFS blocks. Suggested minimum value: 4294967296
- Kafka: Java Heap Size of Broker
  Suppress...
  50 is less than the recommended minimum of 256.
- quickstart.cloudera: Memory Overcommit Validation Threshold
  Suppress...
  Memory on host quickstart.cloudera is overcommitted. The total memory allocation is 13.7 GiB bytes but there are only 3.7 GiB bytes of RAM (766.5 MiB bytes of which are reserved for the system). Visit the Resources tab on the Host page for allocation details. Reconfigure the roles on the host to lower the overall memory allocation. Note: Java maximum heap sizes are multiplied by 1.3 to approximate JVM overhead.
- quickstart.cloudera: Package installs detected on host with parcels
  Suppress...
  Parcels are in use, but packages were also detected. Cloudera Manager recommends removing the packages. Components affected: crunch,flume-ng,hadoop,hadoop-0.20-mapreduce,hadoop-hdfs,hadoop-httpfs,hadoop-kms,hadoop-mapreduce,hadoop-yarn,hbase,hbase-solr,hive,hive-hcatalog,hue,hue-common,impala,llama,oozie,parquet,pig,sentry,solr,spark,sqoop,sqoop2,zookeeper.
Other
- Cloudera Management Service: Java Heap Size of Service Monitor in Bytes
  Suppress...
  The recommended heap size is 1.0 GiB bytes, 768.0 MiB more than is configured.
- Cloudera Management Service: Maximum Non-Java Memory of Service Monitor
  Suppress...
  The recommended non-Java memory size is 1.5 GiB, 768.0 MiB more than is configured.
- Cloudera Management Service: Java Heap Size of Host Monitor in Bytes
  Suppress...
  The recommended heap size is 1.0 GiB bytes, 768.0 MiB more than is configured.
- Cloudera Management Service: Maximum Non-Java Memory of Host Monitor
  Suppress...
  The recommended non-Java memory size is 1.5 GiB, 768.0 MiB more than is configured.
  
  I am new to Cloudera, so what should I change so that my VM will start working. Please help me. thanks for help in advance.

Re: Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0.

dspivak — Thu, 11 Aug 2016 12:52:59 GMT

Give your VM more RAM. CM is starved.

Re: Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0.

Richi — Thu, 11 Aug 2016 13:04:19 GMT

Yes Sir. Got it. The RAM was very less. I assigned 10 GB and now its working great and also I stopped and removed inwanted roles and services. So its working now. Thanks for your reply.

question Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0. in Archives of Support Questions (Read Only)

Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0.

Re: Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0.

Re: Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0.