error reading information on service cloudera-scm-server: No such file or directory

When removing/uninstalling Cloudera Manager; sometimes the removal process is not complete.

Use both rpm and yum package managers to list what is installed under CM and remove separately.


First make sure all the cloudera processes are stopped. 

ps -ef | grep cloudera

bash-4.1$ ps -ef | grep cloudera

498       8042     1  0 02:24 ?        00:00:01 /usr/bin/postgres -D /var/lib/cloudera-scm-server-db/data

root      8074     1  0 02:24 ?        00:00:00 su cloudera-scm -s /bin/bash -c nohup /usr/sbin/cmf-server 

498       8077  8074  1 02:24 ?        00:14:11 /usr/lib/jvm/jre-openjdk/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:-CMSConcurrentMTEnabled -XX:+UseParNewGC -XX:+HeapDumpOnOutOfMemoryError -Xmx2G -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -XX:OnOutOfMemoryError=kill -9 %p com.cloudera.server.cmf.Main

doug     13875 13791  0 15:15 pts/1    00:00:00 grep cloudera

Remove processes with pids 498, 8074,8077. Note openjdk is being used in process 8077. This is incorrect since CM does not support open-jdk. CM uses bigtop-0.7 which supports openjdk so if it is on your system bigtop-utils will detect and use it. This won't pass the Cloudera validation step when it checks hosts during the installation process. 

kill -9 8042 8074 8077

Verify all are killed: 

[root@r2371-d5-us01 ~]# ps -ef | grep cloudera

root     13915 13754  0 15:21 pts/1    00:00:00 grep cloudera

First test the rpm installer and remove the rpm Cloudera installed packages

[root@r2371-d5-us01 ~]# rpm -qa | grep cloudera

cloudera-manager-server-5.3.2-1.cm532.p0.209.el6.x86_64

cloudera-manager-agent-5.3.2-1.cm532.p0.209.el6.x86_64

cloudera-manager-daemons-5.3.2-1.cm532.p0.209.el6.x86_64

cloudera-manager-server-db-2-5.3.2-1.cm532.p0.209.el6.x86_64

[root@r2371-d5-us01 ~]# rpm -e --nodeps cloudera-manager-server-5.3.2-1.cm532.p0.209.el6.x86_64

cloudera-scm-server: unrecognized service

error reading information on service cloudera-scm-server: No such file or directory

error: %preun(cloudera-manager-server-5.3.2-1.cm532.p0.209.el6.x86_64) scriptlet failed, exit status 1

In the case above the paths were removed but the rpm db still has the cloudera-manager-server-cb installed. Use the --justdb option to remove the db entry.

rpm -e --justdb cloudera-manager-server-db-2-5.3.2-1.cm532.p0.209.el6.x86_64

Remove the yum installed packages

[root@r2371-d5-us01 ~]# yum list installed | grep cloudera

jdk.x86_64                          2000:1.6.0_31-fcs                @cloudera-manager

oracle-j2sdk1.7.x86_64              1.7.0+update67-1                 @cloudera-manager

remove the above yum packages then run cleancloudera.sh