Thank You mgrover for all the answers. ... View more

Apparently this was the issue as it reported a successful install. But now CM doesn't come up in my browser at port 7180.  😞   Still working through that.  The content of the log file follows:     Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile  * base: centos.mia.host-engine.com  * extras: mirror.raystedman.net  * updates: mirror.5ninesolutions.com Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package cloudera-manager-server.x86_64 0:5.0.2-1.cm502.p0.297.el6 will be installed --> Processing Dependency: cloudera-manager-daemons = 5.0.2 for package: cloudera-manager-server-5.0.2-1.cm502.p0.297.el6.x86_64 --> Running transaction check ---> Package cloudera-manager-daemons.x86_64 0:5.0.2-1.cm502.p0.297.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================  Package                 Arch   Version                  Repository        Size ================================================================================ Installing:  cloudera-manager-server x86_64 5.0.2-1.cm502.p0.297.el6 cloudera-manager 8.0 k Installing for dependencies:  cloudera-manager-daemons                          x86_64 5.0.2-1.cm502.p0.297.el6 cloudera-manager 315 M Transaction Summary ================================================================================ Install       2 Package(s) Total download size: 315 M Installed size: 428 M Downloading Packages: -------------------------------------------------------------------------------- Total                                           317 kB/s | 315 MB     16:56      Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Warning: RPMDB altered outside of yum.    Installing : cloudera-manager-daemons-5.0.2-1.cm502.p0.297.el6.x86_64     1/2    Installing : cloudera-manager-server-5.0.2-1.cm502.p0.297.el6.x86_64      2/2    Verifying  : cloudera-manager-daemons-5.0.2-1.cm502.p0.297.el6.x86_64     1/2    Verifying  : cloudera-manager-server-5.0.2-1.cm502.p0.297.el6.x86_64      2/2 Installed:   cloudera-manager-server.x86_64 0:5.0.2-1.cm502.p0.297.el6                      Dependency Installed:   cloudera-manager-daemons.x86_64 0:5.0.2-1.cm502.p0.297.el6                     Complete! ... View more

Thanks jkestelyn and mrover it s helped us lot to get the product information. ... View more

Glad to hear it, thanks for the followup! ... View more

Thanks for quick&clear reply ... View more

Thanks, will do! ... View more

We use CDH 4.3, CM 4.6.3 The first thing we've checked was metastore service. It works. impala queries, other hive queries run fine. All our "SQL-like" stuff uses single metastore in PostGre DB. I've also see how does hive tried to get partitions for table used in failed query. There no exceptions on Metastore side, it works 100%   We've mentioned one more intersting thing. Queried table have ~1500 partitions (hour partitions). When we issue the same query explicitly specifing the range partition, it works. Even if we specify the range between the oldest and the newest partition (the same as we don't sepcify them at all!) it works.   I have no Idea what is that...   ... View more