@cloud123user, Thanks for the kind feedback.  I am glad that the solution worked for you! ... View more

@RjsChw,   I am not a Sqoop expert, but the error you getting is not coming from Hadoop services; rather, the login to your Oracle Database is failing.  In this case, I believe you should review how you are supplying credentials to authenticate to the Oracle DB and verify they are correct. ... View more

@monicbw,   Hadoop uses the following to derive group membership when using ShellBasedUnixGroupsMapping:   id -gn monica.baniwijaya;id -Gn monica.baniwijaya You can run the above to see what hdfs sees when it tries to figure out to what groups you belong. Also, you can run the following to find out what groups hdfs thinks you belong to: hdfs groups monica.baniwijaya This will return what is in hdfs's user/group mapping cache. Knowing what each of the above returns will go a long way toward understanding the problem better.   That said, I am concerned about 2 things you mentioned:  (1)   You referred to "LDAP".  OS users and LDAP users are completely different unless you have some way for your OS to pull information from LDAP and return it for user/group requests (SSSD, IPA, Centrify, are a few examples).  How is LDAP involved in this situation?   (2) in your "useradd" example, you are setting the primary group for your user which is not common as far as I know.  I think you meant to use -G instead which will add a secondary group to a user: -g, --gid GROUP name or ID of the primary group of the new account -G, --groups GROUPS list of supplementary groups of the new account Lastly, you mentioned that in HDFS your user belongs to a different group than on the OS and that you would expect the group to be created in HDFS too.  HDFS relies on the user/groups mapping returned from the OS... it will cache that information, but it is not created in HDFS.  Minor difference.  What test did you do to determine that the OS and HDFS groups appear different for your user?  I'd use the "id" and "hdfs groups" commands I pointed out earlier to get a better sense of what HDFS sees.   ... View more

@kvinod,   Since Reports Manager and Activity Monitor are not as essential as Host Monitor, Service Monitor, Events Server, and Alerts Publisher, I recommend adding the Management Service with only those for now.    They don't use a SQL database, so you should be able to get your CM and Management Service looking good again.  You can then add the Activity Monitor and Reports Manager later without as much stress.   REGARDING THE PROBLEM: I'd like to point out that the error you got in the wizard (when you took the screen shot) showed that the host/port combination provided in the Add Service wizard could not be contacted.  The "No database server found running on host ___" error is thrown if a CONNECTION REFUSED is returned by the attempt to connect.  This generally means that there was nothing listening on the requested host and port.   Since we found no port number (7432) specified in the database host string (in the Add Service wizard) the default of 5432 would be used.  NOTE that you have 2 postgres servers running on the host where you did the netstat: Cloudera Embedded (listening on 7432) Another postgres server (listening on 5432) If that is the case and the "test connection" could connect to neither, that makes me curious whether the hostname specified in the wizard is the one where the postgres servers are listening.   We understand that you are under some stress, but it is very difficult to understand what is going wrong with just the information we have.  It might be useful to take a look at the stderr.log and stdout.log for the test connection command. On the host where you are attempting to install the Reports Manager and Activity Monitor, you can look in the /var/run/cloudera-scm-agent/process directory to find the db test command process directory.  It sill look like this for instance: 2839-MGMT.ACTIVITYMONITOR-test-db-connection.   Inside it, you will find a logs directory containing stderr.log... you might go over that file and see if there are any other clues.   Also, you could use psql command to test the connection yourself from the host where you are trying add the Reports Manager and Activity Monitor.     ... View more

@kvinod,   Thank you for all that information.  It really helps us understand the problem. When you are specifying the database host, I note in your image that you specified just the host which means it will default to using the default postgres port (5432).  The port for the embedded db is "7432".   Try specifying your database host with "host:7432" (including the port) to see if that helps.   Since you are using the embedded database, the usernames and passwords will be created for you. To use the existing embedded database, you will need to use the generated username and passwords that are stored for reference in the following file: /etc/cloudera-scm-server/db.mgmt.properties You can use the username and password specified for each database. Based on what you mentioned, the above are likely to help. ... View more

@kvinod,   The "No database server found running" indicates that your postgres server is either not running on the host you specified or is running on another host.  If you don't know where your database server is or it is missing, make sure you know if you installed and configured your own database or if you are using the "embedded" database from Cloudera that is intended for Proof of Concept installs.   If you need to set up your databases again, you can use this:   https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_extrnl_pstgrs.html   After preparing the database, you can retry the install.   NOTE:  If you are *not* using MapReduce1 then you do not need Activity Monitor as it does not capture MR2/YARN.  If you are only using YARN for your Map Reduce, then this is a good time to get rid of Activity Monitor.     ... View more

@wert_1311, Ah, since you are using Cloudera Manager 5.x, Oozie service is required.  You don't have to have it running, so you could just configure it to use minimal memory (in case it gets started by accident) and then just leave it off.  This will make CM happy.   We did remove this dependency in Cloudera Manager 6.2.(latest) and and CM 6.3.  For reference, the work was done in Cloudera Internal (private) Jira OPSAPS-49904.  So, you can upgrade to Cloudera Manager 6.3 to solve the issue you are hitting as well.  CM 6.3 can manage a CDH 5 cluster, so you don't need to upgrade CDH, too, if you do not want to.       Regards,   Ben ... View more

Hi @wert_1311 ,   The version of Cloudera Manager can matter here, but give this a try:   (1)   Log into Cloudera Manager and navigate to the Hue Service Click Configuration subtab   (2)   In the Configuration search field, type "oozie" You should see the following Oozie Service configuration return   (3)   Set Oozie Service to "None" Save your change   (4)   Restart Hue and see if the problem still occurs.   In later releases (CM 6.3, for instance) you will get a warning if trying to delete a Service on which another Service is dependent.   Hope that helps! ... View more