Done that, Did not see any entries in drillbit.log and drillbit.out
-----Original Message----- From: Parth Chandra <[email protected]> Sent: Wednesday, May 9, 2018 7:31 PM To: [email protected] Subject: Re: Handhsake Error Try to set the logging level of the drillbit to trace. In your logback.xml - <logger name="org.apache.drill.exec.rpc" additivity="false"> <level value="trace" /> <appender-ref ref="FILE" /> </logger> There should be a message starting with "Handling handshake ... " On Wed, May 9, 2018 at 11:12 AM, Peter Edike < [email protected]> wrote: > I have increased the timeout and I am quite sure there are no > authentication modules enabled. Is there anyway I can check if the > request is getting to the server in the first place???? > > On May 9, 2018 7:09 PM, Parth Chandra <[email protected]> wrote: > If you haven't tried it already, try increasing the handshake timeout. > Do you have any security/authentication settings turned on? One > possibility is that an authentication module is being accessed by the > server during the handshake and the server is taking too long to reply > to the handshake causing the timeout. > > > > > > On Wed, May 9, 2018 at 3:05 AM, Peter Edike < > [email protected]> wrote: > > > > > Hello everyone > > > > I am trying to setup a datasource to connect to a drillbit running > > on a host I am using the Direct To DrillBit Option And have > > specified the ip-address of the server on which the drill bit > > service is running as > well > > as the appropriate ports > > I can telnet from my windows pc into this port via the telnet > > command but all attempts to initiate a connection from DSN Setup > > Dialog Box Fails > with > > Handshake Error. > > > > FAILED! > > > > [MapR][Drill] (1010) Error occurred while trying to connect: > [MapR][Drill] > > (40) Handshake timed out (HandshakeTimeout=5) while trying to > > connect to local=172.x.x.x:31010. Check whether Drillbit is running > > in a healthy > state > > or increase the timeout. > > > > Warm Regards > > Peter E > > ________________________________ > > > > This message has been marked as CONFIDENTIAL on Wednesday, May 9, > > 2018 @ > > 11:05:23 AM > > > > >
