Hi,

I'm new to the list, just registered for this question.

I'm setting up HBase in pseudo-distributed mode. I can run the hbase
shell locally, and create tables, put some rows, they are present in
the HDFS good.
However, when I try to connect either from the same machine or the
host machine (the HBase setup is on a VM), the client hangs after
connecting to ZooKeeper.

The console output is:

13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket connection to server
 debian-vm/192.168.1.102:2181. Will not attempt to authenticate using SASL (unkn
own error)
13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection established to de
bian-vm/192.168.1.102:2181, initiating session
13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment complete on s
erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005, negotiated ti
meout = 180000
 [..then waits forever, then after forever shows:]
org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to find regio
 for stops,,99999999999999 after 10 tries.

I checked the following pitfalls:
-- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according to
HBase documentation
-- I put 'vm-debian' (the hostname I want to identify my virtual
machine that runs the HBase setup) into the host and virtual machine's
/etc/host file to map the hostname nicely (and it works, because
browser shows Hadoop and HBase info pages)
-- I copied the hadoop related jars from hadoop root and hadoop/lib
into HBase/lib (although they were the same version, but I could never
know)
-- I set up the time on the virtual machine where the HBase setup runs
properly, no time shifts
-- I checked the logs and web UIs to see every processes are running:
Hadoop, HBase master, Zookeeper

Environment:
HBase install is a Debian 32 bit virtual machine, with JDK 1.7.0_17
Host machine is Windows 7 with JDK 1.7.0_05

but the client program does not work regardless if it's running on the
HBase VM or on the host

The tiny client is:
http://pastebin.com/060Yu2Gz

here are the config files:
http://pastebin.com/ArVvwU59

Please help and tell me what I do wrong, because it has been driving
me crazy for about 3 days, and I'm getting very angry about this whole
Hadoop stuff, that I cannot even get running a very basic use-case
with it.

Thanks,
Pal

Can you also send us the server logs during that timeframe?
Thanks.

-- Lars

________________________________
 From: Pal Konyves <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Tuesday, March 19, 2013 5:02 PM
Subject: HBase client hangs after connecting to Zookeeper in pseudo-mode
 
Hi,

I'm new to the list, just registered for this question.

I'm setting up HBase in pseudo-distributed mode. I can run the hbase
shell locally, and create tables, put some rows, they are present in
the HDFS good.
However, when I try to connect either from the same machine or the
host machine (the HBase setup is on a VM), the client hangs after
connecting to ZooKeeper.

The console output is:

13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket connection to server
debian-vm/192.168.1.102:2181. Will not attempt to authenticate using SASL (unkn
own error)
13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection established to de
bian-vm/192.168.1.102:2181, initiating session
13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment complete on s
erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005, negotiated ti
meout = 180000
[..then waits forever, then after forever shows:]
org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to find regio
for stops,,99999999999999 after 10 tries.

I checked the following pitfalls:
-- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according to
HBase documentation
-- I put 'vm-debian' (the hostname I want to identify my virtual
machine that runs the HBase setup) into the host and virtual machine's
/etc/host file to map the hostname nicely (and it works, because
browser shows Hadoop and HBase info pages)
-- I copied the hadoop related jars from hadoop root and hadoop/lib
into HBase/lib (although they were the same version, but I could never
know)
-- I set up the time on the virtual machine where the HBase setup runs
properly, no time shifts
-- I checked the logs and web UIs to see every processes are running:
Hadoop, HBase master, Zookeeper

Environment:
HBase install is a Debian 32 bit virtual machine, with JDK 1.7.0_17
Host machine is Windows 7 with JDK 1.7.0_05

but the client program does not work regardless if it's running on the
HBase VM or on the host

The tiny client is:
http://pastebin.com/060Yu2Gz

here are the config files:
http://pastebin.com/ArVvwU59

Please help and tell me what I do wrong, because it has been driving
me crazy for about 3 days, and I'm getting very angry about this whole
Hadoop stuff, that I cannot even get running a very basic use-case
with it.

Thanks,
Pal

Hello Pal,

    Add 127.0.0.1 along with the hostname of your vm, where you are running
your Hbase, into its /etc/hosts file. You are running Hbase in pseudo
distributed mode, but the logs show that the connection request is going to
some other IP.

