Cloudera Manager Server服务在RedHat7状态显示异常分析

温馨提示：要看高清无码套图，请使用手机打开并单击图片放大查看。

1.问题描述

在RedHat7.x上启动了Cloudera Manager Server服务，Web界面访问正常，集群各个服务均正常，集群状态正常如下图所示：

在RedHat服务器上使用“systemctl status cloudera-scm-server”命令查看cloudera-scm-server服务状态为exited（正常的服务应该是active(running)），显示如下：

ec2-user@ip-172-31-22-86~$ systemctl status cloudera-scm-server

●cloudera-scm-server.service- LSB:Cloudera SCM Server

Loaded: loaded (/etc/rc.d/init.d/cloudera-scm-server; bad; vendor preset: disabled)

Active: active (exited)since Mon 2017-11-13 09:27:27 EST; 14min ago

Docs: man:systemd-sysv-generator(8)

Process: 788 ExecStart=/etc/rc.d/init.d/cloudera-scm-serverstart (code=exited, status=0/SUCCESS)

Nov 13 09:27:21ip-172-31-22-86.ap-southeast-1.compute.internal systemd1: Starting LSB:Clou...

Nov 13 09:27:22ip-172-31-22-86.ap-southeast-1.compute.internal su928: (to cloudera-scm) roo...

Nov 13 09:27:27 ip-172-31-22-86.ap-southeast-1.compute.internalcloudera-scm-server788: Star...

Nov 13 09:27:27ip-172-31-22-86.ap-southeast-1.compute.internal systemd1: Started LSB:Cloud...

Hint: Some lines were ellipsized, use-l to show in full.

ec2-user@ip-172-31-22-86~$

2.问题分析

在使用systemctl status cloudera-scm-server输出CM服务器的状态时，因为OS检测到Cloudera Manager启动后，不知道如何跟踪Cloudera Manager的状态导致。

3.查看CM服务器状态方式

以下介绍了在服务器上查看Cloudera Manager服务状态是否正常的几种方式。

使用“ps –ef”命令来检查Cloudera Manager的后台进程

[ec2-user@ip-172-31-22-86 ~]$ ps -ef |grep cloudera-scm-server
clouder+   986   928 19 09:27 ?        00:07:25 /usr/java/jdk1.7.0_67-cloudera/bin/java -cp .:lib/*:/usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar -server -Dlog4j.configuration=file:/etc/cloudera-scm-server/log4j.properties -Dfile.encoding=UTF-8 -Dcmf.root.logger=INFO,LOGFILE -Dcmf.log.dir=/var/log/cloudera-scm-server -Dcmf.log.file=cloudera-scm-server.log -Dcmf.jetty.threshhold=WARN -Dcmf.schema.dir=/usr/share/cmf/schema -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dpython.home=/usr/share/cmf/python -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+HeapDumpOnOutOfMemoryError -Xmx2G -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -XX:OnOutOfMemoryError=kill -9 %p com.cloudera.server.cmf.Main
ec2-user 29038 19145  0 10:05 pts/0    00:00:00 grep --color=auto cloudera-scm-server

有如上截图标注部分则表示CM服务启动正常。

通过查看/var/log/cloudera-scm-server/cloudera-scm-server.log的方式

[root@ip-172-31-22-86 cloudera-scm-server]# pwd
/var/log/cloudera-scm-server
[root@ip-172-31-22-86 cloudera-scm-server]# tail -f cloudera-scm-server.log
2017-11-13 10:41:08,960 INFO 1253652960@agentServer-2:com.cloudera.server.common.MonitoringThreadPool: agentServer: execution stats: average=61ms, min=16ms, max=6633ms.

2017-11-13 10:41:08,960 INFO 1253652960@agentServer-2:com.cloudera.server.common.MonitoringThreadPool: agentServer: waiting in queue stats: average=0ms, min=0ms, max=34ms.

2017-11-13 10:41:13,625 INFO ScmActive-0:com.cloudera.server.cmf.components.ScmActive: (119 skipped) ScmActive completed successfully.

如上日志显示”ScmActivecompleted successfully”信息则表示CM服务启动成功。

使用“netstat –apn |grep 7180”方式

[root@ip-172-31-22-86 cloudera-scm-server]# netstat -apn |grep 7180
tcp        0      0 0.0.0.0:7180            0.0.0.0:*               LISTEN      30821/java
[root@ip-172-31-22-86 cloudera-scm-server]#

如上截图7180端口被监听则表示CM服务启动成功。

4.说明

CM的agent服务也会有这个问题，通过systemctl status cloudera-scm-agent也无法查看agent的正确状态。具体也可以通过进程，日志和端口来判断服务是否正常。

为天地立心，为生民立命，为往圣继绝学，为万世开太平。

温馨提示：要看高清无码套图，请使用手机打开并单击图片放大查看。