I uninstalled and purges postgress, cleared out /opt/ImpalaToolchain, and then bootstrapping failed on hadoop-lzo with
Incompatible version of org.apache.tools.ant.Main detected Location of this class /home/jbapple/Impala/fe/target/dependency/ant-1.5.jar ant.home: /usr/share/ant So, I removed the jar, ran bin/clean.sh, and bootstrapping then worked. Shrug emoji. On Thu, Apr 26, 2018 at 12:15 PM, Jim Apple <jbap...@cloudera.com> wrote: > OK, that got me past that barrier. Then I needed to update my metastore > schema, so I ran > > ./buildall.sh -format -testdata -skiptests -notests -ninja > > which resulted in > > Metastore service failed to start within 300.0 seconds. > > logs/cluster/hive-metastore.log shows: > > WARN [main] metastore.HiveMetaStore: Retrying creating default database > after error: Unable to open a test connection to the given database. JDBC > url = jdbc:postgresql://localhost:5432/hive_impala, username = hiveuser. > Terminating connection pool (set lazyInit to true if you expect to start > your database after your app). Original Exception: ------ > org.postgresql.util.PSQLException: Connection refused. Check that the > hostname and port are correct and that the postmaster is accepting TCP/IP > connections. > > so I tried > > psql -U hiveuser -c "SELECT * FROM pg_roles WHERE rolname = 'hiveuser';" > psql: FATAL: database "hiveuser" does not exist > > and then > > createdb hiveuser > bin/create-test-configuration.sh > > That worked. I then ran > > testdata/bin/run-all.sh > > again, and it failed again, with the same error as above about "Unable to > open a test connection to the given database". > > On Thu, Apr 26, 2018 at 10:36 AM, Lars Volker <l...@cloudera.com> wrote: > >> This has bitten me before, too. I pushed a change to issue an additional >> warning if the minicluster fails to start and the environment points to >> Java 7 and Hadoop 3: https://gerrit.cloudera.org/#/c/10222/ >> >> Most people will have seen it by now, but maybe it's not too late to safe >> someone else from the trouble. :) >> >> On Thu, Apr 26, 2018 at 9:40 AM, Gabor Kaszab <gaborkas...@cloudera.com> >> wrote: >> >> > Hey Jim, >> > I got the same error the other day. Moving to Java8 solved it for me. >> > >> > Gabor >> > >> > On Thu, Apr 26, 2018 at 6:37 PM, Philip Zeyliger <phi...@cloudera.com> >> > wrote: >> > >> > > Hi Jim, >> > > >> > > Are you using JDK7? Hadoop3 supports only JDK8+. >> > > >> > > -- Philip >> > > >> > > On Thu, Apr 26, 2018 at 9:35 AM, Jim Apple <jbap...@cloudera.com> >> wrote: >> > > >> > > > testdata/bin/run-all.sh fails for me with the following error >> > > > >> > > > Exception in thread "main" java.lang.UnsupportedClassVersionError: >> > > > org/apache/hadoop/hdfs/server/namenode/NameNode : Unsupported >> > > major.minor >> > > > version 52.0 >> > > > >> > > > This is at gerrit HEAD, at tree hash >> > > > >> > > > 6e88e1b26423badb4012506c10a98f32f600dbdb IMPALA-6892: >> > > > CheckHashAndDecrypt() >> > > > includes file and host >> > > > >> > > > aka commit >> > > > >> > > > 518bcd3e148caa8b42011de11e971c2978fb6f3b >> > > > >> > > > This occurs even after a successful buildall.sh >> > > > >> > > >> > >> > >