Warm Regards,
Tariq
https://mtariq.jux.com/
cloudfront.blogspot.com
On Wed, Mar 20, 2013 at 5:32 AM, Pal Konyves <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I'm new to the list, just registered for this question.
>
> I'm setting up HBase in pseudo-distributed mode. I can run the hbase
> shell locally, and create tables, put some rows, they are present in
> the HDFS good.
> However, when I try to connect either from the same machine or the
> host machine (the HBase setup is on a VM), the client hangs after
> connecting to ZooKeeper.
>
> The console output is:
>
> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket connection to
> server
>  debian-vm/192.168.1.102:2181. Will not attempt to authenticate using
> SASL (unkn
> own error)
> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection established
> to de
> bian-vm/192.168.1.102:2181, initiating session
> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment
> complete on s
> erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005,
> negotiated ti
> meout = 180000
>  [..then waits forever, then after forever shows:]
> org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to find
> regio
>  for stops,,99999999999999 after 10 tries.
>
> I checked the following pitfalls:
> -- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according to
> HBase documentation
> -- I put 'vm-debian' (the hostname I want to identify my virtual
> machine that runs the HBase setup) into the host and virtual machine's
> /etc/host file to map the hostname nicely (and it works, because
> browser shows Hadoop and HBase info pages)
> -- I copied the hadoop related jars from hadoop root and hadoop/lib
> into HBase/lib (although they were the same version, but I could never
> know)
> -- I set up the time on the virtual machine where the HBase setup runs
> properly, no time shifts
> -- I checked the logs and web UIs to see every processes are running:
> Hadoop, HBase master, Zookeeper
>
> Environment:
> HBase install is a Debian 32 bit virtual machine, with JDK 1.7.0_17
> Host machine is Windows 7 with JDK 1.7.0_05
>
> but the client program does not work regardless if it's running on the
> HBase VM or on the host
>
> The tiny client is:
> http://pastebin.com/060Yu2Gz
>
> here are the config files:
> http://pastebin.com/ArVvwU59
>
> Please help and tell me what I do wrong, because it has been driving
> me crazy for about 3 days, and I'm getting very angry about this whole
> Hadoop stuff, that I cannot even get running a very basic use-case
> with it.
>
> Thanks,
> Pal
>

Yes, here they are, every of them are from hbase-start untill about 10
seconds the client is started and stuck. Additional logging is set so
the master log is probably bloated, sorry about that.

Zookeeper.log: pastebin.com/3ZErnH44
regionserver.log: pastebin.com/h3BBAhXf
master.out: pastebin.com/6zMGfFer
master.log: pastebin.com/kEryhz7j

Thanks for the quick reply,
Pal
On Wed, Mar 20, 2013 at 1:17 AM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Can you also send us the server logs during that timeframe?
>
>
> Thanks.
>
> -- Lars
>
>
>
> ________________________________
>  From: Pal Konyves <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Tuesday, March 19, 2013 5:02 PM
> Subject: HBase client hangs after connecting to Zookeeper in pseudo-mode
>
> Hi,
>
> I'm new to the list, just registered for this question.
>
> I'm setting up HBase in pseudo-distributed mode. I can run the hbase
> shell locally, and create tables, put some rows, they are present in
> the HDFS good.
> However, when I try to connect either from the same machine or the
> host machine (the HBase setup is on a VM), the client hangs after
> connecting to ZooKeeper.
>
> The console output is:
>
> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket connection to server
> debian-vm/192.168.1.102:2181. Will not attempt to authenticate using SASL (unkn
> own error)
> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection established to de
> bian-vm/192.168.1.102:2181, initiating session
> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment complete on s
> erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005, negotiated ti
> meout = 180000
> [..then waits forever, then after forever shows:]
> org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to find regio
> for stops,,99999999999999 after 10 tries.
>
> I checked the following pitfalls:
> -- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according to
> HBase documentation
> -- I put 'vm-debian' (the hostname I want to identify my virtual
> machine that runs the HBase setup) into the host and virtual machine's
> /etc/host file to map the hostname nicely (and it works, because
> browser shows Hadoop and HBase info pages)
> -- I copied the hadoop related jars from hadoop root and hadoop/lib
> into HBase/lib (although they were the same version, but I could never
> know)
> -- I set up the time on the virtual machine where the HBase setup runs
> properly, no time shifts
> -- I checked the logs and web UIs to see every processes are running:
> Hadoop, HBase master, Zookeeper
>
> Environment:
> HBase install is a Debian 32 bit virtual machine, with JDK 1.7.0_17
> Host machine is Windows 7 with JDK 1.7.0_05
>
> but the client program does not work regardless if it's running on the
> HBase VM or on the host
>
> The tiny client is:
> http://pastebin.com/060Yu2Gz
>
> here are the config files:
> http://pastebin.com/ArVvwU59
>
> Please help and tell me what I do wrong, because it has been driving
> me crazy for about 3 days, and I'm getting very angry about this whole
> Hadoop stuff, that I cannot even get running a very basic use-case
> with it.
>
> Thanks,
> Pal

