What I See

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa

Update Cloudera Manager to specific version [5.4.5] Take database backup. If we are running a dedicated database which is recommended in production setup. then we need to take a backup of the DB as a precaution. Assuming we are using a dedicated DB. Stop Cloudera Manager Server, Database, and Agent Shutdown cloudera manager server. sudo service cloudera-scm-server stop If cloudera manager is also running an Agent service. sudo service cloudera-scm-agent stop NOTE : If we are using a standalone/embedded database then we need to stop that as well. sudo service cloudera-scm-server-db stop Update repository to get the latest rpm. Create a file cloudera-manager.repo with below contents. [cloudera-manager] # Packages for Cloudera Manager, Version 5.4.5, on RedHat or CentOS 6 x86_64 name=Cloudera Manager baseurl=http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.4.5/ gpgkey=http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera gpgcheck=1 copy c

Getting started with Hive with Kerberos. Grant Permissions to user groups to access hive . Login to the server and create a role. If these roles are not created then we get permission (Privileges) Issues. Issue as below. Error: Error while compiling statement: FAILED: SemanticException No valid privileges Required privileges for this query: Server=server1->action=*; (state=42000,code=40000) Here is how to grant permissions to hive group, so that you can access it. [sas@waepprrkb004 root]$ beeline -u "jdbc:hive2://hive-server.server.com:10000/default;principal=hive/hive-server.server.com@XYZ.DOMAIN.COM" 0: jdbc:hive2://hive-server.server.com> create role admin; 1 row affected 0: jdbc:hive2://hive-server.server.com> show roles; +--------+--+ | role | +--------+--+ | admin | +--------+--+ 0: jdbc:hive2://hive-server.server.com> GRANT ROLE admin TO GROUP hive; 0: jdbc:hive2://hive-server.server.com> GRANT ALL ON DATABASE default TO ROLE admin;

Setup and Configure NFS Mounts on Linux Server To setup we will need 2 servers. Master and Slave. nfsmaster.server.com 192.168.33.135 # Hosts the NFS shared drive. nfsslave.server.com 192.168.33.132 # Client to use the master shared drive. NOTE: You can add the hostnames in the /etc/hosts file and user the hostnames in the configuration rather than IP addresses. Steps to setup NFS. Install NFS and rpcbind on master and slave servers. nfs-utils nfs-utils-lib rpcbind Configure NFS on master server. Configure mount points on slave server. Mount NFS on slave server. Installing NFS Server and NFS Slave We need to install NFS packages using yum . [root@nfsmaster ~]# yum install nfs-utils nfs-utils-lib [root@nfsmaster ~]# yum install rpcbind Make sure to install rpcbind and start it first. Now start the services on both machines. [root@nfsmaster ~]# /etc/init.d/rpcbind start NOTE: Start rpcbind first else you will get the below error. [root@nfsmaster