Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of hsreekumar@clickable.com
 designates 74.125.149.205 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <SNT118-W19AFAC2AA060284408249ABC300@phx.gbl>
References: <SNT118-W19AFAC2AA060284408249ABC300@phx.gbl>
Date: Wed, 10 Nov 2010 10:33:07 +0530
Message-ID: <AANLkTi=KaufbPOXXvgK5zWSCO58yvYR2AAhLwNW_s7hP@mail.gmail.com>
Subject: Re: Browse filesystem web link exception
From: Hari Sreekumar <hsreekumar@clickable.com>
To: common-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=0016367fb805e2cb510494abc55f

--0016367fb805e2cb510494abc55f
Content-Type: text/plain; charset=ISO-8859-1

Never seen such an error before myself.. some more info would be helpful..
what is the output of jps? Are all daemons running?
What happens if you access HDFS from command line ($HADOOP_HOME/bin/hadoop
dfs -ls /)? Are you able to -put files into HDFS from command line?

hari

On Wed, Nov 10, 2010 at 4:10 AM, Fabio Miranda <fabiomiranda@live.com>wrote:

>
> Hello,
>
> Browsing a single setup instance on web port 50070, click on "browse
> filesystem" and got this error:
>
> HTTP ERROR: 500n must be positive
> RequestURI=/nn_browsedfscontent.jspCaused
> by:java.lang.IllegalArgumentException: n must be positive
>        at java.util.Random.nextInt(Random.java:250)
>        at
> org.apache.hadoop.net.NetworkTopology.chooseRandom(NetworkTopology.java:540)
>        at
> org.apache.hadoop.net.NetworkTopology.chooseRandom(NetworkTopology.java:508)
>        at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getRandomDatanode(FSNamesystem.java:3411)
>        at
> org.apache.hadoop.hdfs.server.namenode.NamenodeJspHelper.redirectToRandomDataNode(NamenodeJspHelper.java:288)
>        at
> org.apache.hadoop.hdfs.server.namenode.nn_005fbrowsedfscontent_jsp._jspService(nn_005fbrowsedfscontent_jsp.java:74)
>        at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>        at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
>        at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124)
>        at
> org.apache.hadoop.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:767)
>        at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)
>        at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)
>        at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>        at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>        at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
>        at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
>        at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
>        at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>        at org.mortbay.jetty.Server.handle(Server.java:324)
>        at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
>        at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
>        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
>        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
>        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
>        at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
>        at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
>
> Powered by Jetty://
>
> what could be the cause ?
>
> thanks,
>

--0016367fb805e2cb510494abc55f--