Mohammad, I made the connection from host os to the virtual os where
HBase is running. the virtual OS is set up with bridged network, so it
gets it's own local IP address, which in this case was
HBase VM: 192.168.0.102
Host os: 192.168.0.101 (I'm not sure, but you will see it in the zookeeper log)

I know it works, because http://debian-vm:60010 comes up from Host os

On Wed, Mar 20, 2013 at 1:30 AM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> Hello Pal,
>
>     Add 127.0.0.1 along with the hostname of your vm, where you are running
> your Hbase, into its /etc/hosts file. You are running Hbase in pseudo
> distributed mode, but the logs show that the connection request is going to
> some other IP.
>
> Warm Regards,
> Tariq
> https://mtariq.jux.com/
> cloudfront.blogspot.com
>
>
> On Wed, Mar 20, 2013 at 5:32 AM, Pal Konyves <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> I'm new to the list, just registered for this question.
>>
>> I'm setting up HBase in pseudo-distributed mode. I can run the hbase
>> shell locally, and create tables, put some rows, they are present in
>> the HDFS good.
>> However, when I try to connect either from the same machine or the
>> host machine (the HBase setup is on a VM), the client hangs after
>> connecting to ZooKeeper.
>>
>> The console output is:
>>
>> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket connection to
>> server
>>  debian-vm/192.168.1.102:2181. Will not attempt to authenticate using
>> SASL (unkn
>> own error)
>> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection established
>> to de
>> bian-vm/192.168.1.102:2181, initiating session
>> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment
>> complete on s
>> erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005,
>> negotiated ti
>> meout = 180000
>>  [..then waits forever, then after forever shows:]
>> org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to find
>> regio
>>  for stops,,99999999999999 after 10 tries.
>>
>> I checked the following pitfalls:
>> -- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according to
>> HBase documentation
>> -- I put 'vm-debian' (the hostname I want to identify my virtual
>> machine that runs the HBase setup) into the host and virtual machine's
>> /etc/host file to map the hostname nicely (and it works, because
>> browser shows Hadoop and HBase info pages)
>> -- I copied the hadoop related jars from hadoop root and hadoop/lib
>> into HBase/lib (although they were the same version, but I could never
>> know)
>> -- I set up the time on the virtual machine where the HBase setup runs
>> properly, no time shifts
>> -- I checked the logs and web UIs to see every processes are running:
>> Hadoop, HBase master, Zookeeper
>>
>> Environment:
>> HBase install is a Debian 32 bit virtual machine, with JDK 1.7.0_17
>> Host machine is Windows 7 with JDK 1.7.0_05
>>
>> but the client program does not work regardless if it's running on the
>> HBase VM or on the host
>>
>> The tiny client is:
>> http://pastebin.com/060Yu2Gz
>>
>> here are the config files:
>> http://pastebin.com/ArVvwU59
>>
>> Please help and tell me what I do wrong, because it has been driving
>> me crazy for about 3 days, and I'm getting very angry about this whole
>> Hadoop stuff, that I cannot even get running a very basic use-case
>> with it.
>>
>> Thanks,
>> Pal
>>

I said this as I saw 127.0.0.1 in your configuration file. The master
references itself in the ZK. If the master finds itself to be "127.0.0.1",
ZK will also have "127.0.0.1".

Now, your request is going to 192.168.0.102 which would be getting resolved
to debian-vm(which is correct actually). But ZK contains 127.0.0.1(courtesy
your config file), which might be getting resolved to localhost. That's why
I said to add that line. Could you please show me your /etc/hosts file once?

Warm Regards,
Tariq
https://mtariq.jux.com/
cloudfront.blogspot.com
On Wed, Mar 20, 2013 at 6:13 AM, Pal Konyves <[EMAIL PROTECTED]> wrote:

> Mohammad, I made the connection from host os to the virtual os where
> HBase is running. the virtual OS is set up with bridged network, so it
> gets it's own local IP address, which in this case was
> HBase VM: 192.168.0.102
> Host os: 192.168.0.101 (I'm not sure, but you will see it in the zookeeper
> log)
>
> I know it works, because http://debian-vm:60010 comes up from Host os
>
> On Wed, Mar 20, 2013 at 1:30 AM, Mohammad Tariq <[EMAIL PROTECTED]>
> wrote:
> > Hello Pal,
> >
> >     Add 127.0.0.1 along with the hostname of your vm, where you are
> running
> > your Hbase, into its /etc/hosts file. You are running Hbase in pseudo
> > distributed mode, but the logs show that the connection request is going
> to
> > some other IP.
> >
> > Warm Regards,
> > Tariq
> > https://mtariq.jux.com/
> > cloudfront.blogspot.com
> >
> >
> > On Wed, Mar 20, 2013 at 5:32 AM, Pal Konyves <[EMAIL PROTECTED]>
> wrote:
> >
> >> Hi,
> >>
> >> I'm new to the list, just registered for this question.
> >>
> >> I'm setting up HBase in pseudo-distributed mode. I can run the hbase
> >> shell locally, and create tables, put some rows, they are present in
> >> the HDFS good.
> >> However, when I try to connect either from the same machine or the
> >> host machine (the HBase setup is on a VM), the client hangs after
> >> connecting to ZooKeeper.
> >>
> >> The console output is:
> >>
> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket connection
> to
> >> server
> >>  debian-vm/192.168.1.102:2181. Will not attempt to authenticate using
> >> SASL (unkn
> >> own error)
> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection
> established
> >> to de
> >> bian-vm/192.168.1.102:2181, initiating session
> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment
> >> complete on s
> >> erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005,
> >> negotiated ti
> >> meout = 180000
> >>  [..then waits forever, then after forever shows:]
> >> org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to
> find
> >> regio
> >>  for stops,,99999999999999 after 10 tries.
> >>
> >> I checked the following pitfalls:
> >> -- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according to
> >> HBase documentation
> >> -- I put 'vm-debian' (the hostname I want to identify my virtual
> >> machine that runs the HBase setup) into the host and virtual machine's
> >> /etc/host file to map the hostname nicely (and it works, because
> >> browser shows Hadoop and HBase info pages)
> >> -- I copied the hadoop related jars from hadoop root and hadoop/lib
> >> into HBase/lib (although they were the same version, but I could never
> >> know)
> >> -- I set up the time on the virtual machine where the HBase setup runs
> >> properly, no time shifts
> >> -- I checked the logs and web UIs to see every processes are running:
> >> Hadoop, HBase master, Zookeeper
> >>
> >> Environment:
> >> HBase install is a Debian 32 bit virtual machine, with JDK 1.7.0_17
> >> Host machine is Windows 7 with JDK 1.7.0_05
> >>
> >> but the client program does not work regardless if it's running on the
> >> HBase VM or on the host
> >>
> >> The tiny client is:
> >> http://pastebin.com/060Yu2Gz
> >>
> >> here are the config files:
> >> http://pastebin.com/ArVvwU59
> >>
> >> Please help and tell me what I do wrong, because it has been driving

okay, it reads for the VM:
192.168.1.102  debian-vm
192.168.1.102  debian
127.0.0.1         localhost

# and some ipv6 setup
For the host machine:
192.168.1.102      debian-vm

shall I set the config files so everywhere it references to debian-vm?
I will try it tomorrow, because it's getting late here.

Pal

On Wed, Mar 20, 2013 at 1:56 AM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> I said this as I saw 127.0.0.1 in your configuration file. The master
> references itself in the ZK. If the master finds itself to be "127.0.0.1",
> ZK will also have "127.0.0.1".
>
> Now, your request is going to 192.168.0.102 which would be getting resolved
> to debian-vm(which is correct actually). But ZK contains 127.0.0.1(courtesy
> your config file), which might be getting resolved to localhost. That's why
> I said to add that line. Could you please show me your /etc/hosts file once?
>
>
>
> Warm Regards,
> Tariq
> https://mtariq.jux.com/
> cloudfront.blogspot.com
>
>
> On Wed, Mar 20, 2013 at 6:13 AM, Pal Konyves <[EMAIL PROTECTED]> wrote:
>
>> Mohammad, I made the connection from host os to the virtual os where
>> HBase is running. the virtual OS is set up with bridged network, so it
>> gets it's own local IP address, which in this case was
>> HBase VM: 192.168.0.102
>> Host os: 192.168.0.101 (I'm not sure, but you will see it in the zookeeper
>> log)
>>
>> I know it works, because http://debian-vm:60010 comes up from Host os
>>
>> On Wed, Mar 20, 2013 at 1:30 AM, Mohammad Tariq <[EMAIL PROTECTED]>
>> wrote:
>> > Hello Pal,
>> >
>> >     Add 127.0.0.1 along with the hostname of your vm, where you are
>> running
>> > your Hbase, into its /etc/hosts file. You are running Hbase in pseudo
>> > distributed mode, but the logs show that the connection request is going
>> to
>> > some other IP.
>> >
>> > Warm Regards,
>> > Tariq
>> > https://mtariq.jux.com/
>> > cloudfront.blogspot.com
>> >
>> >
>> > On Wed, Mar 20, 2013 at 5:32 AM, Pal Konyves <[EMAIL PROTECTED]>
>> wrote:
>> >
>> >> Hi,
>> >>
>> >> I'm new to the list, just registered for this question.
>> >>
>> >> I'm setting up HBase in pseudo-distributed mode. I can run the hbase
>> >> shell locally, and create tables, put some rows, they are present in
>> >> the HDFS good.
>> >> However, when I try to connect either from the same machine or the
>> >> host machine (the HBase setup is on a VM), the client hangs after
>> >> connecting to ZooKeeper.
>> >>
>> >> The console output is:
>> >>
>> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket connection
>> to
>> >> server
>> >>  debian-vm/192.168.1.102:2181. Will not attempt to authenticate using
>> >> SASL (unkn
>> >> own error)
>> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection
>> established
>> >> to de
>> >> bian-vm/192.168.1.102:2181, initiating session
>> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment
>> >> complete on s
>> >> erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005,
>> >> negotiated ti
>> >> meout = 180000
>> >>  [..then waits forever, then after forever shows:]
>> >> org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to
>> find
>> >> regio
>> >>  for stops,,99999999999999 after 10 tries.
>> >>
>> >> I checked the following pitfalls:
>> >> -- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according to
>> >> HBase documentation
>> >> -- I put 'vm-debian' (the hostname I want to identify my virtual
>> >> machine that runs the HBase setup) into the host and virtual machine's
>> >> /etc/host file to map the hostname nicely (and it works, because
>> >> browser shows Hadoop and HBase info pages)
>> >> -- I copied the hadoop related jars from hadoop root and hadoop/lib
>> >> into HBase/lib (although they were the same version, but I could never
>> >> know)
>> >> -- I set up the time on the virtual machine where the HBase setup runs
>> >> properly, no time shifts
>> >> -- I checked the logs and web UIs to see every processes are running:

Yes. Either add "192.168.1.102   localhost" here or just change your config
properties in the config files to contain "debian-vm" at all the places.

No prob. I am also sleepy. It's already 6:40 am here in India :)

Warm Regards,
Tariq
https://mtariq.jux.com/
cloudfront.blogspot.com
On Wed, Mar 20, 2013 at 6:35 AM, Pal Konyves <[EMAIL PROTECTED]> wrote:

> okay, it reads for the VM:
> 192.168.1.102  debian-vm
> 192.168.1.102  debian
> 127.0.0.1         localhost
>
> # and some ipv6 setup
>
>
> For the host machine:
> 192.168.1.102      debian-vm
>
> shall I set the config files so everywhere it references to debian-vm?
> I will try it tomorrow, because it's getting late here.
>
> Pal
>
> On Wed, Mar 20, 2013 at 1:56 AM, Mohammad Tariq <[EMAIL PROTECTED]>
> wrote:
> > I said this as I saw 127.0.0.1 in your configuration file. The master
> > references itself in the ZK. If the master finds itself to be
> "127.0.0.1",
> > ZK will also have "127.0.0.1".
> >
> > Now, your request is going to 192.168.0.102 which would be getting
> resolved
> > to debian-vm(which is correct actually). But ZK contains
> 127.0.0.1(courtesy
> > your config file), which might be getting resolved to localhost. That's
> why
> > I said to add that line. Could you please show me your /etc/hosts file
> once?
> >
> >
> >
> > Warm Regards,
> > Tariq
> > https://mtariq.jux.com/
> > cloudfront.blogspot.com
> >
> >
> > On Wed, Mar 20, 2013 at 6:13 AM, Pal Konyves <[EMAIL PROTECTED]>
> wrote:
> >
> >> Mohammad, I made the connection from host os to the virtual os where
> >> HBase is running. the virtual OS is set up with bridged network, so it
> >> gets it's own local IP address, which in this case was
> >> HBase VM: 192.168.0.102
> >> Host os: 192.168.0.101 (I'm not sure, but you will see it in the
> zookeeper
> >> log)
> >>
> >> I know it works, because http://debian-vm:60010 comes up from Host os
> >>
> >> On Wed, Mar 20, 2013 at 1:30 AM, Mohammad Tariq <[EMAIL PROTECTED]>
> >> wrote:
> >> > Hello Pal,
> >> >
> >> >     Add 127.0.0.1 along with the hostname of your vm, where you are
> >> running
> >> > your Hbase, into its /etc/hosts file. You are running Hbase in pseudo
> >> > distributed mode, but the logs show that the connection request is
> going
> >> to
> >> > some other IP.
> >> >
> >> > Warm Regards,
> >> > Tariq
> >> > https://mtariq.jux.com/
> >> > cloudfront.blogspot.com
> >> >
> >> >
> >> > On Wed, Mar 20, 2013 at 5:32 AM, Pal Konyves <[EMAIL PROTECTED]>
> >> wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I'm new to the list, just registered for this question.
> >> >>
> >> >> I'm setting up HBase in pseudo-distributed mode. I can run the hbase
> >> >> shell locally, and create tables, put some rows, they are present in
> >> >> the HDFS good.
> >> >> However, when I try to connect either from the same machine or the
> >> >> host machine (the HBase setup is on a VM), the client hangs after
> >> >> connecting to ZooKeeper.
> >> >>
> >> >> The console output is:
> >> >>
> >> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Opening socket
> connection
> >> to
> >> >> server
> >> >>  debian-vm/192.168.1.102:2181. Will not attempt to authenticate
> using
> >> >> SASL (unkn
> >> >> own error)
> >> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Socket connection
> >> established
> >> >> to de
> >> >> bian-vm/192.168.1.102:2181, initiating session
> >> >> 13/03/20 00:20:36 INFO zookeeper.ClientCnxn: Session establishment
> >> >> complete on s
> >> >> erver debian-vm/192.168.1.102:2181, sessionid = 0x13d84e02e920005,
> >> >> negotiated ti
> >> >> meout = 180000
> >> >>  [..then waits forever, then after forever shows:]
> >> >> org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to
> >> find
> >> >> regio
> >> >>  for stops,,99999999999999 after 10 tries.
> >> >>
> >> >> I checked the following pitfalls:
> >> >> -- My HBase 94.4 build is compatible with my Hadoop 1.0.4 according
> to
> >> >> HBase documentation
> >> >> -- I put 'vm-debian' (the hostname I want to identify my virtual

Yes. You can connect from any remote client. Try to go through this
link<http://cloudfront.blogspot.in/2012/06/how-to-configure-habse-in-pseudo.html#.UUs3HTWH6IQ>and
see if it helps. If you follow all the steps properly, hopefully
you'll
be able to do it.
Pal Konyves <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> progress! not... I'm still struggling with it. I changed all my hosts
> files have the external ip of the VM and the 127.0.0.1 point to
>
> hostname 'debian' (that was the original name of the machine). I
> changed every config files to use the hostname 'debian'. I formated
> the hdfs, but no luck, the client still hangs. I will probably have to
>
> debug this stuff.
>
> But still, if you have any ideas, please tell me! I have to make
> progress at learning HBase, so if I cannot get it work in
> pseudo-distributed mode, can I connect to it from a remote client in
>
> standalone mode?
>
> Thanks,
> Pal
>
> On Wed, Mar 20, 2013 at 2:09 AM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
>
>>
>> Yes. Either add "192.168.1.102   localhost" here or just change your config
>> properties in the config files to contain "debian-vm" at all the places.
>>
>> No prob. I am also sleepy. It's already 6:40 am here in India :)
>>
>> Warm Regards,
>> Tariq
>> https://mtariq.jux.com/
>> cloudfront.blogspot.com
>>
>>
>> On Wed, Mar 20, 2013 at 6:35 AM, Pal Konyves <[EMAIL PROTECTED]> wrote:
>>
>>
>>> okay, it reads for the VM:
>>> 192.168.1.102  debian-vm
>>> 192.168.1.102  debian
>>> 127.0.0.1         localhost
>>>
>>> # and some ipv6 setup
>>>
>>>
>>> For the host machine:
>>> 192.168.1.102      debian-vm
>>>
>>> shall I set the config files so everywhere it references to debian-vm?
>>>
>>> I will try it tomorrow, because it's getting late here.
>>>
>>> Pal
>>>
>>> On Wed, Mar 20, 2013 at 1:56 AM, Mohammad Tariq <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>> I said this as I saw 127.0.0.1 in your configuration file. The master
>>>>
>>>> references itself in the ZK. If the master finds itself to be
>>>>
>>> "127.0.0.1",
>>>
>>>>
>>>> ZK will also have "127.0.0.1".
>>>>
>>>> Now, your request is going to 192.168.0.102 which would be getting
>>>>
>>>
>>> resolved
>>>
>>>> to debian-vm(which is correct actually). But ZK contains
>>>>
>>> 127.0.0.1(courtesy
>>>
>>>> your config file), which might be getting resolved to localhost. That's
>>>>
>>> why
>>>
>>>>
>>>> I said to add that line. Could you please show me your /etc/hosts file
>>>>
>>> once?
>>>
>>>
>>>
>>> Warm Regards,
>>>>
>>>> Tariq
>>>> https://mtariq.jux.com/
>>>> cloudfront.blogspot.com
>>>>
>>>>
>>>> On Wed, Mar 20, 2013 at 6:13 AM, Pal Konyves <[EMAIL PROTECTED]>
>>>>
>>> wrote:
>>>
>>>
>>>>> Mohammad, I made the connection from host os to the virtual os where
>>>>> HBase is running. the virtual OS is set up with bridged network, so it
>>>>> gets it's own local IP address, which in this case was
>>>>> HBase VM: 192.168.0.102
>>>>>
>>>>> Host os: 192.168.0.101 (I'm not sure, but you will see it in the
>>>>>
>>>> zookeeper
>>>
>>>> log)
>>>>>
>>>>> I know it works, because http://debian-vm:60010 comes up from Host os
>>>>>
>>>>> On Wed, Mar 20, 2013 at 1:30 AM, Mohammad Tariq <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Hello Pal,
>>>>>>
>>>>>> Add 127.0.0.1 along with the hostname of your vm, where you are
>>>>>>
>>>>> running
>>>>>
>>>>>>
>>>>>> your Hbase, into its /etc/hosts file. You are running Hbase in pseudo
>>>>>> distributed mode, but the logs show that the connection request is
>>>>>>
>>>>> going
>>>
>>>> to
>>>>>
>>>>>>
>>>>>> some other IP.
>>>>>>
>>>>>> Warm Regards,
>>>>>> Tariq
>>>>>> https://mtariq.jux.com/
>>>>>> cloudfront.blogspot.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 20, 2013 at 5:32 AM, Pal Konyves <[EMAIL PROTECTED]>
>>>>>>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>>>
>>>>>>> I'm new to the list, just registered for this question.
>>>>>>>
>>>>>>> I'm setting up HBase in pseudo-distributed mode. I can run the hbase
>>>>>>>
>>>>>>> shell locally, and create tables, put some rows, they are present in

All right folks, I got the problem. I set
  <property>
    <name>zookeeper.znode.rootserver</name>
    <value>debian</value>
  </property>

on the Hbase server hbase-site.xml, but not on the client.
So I got messages on ZooKeeper such as:

DEBUG txntype:unknown reqpath:/hbase/root-region-server
[...]

because the client thought the request path of the root-region-server
is /hbase/root-region-server, but it was set up /hbase/debian in fact.
Then I removed the above property from the server, and my simple
client worked fine so far. It just set me back about 1,5 weeks, but no
problem.
However, It would have been useful, if that b*tch client had not just
hung, but actually prompted about a useful message, like the one from
ZooKeeper. What it did show, on the other hand is:

INFO zookeeper.ClientCnxn: Session establishment complete on server
debian/192.168.1.100:2181, sessionid = 0x13d9e353f060006, negotiated
timeout = 180000
[just hang forever]

And in DEBUG mode:
Unable to get data of znode /hbase/root-region-server because node
does not exist (not an error)

You see, it's not an error, it just happens casually, so just hide it
from the user, and even say "(not an error)". Don't even try to repair
anything in your setup going on this path..
All right, thanks for reading my sarcastic afternote :)

Pal

On Thu, Mar 21, 2013 at 5:38 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> Yes. You can connect from any remote client. Try to go through this
> link<http://cloudfront.blogspot.in/2012/06/how-to-configure-habse-in-pseudo.html#.UUs3HTWH6IQ>and
> see if it helps. If you follow all the steps properly, hopefully
> you'll
> be able to do it.
>
>
> Pal Konyves <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> progress! not... I'm still struggling with it. I changed all my hosts
>> files have the external ip of the VM and the 127.0.0.1 point to
>>
>> hostname 'debian' (that was the original name of the machine). I
>> changed every config files to use the hostname 'debian'. I formated
>> the hdfs, but no luck, the client still hangs. I will probably have to
>>
>> debug this stuff.
>>
>> But still, if you have any ideas, please tell me! I have to make
>> progress at learning HBase, so if I cannot get it work in
>> pseudo-distributed mode, can I connect to it from a remote client in
>>
>> standalone mode?
>>
>> Thanks,
>> Pal
>>
>> On Wed, Mar 20, 2013 at 2:09 AM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
>>
>>>
>>> Yes. Either add "192.168.1.102   localhost" here or just change your config
>>> properties in the config files to contain "debian-vm" at all the places.
>>>
>>> No prob. I am also sleepy. It's already 6:40 am here in India :)
>>>
>>> Warm Regards,
>>> Tariq
>>> https://mtariq.jux.com/
>>> cloudfront.blogspot.com
>>>
>>>
>>> On Wed, Mar 20, 2013 at 6:35 AM, Pal Konyves <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>> okay, it reads for the VM:
>>>> 192.168.1.102  debian-vm
>>>> 192.168.1.102  debian
>>>> 127.0.0.1         localhost
>>>>
>>>> # and some ipv6 setup
>>>>
>>>>
>>>> For the host machine:
>>>> 192.168.1.102      debian-vm
>>>>
>>>> shall I set the config files so everywhere it references to debian-vm?
>>>>
>>>> I will try it tomorrow, because it's getting late here.
>>>>
>>>> Pal
>>>>
>>>> On Wed, Mar 20, 2013 at 1:56 AM, Mohammad Tariq <[EMAIL PROTECTED]>
>>>> wrote:
>>>>
>>>>> I said this as I saw 127.0.0.1 in your configuration file. The master
>>>>>
>>>>> references itself in the ZK. If the master finds itself to be
>>>>>
>>>> "127.0.0.1",
>>>>
>>>>>
>>>>> ZK will also have "127.0.0.1".
>>>>>
>>>>> Now, your request is going to 192.168.0.102 which would be getting
>>>>>
>>>>
>>>> resolved
>>>>
>>>>> to debian-vm(which is correct actually). But ZK contains
>>>>>
>>>> 127.0.0.1(courtesy
>>>>
>>>>> your config file), which might be getting resolved to localhost. That's
>>>>>
>>>> why
>>>>
>>>>>
>>>>> I said to add that line. Could you please show me your /etc/hosts file
>>>>>
>>>> once?
>>>>
>>>>
>>>>
>>>> Warm Regards,