Thanks for your help. I tried to change the port however I couldn't find
the configuration of port in the manager (Please see attachment though the
main language is Korean).
[image: 본문 이미지 1]
I can see configuration xml files in /var/run/cloudera-scm-agent/process/,
however I think this is the place for the currently running processes.
So, I though if I put the port
configuration /etc/hbase/conf.cloudera.hbase1/hbase-site.xml or
/etc/hbase/conf.dist/hbase-site.xml, then the value ccould be propagated to
there but it didn't.
Let me know where to configure the master port.
Thanks,
Jun
2013/4/10 Philip Zeyliger <philip@cloudera.com>
Hi folks,
*Caused by: java.net.BindException: Address already in use*
*
*
That error in the logs more or less uniquely means that the port is
already being used by some other process. Here is how I tend to check what
ports are being used:
$sudo lsof -P -n | grep LISTEN | grep 60030
java 28283 hbase 312u IPv4 148789875 0t0
TCP *:60030 (LISTEN)
You should check the configuration to figure out what ports HBase is
trying to use, and who they're used by. If it's a different HBase process,
then probably you installed the "hbase-master" package from CDH and it's
starting HBase for you when your machine boots. Turn that off with
"chkconfig" and "service hbase-master stop". If it's some other random
process, you can either kill it or change the port numbers in the CM
configuration screens.
Cheers,
-- Philip
*Caused by: java.net.BindException: Address already in use*
*
*
That error in the logs more or less uniquely means that the port is
already being used by some other process. Here is how I tend to check what
ports are being used:
$sudo lsof -P -n | grep LISTEN | grep 60030
java 28283 hbase 312u IPv4 148789875 0t0
TCP *:60030 (LISTEN)
You should check the configuration to figure out what ports HBase is
trying to use, and who they're used by. If it's a different HBase process,
then probably you installed the "hbase-master" package from CDH and it's
starting HBase for you when your machine boots. Turn that off with
"chkconfig" and "service hbase-master stop". If it's some other random
process, you can either kill it or change the port numbers in the CM
configuration screens.
Cheers,
-- Philip
On Tue, Apr 9, 2013 at 12:13 AM, Anupam Ranjan wrote:
I still have the same issue...could not get any solution from Cloudera
side.
*Anupam Ranjan*
I still have the same issue...could not get any solution from Cloudera
side.
On 9 April 2013 12:39, j wrote:
.log.out shows like belo
.log.out shows like belo
*Anupam Ranjan*
