Created on 04-16-2018 10:15 AM - last edited on 04-16-2018 12:16 PM by cjervis
Made TLS implementation for Cloudera Manager. Unable to access CM after that.
Referred this link: https://community.cloudera.com/t5/Cloudera-Manager-Installation/how-to-rollback-cloudera-manager-tls...
to revert the changes. Not able to access the embedded Postgres console to do so.
Getting the error: [root@hostname pgsql]# psql -U cloudera-scm -p 7432 -h localhost -d postgres
psql: FATAL: the database system is shutting down
# lsof -i | grep LISTEN | grep cloudera-scm
postgres 11232 cloudera-scm 3u IPv4 105319 0t0 TCP *:7432 (LISTEN)
postgres 11232 cloudera-scm 4u IPv6 105320 0t0 TCP *:7432 (LISTEN)
java 24548 cloudera-scm 243u IPv4 3988695 0t0 TCP hostname.com:us-srv (LISTEN)
java 24548 cloudera-scm 244u IPv4 3988697 0t0 TCP *:rrac (LISTEN)
java 24550 cloudera-scm 347u IPv4 3988161 0t0 TCP hostname.com:palace-6 (LISTEN)
java 24550 cloudera-scm 348u IPv4 3989833 0t0 TCP hostname.com:d-s-n (LISTEN)
java 24550 cloudera-scm 349u IPv4 3989832 0t0 TCP *:palace-5 (LISTEN)
java 24587 cloudera-scm 237u IPv4 3987633 0t0 TCP *:7184 (LISTEN)
java 24587 cloudera-scm 241u IPv4 3987635 0t0 TCP *:8084 (LISTEN)
java 24587 cloudera-scm 245u IPv4 3987637 0t0 TCP *:7185 (LISTEN)
java 24627 cloudera-scm 268u IPv4 3989842 0t0 TCP *:distinct32 (LISTEN)
java 24627 cloudera-scm 272u IPv4 3989844 0t0 TCP hostname.com:distinct (LISTEN)
java 24627 cloudera-scm 273u IPv4 3988199 0t0 TCP hostname.com:simplifymedia (LISTEN)
java 24656 cloudera-scm 302u IPv4 3984366 0t0 TCP hostname.com:palace-4 (LISTEN)
java 24656 cloudera-scm 308u IPv4 3986063 0t0 TCP *:palace-3 (LISTEN)
java 24656 cloudera-scm 309u IPv4 3986068 0t0 TCP hostname.com:jamlink (LISTEN)
java 24704 cloudera-scm 232u IPv4 3987626 0t0 TCP *:ezmeeting-2 (LISTEN)
Please suggest.
Created 04-17-2018 02:52 AM
Created 04-17-2018 02:52 AM