okay, it reads for the VM:
# and some ipv6 setup
For the host machine:
shall I set the config files so everywhere it references to debian-vm?
I will try it tomorrow, because it's getting late here.
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,
> 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
>> 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]>
>> > Hello Pal,
>> > Add 127.0.0.1 along with the hostname of your vm, where you are
>> > 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
>> > 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]>
>> >> 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
>> >> 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
>> >> 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
>> >> 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: