chukwa-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DKN <>
Subject Re: A demo setup on a single linux server
Date Wed, 01 Jun 2011 11:25:11 GMT
Thanks Eric,

The 1st and 2nd problem doesn't appear anymore. I'm using hadoop 0.20.2 and
also exported the following environment variable :
export HADOOP_CLASSPATH=${HADOOP_HOME}/lib/json-simple-1.1.jar:
It didn't appear to be a file permission issue for json-simple-1.1.jar.

The hicc app has been giving some more problems today.

HICC. 1 -> No data available in HBase.

I checked this using hbase shell and doing a scan 'Hadoop' (or other

I understand that the chukwa collector writes to HBase, simultaneously along
with writing the temp sync files to HDFS (please correct me if I am wrong ..
). The collector logs doesn't indicate anything of such activity with HBase.

I have uncommented the HBaseWriter parameters in chukwa-collector-conf.xml.

Here's the initialization console output when I start the collector. (Note
that I have the correct value for CHUKWA_DATA_DIR .. ).

root@xtest12:/home/dev/chukwa-0.5.0-incubating/bin# WARN: option may not exist; val = /chukwa
        chukwaRootDir null URI
        nullWriter.dataRate Time
WARN: option may not exist; val = /chukwa/temp
        chukwaRootDir null
        nullWriter.dataRate Time
        chukwaCollector.tee.port Integral
OK chukwaCollector.http.port [Integral] = 8080
OK chukwaCollector.pipeline [ClassName list] =
OK chukwaCollector.rotateInterval [Time] = 300000
WARN: option hbase.demux.package may not exist; val =
Guesses: URI
        nullWriter.dataRate Time
        CHUKWA_DATA_DIR null
WARN: option hbase.writer.halt.on.schema.mismatch may not exist; val = false
        nullWriter.dataRate Time URI
        chukwaCollector.http.threads Integral
WARN: option hbase.writer.verify.schema may not exist; val = false
        nullWriter.dataRate Time URI
        httpConnector.asyncAcks Boolean
OK writer.hdfs.filesystem [URI] = hdfs://localhost:9000/
No checker rules for:   chukwaCollector.outputDir
2011-06-01 15:03:08.570::INFO:  Logging to STDERR via
2011-06-01 15:03:08.616::INFO:  jetty-6.1.11
2011-06-01 15:03:46.083::INFO:  Started SelectChannelConnector@
started Chukwa http collector on port 8080


HICC. 2-> When I now access the front page (http://localhost:4080/hicc) - [
This somehow appeared to work for me yesterday after some time .. ].
Probably if we address the first issue, this problem may disappear ..

	at java.util.HashMap$HashIterator.nextEntry(
	at java.util.HashMap$
	at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:100)
	at org.apache.jasper.runtime.HttpJspBase.service(
	at javax.servlet.http.HttpServlet.service(
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(
	at org.apache.jasper.servlet.JspServlet.service(
	at javax.servlet.http.HttpServlet.service(
	at org.mortbay.jetty.servlet.ServletHolder.handle(

HICC.3 - hicc application is available only on localhost.

If I try to access hicc on another server, jetty doesn't seem to honor the
request. (for example http://xtest:4080/hicc is not accessible from another
box .. ). Is there a specific setting to be done here in auth.conf ?

Cheers, DKN

View this message in context:
Sent from the Chukwa - Users mailing list archive at

View raw message