Ralph, The most common reason for not being able to start a Drillbit is that the port used for the Web UI is still being consumed by another instance of Drill. If you have previously tried to start a Drillbit outside of embedded mode there might still be some portion of the process still running. Could you check your running processes for anything that looks like Drill?
-Jason On Mon, Jan 19, 2015 at 9:00 AM, Andries Engelbrecht < aengelbre...@maprtech.com> wrote: > Hi Ralph, > > See what is in your drillbit.log file and if there are any clues as to why > the drillbit doesn’t want to start. > > Have not used RHEL 6.6 with Drill, don’t know if there is a major blocker > for Drill between RHEL 6.5 and 6.6. > > —Andries > > > > On Jan 19, 2015, at 8:49 AM, Ralph Schlosser <ralph.schlos...@ericsson.com> > wrote: > > > Hi Andries, > > > > Thanks for taking your time to look into this, I really appreciate it. > > > > I probably should have mentioned that I did use sqlline too. > > > > Just for completeness sake I ran the command again, as you suggested, > and cleared out the log directory beforehand: > > > > [vagrant@rhelbox apache-drill-0.7.0]$ cd log > > [vagrant@rhelbox log]$ ls -la > > total 8 > > drwxrwxr-x. 2 vagrant vagrant 4096 Jan 19 16:39 . > > drwxrwxr-x. 7 vagrant vagrant 4096 Jan 19 13:43 .. > > [vagrant@rhelbox log]$ cd .. > > [vagrant@rhelbox apache-drill-0.7.0]$ ./bin/sqlline -u > jdbc:drill:zk=local -n admin -p admin > > Drill log directory /var/log/drill does not exist, defaulting to > /home/vagrant/opt/apache-drill-0.7.0/log > > Error: Failure while attempting to start Drillbit in embedded mode. > (state=,code=0) > > sqlline version 1.1.6 > > 0: jdbc:drill:zk=local> Connection is already closed. > > > > As you can see, this is still not working. > > > > I'm guessing this is related to the environment, RHEL 6.6, as it > successfully works in Ubuntu 14.04. > > > > Is there any other way to look into this in more detail, short of > re-compiling the source from scratch and attach a debugger etc? > > > > > > Regards, > > Ralph > > -----Original Message----- > > From: Andries Engelbrecht [mailto:aengelbre...@maprtech.com] > > Sent: Monday, January 19, 2015 4:34 PM > > To: user@drill.apache.org > > Subject: Re: Connection timeout on port 2181 - apache-drill-0.7.0 > > > > 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 < > ralph.schlos...@ericsson.com> 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:aengelbre...@maprtech.com] > >> Sent: Monday, January 19, 2015 3:44 PM > >> To: user@drill.apache.org > >> 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=44994 > >> 063#Starting/StoppingDrill-invokeSQLLine > >> > >> > >> > >> -Andries > >> > >> > >> > >> On Jan 19, 2015, at 6:35 AM, Ralph Schlosser < > ralph.schlos...@ericsson.com> 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 > >> > > > >
