Hi Ralph, With embedded mode the drill bit will start when using the sqlline command as mentioned earlier. You don’t need to run the drillbit.sh scrip to start the drillbit.
Try running-- ./bin/sqlline -u jdbc:drill:zk=local -n admin -p admin (from the drill HOME directory). This will actually start the drillbit for you in embedded mode. Once it is up you can connect to the drill webUI using port 8047, and also via ODBC to port 31010. —Andries On Jan 19, 2015, at 8:21 AM, Ralph Schlosser <[email protected]> wrote: > Hi Andries, > > That's exactly what I did, started in embedded mode simply by running > "./drillbit.sh start". As this is my first encounter with Drill I followed > the 10 minute quick start tutorial to the letter. :) > > The problem, though, is that Drill never seems to fully initialize, hence the > error message. > > Issuing "netstat -an" confirms that no process is listening on 2181 (haven't > changed anything from the default config) > > Is there a way to turn on some more detailed debug logs? > > > Regards, > Ralph > -----Original Message----- > From: Andries Engelbrecht [mailto:[email protected]] > Sent: Monday, January 19, 2015 3:44 PM > To: [email protected] > Subject: Re: Connection timeout on port 2181 - apache-drill-0.7.0 > > Are you running Drill in embedded or distributed mode? > > If you are using embedded mode, you don't specify a port number simply start > drill by using sqlline sqlline -u jdbc:drill:zk=local -n admin -p admin > > If using distributed mode, you connect to drill by using the zookeeper port > number of the cluster > (2181 for Apache ZK or 5181 for the Sanbox and MapR Hadoop Distros) > > See > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=44994063#Starting/StoppingDrill-invokeSQLLine > > > > -Andries > > > > On Jan 19, 2015, at 6:35 AM, Ralph Schlosser <[email protected]> > wrote: > >> Hi, >> >> I was trying to follow the Apache Drill tutorial but encountered the >> following error in drillbit.out when starting drillbit: >> >> 11:14:52.901 [main] ERROR org.apache.curator.ConnectionState - >> Connection timed out for connection string (127.0.0.1:2181) and >> timeout (5000) / elapsed (10197) >> org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = >> ConnectionLoss >> at >> org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java: >> 198) [curator-client-2.5.0.jar:na] >> >> Also, this is my environment: >> >> [vagrant@rhelbox log]$ java -version >> java version "1.7.0_71" >> Java(TM) SE Runtime Environment (build 1.7.0_71-b14) Java HotSpot(TM) >> 64-Bit Server VM (build 24.71-b01, mixed mode) [vagrant@rhelbox log]$ >> cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.6 >> (Santiago) [vagrant@rhelbox log]$ >> >> Note that SELinux is turned off (that was my first thought). >> >> Interestingly, this problem doesn't occur when starting drillbit on Ubuntu >> 14.04 and netstat -an confirms the port is open. >> >> Any suggestions as to how to troubleshoot this further? >> >> >> Regards, >> Ralph >
