[ https://issues.apache.org/jira/browse/HBASE-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ramkrishna.s.vasudevan resolved HBASE-8168. ------------------------------------------- Resolution: Invalid Pls raise in User list. > HMaster is not Running. > ----------------------- > > Key: HBASE-8168 > URL: https://issues.apache.org/jira/browse/HBASE-8168 > Project: HBase > Issue Type: Bug > Components: shell > Affects Versions: 0.94.4 > Environment: Ubuntu 12.4 > Reporter: Nallapati T Krishna > Fix For: 0.94.4 > > Attachments: Hbase Error.png > > > When I used to start Hbase, for the first time Hmaster is running. If i type > JPS for second consecutive time, Hmaster is not working. It is showing some > thing like the below. > rg.apache.zookeeper.ClientCnxn: Opening socket connection to server > ubuntu-1/172.16.78.122:2222. Will not attempt to authenticate using SASL > (unknown error) > 2013-03-20 22:04:33,491 INFO org.apache.zookeeper.ClientCnxn: Socket > connection established to ubuntu-1/172.16.78.122:2222, initiating session > 2013-03-20 22:04:33,492 INFO org.apache.zookeeper.ClientCnxn: Unable to read > additional data from server sessionid 0x0, likely server has closed socket, > closing socket connection and attempting reconnect > 2013-03-20 22:04:33,592 WARN > org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient > ZooKeeper exception: > org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode > = ConnectionLoss for /hbase > 2013-03-20 22:04:33,593 INFO org.apache.hadoop.hbase.util.RetryCounter: > Sleeping 4000ms before retry #2... > 2013-03-20 22:04:33,760 INFO org.apache.zookeeper.ClientCnxn: Opening socket > connection to server CLBBLR-6196/172.16.78.91:2222. Will not attempt to > authenticate using SASL (unknown error) > 2013-03-20 22:04:33,760 INFO org.apache.zookeeper.ClientCnxn: Socket > connection established to CLBBLR-6196/172.16.78.91:2222, initiating session > 2013-03-20 22:04:33,761 INFO org.apache.zookeeper.ClientCnxn: Unable to read > additional data from server sessionid 0x0, likely server has closed socket, > closing socket connection and attempting reconnect > 2013-03-20 22:04:34,840 INFO org.apache.zookeeper.ClientCnxn: Opening socket > connection to server CLBBLR-6176/172.16.78.136:2222. Will not attempt to > authenticate using SASL (unknown error) > 2013-03-20 22:04:34,840 INFO org.apache.zookeeper.ClientCnxn: Socket > connection established to CLBBLR-6176/172.16.78.136:2222, initiating session > 2013-03-20 22:04:34,841 INFO org.apache.zookeeper.ClientCnxn: Unable to read > additional data from server sessionid 0x0, likely server has closed socket, > closing socket connection and attempting reconnect > 2013-03-20 22:04:36,026 INFO org.apache.zookeeper.ClientCnxn: Opening socket > connection to server ubuntu-1/172.16.78.122:2222. Will not attempt to > authenticate using SASL (unknown error) > 2013-03-20 22:04:36,027 INFO org.apache.zookeeper.ClientCnxn: Socket > connection established to ubuntu-1/172.16.78.122:2222, initiating session > 2013-03-20 22:04:36,028 INFO org.apache.zookeeper.ClientCnxn: Unable to read > additional data from server sessionid 0x0, likely server has closed socket, > closing socket connection and attempting reconnect > 2013-03-20 22:04:36,570 INFO org.apache.zookeeper.ClientCnxn: Opening socket > connection to server CLBBLR-6196/172.16.78.91:2222. Will not attempt to > authenticate using SASL (unknown error) > 2013-03-20 22:04:36,571 INFO org.apache.zookeeper.ClientCnxn: Socket > connection established to CLBBLR-6196/172.16.78.91:2222, initiating session > 2013-03-20 22:04:36,572 INFO org.apache.zookeeper.ClientCnxn: Unable to read > additional data from server sessionid 0x0, likely server has closed socket, > closing socket connection and attempting reconnect > 2013-03-20 22:04:37,505 INFO org.apache.zookeeper.ClientCnxn: Op > As discussed.Hbase is starting properly without any issue. When we are trying > to list the tables in Hbase or create the table, HMaster is not running. > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira