You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by Mark Vigeant <ma...@riskmetrics.com> on 2009/12/01 16:41:06 UTC
Web Interface Not Working
Hello-
I have a namenode/JT with 3 slaves running cloudera's 0.20 release. Everything was going fine until yesterday when the web interface randomly went down (the http://hostname:50070 and http://hostname:50030). To my knowledge everything else is fine, but I wanted to know if anyone else has experienced a similar problem / what can I do to fix this?
Thanks!
Mark Vigeant
RiskMetrics Group, Inc.
This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.
RE: Web Interface Not Working
Posted by Mark Vigeant <ma...@riskmetrics.com>.
Steve,
I apologize in advance for being a total n00b right here, but which classpath are we talking about? Should I be modifying the classpath in HADOOP-ENV or should I be modifying the java classpath?
Thanks
-Mark
-----Original Message-----
From: Steve Loughran [mailto:stevel@apache.org]
Sent: Wednesday, December 02, 2009 5:21 AM
To: common-user@hadoop.apache.org
Subject: Re: Web Interface Not Working
Mark Vigeant wrote:
> Todd,
>
> I followed your suggestion, shut down everything, restarted it, and the UI is still not there. Jps shows NN and JT working though.
>
Web UI is precompiled JSP on jetty; the rest of the system doesn't need
it, and if the JSP JARs aren't on the classpath, Jetty won't behave.
* make sure that you have only one version of Jetty on your classpath
* make sure you only have one set of JSP JARs on the CP
* make sure the jetty jars are all consistent (not mixing versions)
* check that the various servlets are live (the TT and DNs have them).
No servlets: jetty is down.
I think you can tell Jetty to log at more detail, worth doing if you are
trying to track down problems.
This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.
Re: Web Interface Not Working
Posted by Farhan Husain <fa...@csebuet.org>.
Thanks a lot Philip!
On Mon, Dec 14, 2009 at 7:13 PM, Philip Zeyliger <ph...@cloudera.com>wrote:
> I believe {dfs|mapred.job.tracker}.http.address are the relevant
> configuration settings.
>
> <property>
> <name>dfs.http.address</name>
> <value>0.0.0.0:50070</value>
> <description>
> The address and the base port where the dfs namenode web ui will listen
> on.
> If the port is 0 then the server will start on a free port.
> </description>
> </property>
>
> <property>
> <name>mapred.job.tracker.http.address</name>
> <value>0.0.0.0:50030</value>
> <description>
> The job tracker http server address and port the server will listen on.
> If the port is 0 then the server will start on a free port.
> </description>
> </property>
>
>
>
> On Mon, Dec 14, 2009 at 5:10 PM, Farhan Husain
> <fa...@csebuet.org> wrote:
> > Guys,
> >
> > I know this is a silly question but how do I bind the web interfaces to
> any
> > other hostname than localhost? I tried to find some documentation on it
> but
> > failed. Please help.
> >
> > Thanks,
> > Farhan
> >
> > On Thu, Dec 3, 2009 at 2:56 PM, Mark Vigeant
> > <ma...@riskmetrics.com>wrote:
> >
> >> Thanks Steve!
> >>
> >> It's all working now. The problem was that I 2 different webapps folders
> >> for whatever reason and it was reading the "wrong one"
> >>
> >> -Mark
> >>
> >> -----Original Message-----
> >> From: Steve Loughran [mailto:stevel@apache.org]
> >> Sent: Wednesday, December 02, 2009 5:21 AM
> >> To: common-user@hadoop.apache.org
> >> Subject: Re: Web Interface Not Working
> >>
> >> Mark Vigeant wrote:
> >> > Todd,
> >> >
> >> > I followed your suggestion, shut down everything, restarted it, and
> the
> >> UI is still not there. Jps shows NN and JT working though.
> >> >
> >>
> >> Web UI is precompiled JSP on jetty; the rest of the system doesn't need
> >> it, and if the JSP JARs aren't on the classpath, Jetty won't behave.
> >> * make sure that you have only one version of Jetty on your classpath
> >> * make sure you only have one set of JSP JARs on the CP
> >> * make sure the jetty jars are all consistent (not mixing versions)
> >> * check that the various servlets are live (the TT and DNs have them).
> >> No servlets: jetty is down.
> >>
> >> I think you can tell Jetty to log at more detail, worth doing if you are
> >> trying to track down problems.
> >>
> >> This email message and any attachments are for the sole use of the
> intended
> >> recipients and may contain proprietary and/or confidential information
> which
> >> may be privileged or otherwise protected from disclosure. Any
> unauthorized
> >> review, use, disclosure or distribution is prohibited. If you are not an
> >> intended recipient, please contact the sender by reply email and destroy
> the
> >> original message and any copies of the message as well as any
> attachments to
> >> the original message.
> >>
> >
>
Re: Web Interface Not Working
Posted by Philip Zeyliger <ph...@cloudera.com>.
I believe {dfs|mapred.job.tracker}.http.address are the relevant
configuration settings.
<property>
<name>dfs.http.address</name>
<value>0.0.0.0:50070</value>
<description>
The address and the base port where the dfs namenode web ui will listen on.
If the port is 0 then the server will start on a free port.
</description>
</property>
<property>
<name>mapred.job.tracker.http.address</name>
<value>0.0.0.0:50030</value>
<description>
The job tracker http server address and port the server will listen on.
If the port is 0 then the server will start on a free port.
</description>
</property>
On Mon, Dec 14, 2009 at 5:10 PM, Farhan Husain
<fa...@csebuet.org> wrote:
> Guys,
>
> I know this is a silly question but how do I bind the web interfaces to any
> other hostname than localhost? I tried to find some documentation on it but
> failed. Please help.
>
> Thanks,
> Farhan
>
> On Thu, Dec 3, 2009 at 2:56 PM, Mark Vigeant
> <ma...@riskmetrics.com>wrote:
>
>> Thanks Steve!
>>
>> It's all working now. The problem was that I 2 different webapps folders
>> for whatever reason and it was reading the "wrong one"
>>
>> -Mark
>>
>> -----Original Message-----
>> From: Steve Loughran [mailto:stevel@apache.org]
>> Sent: Wednesday, December 02, 2009 5:21 AM
>> To: common-user@hadoop.apache.org
>> Subject: Re: Web Interface Not Working
>>
>> Mark Vigeant wrote:
>> > Todd,
>> >
>> > I followed your suggestion, shut down everything, restarted it, and the
>> UI is still not there. Jps shows NN and JT working though.
>> >
>>
>> Web UI is precompiled JSP on jetty; the rest of the system doesn't need
>> it, and if the JSP JARs aren't on the classpath, Jetty won't behave.
>> * make sure that you have only one version of Jetty on your classpath
>> * make sure you only have one set of JSP JARs on the CP
>> * make sure the jetty jars are all consistent (not mixing versions)
>> * check that the various servlets are live (the TT and DNs have them).
>> No servlets: jetty is down.
>>
>> I think you can tell Jetty to log at more detail, worth doing if you are
>> trying to track down problems.
>>
>> This email message and any attachments are for the sole use of the intended
>> recipients and may contain proprietary and/or confidential information which
>> may be privileged or otherwise protected from disclosure. Any unauthorized
>> review, use, disclosure or distribution is prohibited. If you are not an
>> intended recipient, please contact the sender by reply email and destroy the
>> original message and any copies of the message as well as any attachments to
>> the original message.
>>
>
Re: Web Interface Not Working
Posted by Farhan Husain <fa...@csebuet.org>.
Guys,
I know this is a silly question but how do I bind the web interfaces to any
other hostname than localhost? I tried to find some documentation on it but
failed. Please help.
Thanks,
Farhan
On Thu, Dec 3, 2009 at 2:56 PM, Mark Vigeant
<ma...@riskmetrics.com>wrote:
> Thanks Steve!
>
> It's all working now. The problem was that I 2 different webapps folders
> for whatever reason and it was reading the "wrong one"
>
> -Mark
>
> -----Original Message-----
> From: Steve Loughran [mailto:stevel@apache.org]
> Sent: Wednesday, December 02, 2009 5:21 AM
> To: common-user@hadoop.apache.org
> Subject: Re: Web Interface Not Working
>
> Mark Vigeant wrote:
> > Todd,
> >
> > I followed your suggestion, shut down everything, restarted it, and the
> UI is still not there. Jps shows NN and JT working though.
> >
>
> Web UI is precompiled JSP on jetty; the rest of the system doesn't need
> it, and if the JSP JARs aren't on the classpath, Jetty won't behave.
> * make sure that you have only one version of Jetty on your classpath
> * make sure you only have one set of JSP JARs on the CP
> * make sure the jetty jars are all consistent (not mixing versions)
> * check that the various servlets are live (the TT and DNs have them).
> No servlets: jetty is down.
>
> I think you can tell Jetty to log at more detail, worth doing if you are
> trying to track down problems.
>
> This email message and any attachments are for the sole use of the intended
> recipients and may contain proprietary and/or confidential information which
> may be privileged or otherwise protected from disclosure. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not an
> intended recipient, please contact the sender by reply email and destroy the
> original message and any copies of the message as well as any attachments to
> the original message.
>
RE: Web Interface Not Working
Posted by Mark Vigeant <ma...@riskmetrics.com>.
Thanks Steve!
It's all working now. The problem was that I 2 different webapps folders for whatever reason and it was reading the "wrong one"
-Mark
-----Original Message-----
From: Steve Loughran [mailto:stevel@apache.org]
Sent: Wednesday, December 02, 2009 5:21 AM
To: common-user@hadoop.apache.org
Subject: Re: Web Interface Not Working
Mark Vigeant wrote:
> Todd,
>
> I followed your suggestion, shut down everything, restarted it, and the UI is still not there. Jps shows NN and JT working though.
>
Web UI is precompiled JSP on jetty; the rest of the system doesn't need
it, and if the JSP JARs aren't on the classpath, Jetty won't behave.
* make sure that you have only one version of Jetty on your classpath
* make sure you only have one set of JSP JARs on the CP
* make sure the jetty jars are all consistent (not mixing versions)
* check that the various servlets are live (the TT and DNs have them).
No servlets: jetty is down.
I think you can tell Jetty to log at more detail, worth doing if you are
trying to track down problems.
This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.
Re: Web Interface Not Working
Posted by Steve Loughran <st...@apache.org>.
Mark Vigeant wrote:
> Todd,
>
> I followed your suggestion, shut down everything, restarted it, and the UI is still not there. Jps shows NN and JT working though.
>
Web UI is precompiled JSP on jetty; the rest of the system doesn't need
it, and if the JSP JARs aren't on the classpath, Jetty won't behave.
* make sure that you have only one version of Jetty on your classpath
* make sure you only have one set of JSP JARs on the CP
* make sure the jetty jars are all consistent (not mixing versions)
* check that the various servlets are live (the TT and DNs have them).
No servlets: jetty is down.
I think you can tell Jetty to log at more detail, worth doing if you are
trying to track down problems.
RE: Web Interface Not Working
Posted by Mark Vigeant <ma...@riskmetrics.com>.
Todd,
I followed your suggestion, shut down everything, restarted it, and the UI is still not there. Jps shows NN and JT working though.
-----Original Message-----
From: Todd Lipcon [mailto:todd@cloudera.com]
Sent: Tuesday, December 01, 2009 2:34 PM
To: common-user@hadoop.apache.org
Subject: Re: Web Interface Not Working
Hi Mark,
My pessimistic guess is that, if you're in this state, other things are
probably not working correctly either.
If you can afford a bit of downtime (sounds like a dev cluster) I'd restart
the daemons and see if the web UIs reappear. They most likely will either
reappear, or the daemons will fail to start, is my guess :)
-Todd
On Tue, Dec 1, 2009 at 11:31 AM, Mark Vigeant
<ma...@riskmetrics.com>wrote:
> Todd,
>
> They appear to be in the same place... the one thing I did change is I put
> my $HADOOP_HOME in my hbase classpath. I doubt that would do anything
> though.
>
> Either way, I can live without it. I just like the ability to see what's
> going on in a nicely formatted way. This could be my excuse to set up
> cloudera desktop, heh.
>
> -Mark
>
> -----Original Message-----
> From: Todd Lipcon [mailto:todd@cloudera.com]
> Sent: Tuesday, December 01, 2009 2:14 PM
> To: common-user@hadoop.apache.org
> Subject: Re: Web Interface Not Working
>
> Hi Mark,
>
> Very strange. I've only seen this behavior when I've removed the hadoop
> jars
> while the daemon was still running. Can you verify that the jars are still
> in place where you expect them and haven't been moved, etc?
>
> -Todd
>
> On Tue, Dec 1, 2009 at 11:12 AM, Mark Vigeant
> <ma...@riskmetrics.com>wrote:
>
> > Hey Todd,
> >
> > Yes, jobs are working. In fact, I have hbase running on top of it just
> fine
> > right now, so I'm sort of confused. Jps shows the the namenode and
> > jobtracker are running, and here is what curl
> http://127.0.0.1:50030/print out:
> > <HTML><HEAD><TITLE>Directory: /</TITLE></HEAD><BODY>
> > <H1>Directory: /</H1><TABLE BORDER=0><TR><TD><A
> > HREF="/WEB-INF">WEB-INF/ </TD><TD ALIGN=right>4096
> > bytes </TD><TD>Nov 30, 2009 $:58:56 PM</TD></TR>
> > </TABLE>
> > </BODY></HTML>
> >
> > For the record, when I said the UI wasn't working, I meant I saw
> > "directory..." etc, as you would expect from looking at the HTML above.
> > Thanks!
> >
> > -Mark
> >
> > -----Original Message-----
> > From: Todd Lipcon [mailto:todd@cloudera.com]
> > Sent: Tuesday, December 01, 2009 1:45 PM
> > To: common-user@hadoop.apache.org
> > Subject: Re: Web Interface Not Working
> >
> > Hi Mark,
> >
> > Both web UIs went down but jobs can still be submitted, etc? This seems
> > like
> > a problem external to Hadoop, since the JT (port 50030) and NN (port
> 50070)
> > are entirely separate processes. If they both became inaccessible at the
> > same time, perhaps a firewall rule was added that inadvertently blocked
> > them?
> >
> > If you ssh into the machine and run "jps", can you see the NN and JT
> > running? From that machine can you 'curl http://127.0.0.1:50030/' ?
> >
> > -Todd
> >
> > On Tue, Dec 1, 2009 at 7:41 AM, Mark Vigeant
> > <ma...@riskmetrics.com>wrote:
> >
> > > Hello-
> > >
> > > I have a namenode/JT with 3 slaves running cloudera's 0.20 release.
> > > Everything was going fine until yesterday when the web interface
> randomly
> > > went down (the http://hostname:50070 and http://hostname:50030). To my
> > > knowledge everything else is fine, but I wanted to know if anyone else
> > has
> > > experienced a similar problem / what can I do to fix this?
> > >
> > > Thanks!
> > >
> > > Mark Vigeant
> > > RiskMetrics Group, Inc.
> > >
> > >
> > > This email message and any attachments are for the sole use of the
> > intended
> > > recipients and may contain proprietary and/or confidential information
> > which
> > > may be privileged or otherwise protected from disclosure. Any
> > unauthorized
> > > review, use, disclosure or distribution is prohibited. If you are not
> an
> > > intended recipient, please contact the sender by reply email and
> destroy
> > the
> > > original message and any copies of the message as well as any
> attachments
> > to
> > > the original message.
> > >
> >
> > This email message and any attachments are for the sole use of the
> intended
> > recipients and may contain proprietary and/or confidential information
> which
> > may be privileged or otherwise protected from disclosure. Any
> unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not an
> > intended recipient, please contact the sender by reply email and destroy
> the
> > original message and any copies of the message as well as any attachments
> to
> > the original message.
> >
>
> This email message and any attachments are for the sole use of the intended
> recipients and may contain proprietary and/or confidential information which
> may be privileged or otherwise protected from disclosure. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not an
> intended recipient, please contact the sender by reply email and destroy the
> original message and any copies of the message as well as any attachments to
> the original message.
>
This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.
Re: Web Interface Not Working
Posted by Todd Lipcon <to...@cloudera.com>.
Hi Mark,
My pessimistic guess is that, if you're in this state, other things are
probably not working correctly either.
If you can afford a bit of downtime (sounds like a dev cluster) I'd restart
the daemons and see if the web UIs reappear. They most likely will either
reappear, or the daemons will fail to start, is my guess :)
-Todd
On Tue, Dec 1, 2009 at 11:31 AM, Mark Vigeant
<ma...@riskmetrics.com>wrote:
> Todd,
>
> They appear to be in the same place... the one thing I did change is I put
> my $HADOOP_HOME in my hbase classpath. I doubt that would do anything
> though.
>
> Either way, I can live without it. I just like the ability to see what's
> going on in a nicely formatted way. This could be my excuse to set up
> cloudera desktop, heh.
>
> -Mark
>
> -----Original Message-----
> From: Todd Lipcon [mailto:todd@cloudera.com]
> Sent: Tuesday, December 01, 2009 2:14 PM
> To: common-user@hadoop.apache.org
> Subject: Re: Web Interface Not Working
>
> Hi Mark,
>
> Very strange. I've only seen this behavior when I've removed the hadoop
> jars
> while the daemon was still running. Can you verify that the jars are still
> in place where you expect them and haven't been moved, etc?
>
> -Todd
>
> On Tue, Dec 1, 2009 at 11:12 AM, Mark Vigeant
> <ma...@riskmetrics.com>wrote:
>
> > Hey Todd,
> >
> > Yes, jobs are working. In fact, I have hbase running on top of it just
> fine
> > right now, so I'm sort of confused. Jps shows the the namenode and
> > jobtracker are running, and here is what curl
> http://127.0.0.1:50030/print out:
> > <HTML><HEAD><TITLE>Directory: /</TITLE></HEAD><BODY>
> > <H1>Directory: /</H1><TABLE BORDER=0><TR><TD><A
> > HREF="/WEB-INF">WEB-INF/ </TD><TD ALIGN=right>4096
> > bytes </TD><TD>Nov 30, 2009 $:58:56 PM</TD></TR>
> > </TABLE>
> > </BODY></HTML>
> >
> > For the record, when I said the UI wasn't working, I meant I saw
> > "directory..." etc, as you would expect from looking at the HTML above.
> > Thanks!
> >
> > -Mark
> >
> > -----Original Message-----
> > From: Todd Lipcon [mailto:todd@cloudera.com]
> > Sent: Tuesday, December 01, 2009 1:45 PM
> > To: common-user@hadoop.apache.org
> > Subject: Re: Web Interface Not Working
> >
> > Hi Mark,
> >
> > Both web UIs went down but jobs can still be submitted, etc? This seems
> > like
> > a problem external to Hadoop, since the JT (port 50030) and NN (port
> 50070)
> > are entirely separate processes. If they both became inaccessible at the
> > same time, perhaps a firewall rule was added that inadvertently blocked
> > them?
> >
> > If you ssh into the machine and run "jps", can you see the NN and JT
> > running? From that machine can you 'curl http://127.0.0.1:50030/' ?
> >
> > -Todd
> >
> > On Tue, Dec 1, 2009 at 7:41 AM, Mark Vigeant
> > <ma...@riskmetrics.com>wrote:
> >
> > > Hello-
> > >
> > > I have a namenode/JT with 3 slaves running cloudera's 0.20 release.
> > > Everything was going fine until yesterday when the web interface
> randomly
> > > went down (the http://hostname:50070 and http://hostname:50030). To my
> > > knowledge everything else is fine, but I wanted to know if anyone else
> > has
> > > experienced a similar problem / what can I do to fix this?
> > >
> > > Thanks!
> > >
> > > Mark Vigeant
> > > RiskMetrics Group, Inc.
> > >
> > >
> > > This email message and any attachments are for the sole use of the
> > intended
> > > recipients and may contain proprietary and/or confidential information
> > which
> > > may be privileged or otherwise protected from disclosure. Any
> > unauthorized
> > > review, use, disclosure or distribution is prohibited. If you are not
> an
> > > intended recipient, please contact the sender by reply email and
> destroy
> > the
> > > original message and any copies of the message as well as any
> attachments
> > to
> > > the original message.
> > >
> >
> > This email message and any attachments are for the sole use of the
> intended
> > recipients and may contain proprietary and/or confidential information
> which
> > may be privileged or otherwise protected from disclosure. Any
> unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not an
> > intended recipient, please contact the sender by reply email and destroy
> the
> > original message and any copies of the message as well as any attachments
> to
> > the original message.
> >
>
> This email message and any attachments are for the sole use of the intended
> recipients and may contain proprietary and/or confidential information which
> may be privileged or otherwise protected from disclosure. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not an
> intended recipient, please contact the sender by reply email and destroy the
> original message and any copies of the message as well as any attachments to
> the original message.
>
RE: Web Interface Not Working
Posted by Mark Vigeant <ma...@riskmetrics.com>.
Todd,
They appear to be in the same place... the one thing I did change is I put my $HADOOP_HOME in my hbase classpath. I doubt that would do anything though.
Either way, I can live without it. I just like the ability to see what's going on in a nicely formatted way. This could be my excuse to set up cloudera desktop, heh.
-Mark
-----Original Message-----
From: Todd Lipcon [mailto:todd@cloudera.com]
Sent: Tuesday, December 01, 2009 2:14 PM
To: common-user@hadoop.apache.org
Subject: Re: Web Interface Not Working
Hi Mark,
Very strange. I've only seen this behavior when I've removed the hadoop jars
while the daemon was still running. Can you verify that the jars are still
in place where you expect them and haven't been moved, etc?
-Todd
On Tue, Dec 1, 2009 at 11:12 AM, Mark Vigeant
<ma...@riskmetrics.com>wrote:
> Hey Todd,
>
> Yes, jobs are working. In fact, I have hbase running on top of it just fine
> right now, so I'm sort of confused. Jps shows the the namenode and
> jobtracker are running, and here is what curl http://127.0.0.1:50030/print out:
> <HTML><HEAD><TITLE>Directory: /</TITLE></HEAD><BODY>
> <H1>Directory: /</H1><TABLE BORDER=0><TR><TD><A
> HREF="/WEB-INF">WEB-INF/ </TD><TD ALIGN=right>4096
> bytes </TD><TD>Nov 30, 2009 $:58:56 PM</TD></TR>
> </TABLE>
> </BODY></HTML>
>
> For the record, when I said the UI wasn't working, I meant I saw
> "directory..." etc, as you would expect from looking at the HTML above.
> Thanks!
>
> -Mark
>
> -----Original Message-----
> From: Todd Lipcon [mailto:todd@cloudera.com]
> Sent: Tuesday, December 01, 2009 1:45 PM
> To: common-user@hadoop.apache.org
> Subject: Re: Web Interface Not Working
>
> Hi Mark,
>
> Both web UIs went down but jobs can still be submitted, etc? This seems
> like
> a problem external to Hadoop, since the JT (port 50030) and NN (port 50070)
> are entirely separate processes. If they both became inaccessible at the
> same time, perhaps a firewall rule was added that inadvertently blocked
> them?
>
> If you ssh into the machine and run "jps", can you see the NN and JT
> running? From that machine can you 'curl http://127.0.0.1:50030/' ?
>
> -Todd
>
> On Tue, Dec 1, 2009 at 7:41 AM, Mark Vigeant
> <ma...@riskmetrics.com>wrote:
>
> > Hello-
> >
> > I have a namenode/JT with 3 slaves running cloudera's 0.20 release.
> > Everything was going fine until yesterday when the web interface randomly
> > went down (the http://hostname:50070 and http://hostname:50030). To my
> > knowledge everything else is fine, but I wanted to know if anyone else
> has
> > experienced a similar problem / what can I do to fix this?
> >
> > Thanks!
> >
> > Mark Vigeant
> > RiskMetrics Group, Inc.
> >
> >
> > This email message and any attachments are for the sole use of the
> intended
> > recipients and may contain proprietary and/or confidential information
> which
> > may be privileged or otherwise protected from disclosure. Any
> unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not an
> > intended recipient, please contact the sender by reply email and destroy
> the
> > original message and any copies of the message as well as any attachments
> to
> > the original message.
> >
>
> This email message and any attachments are for the sole use of the intended
> recipients and may contain proprietary and/or confidential information which
> may be privileged or otherwise protected from disclosure. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not an
> intended recipient, please contact the sender by reply email and destroy the
> original message and any copies of the message as well as any attachments to
> the original message.
>
This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.
Re: Web Interface Not Working
Posted by Todd Lipcon <to...@cloudera.com>.
Hi Mark,
Very strange. I've only seen this behavior when I've removed the hadoop jars
while the daemon was still running. Can you verify that the jars are still
in place where you expect them and haven't been moved, etc?
-Todd
On Tue, Dec 1, 2009 at 11:12 AM, Mark Vigeant
<ma...@riskmetrics.com>wrote:
> Hey Todd,
>
> Yes, jobs are working. In fact, I have hbase running on top of it just fine
> right now, so I'm sort of confused. Jps shows the the namenode and
> jobtracker are running, and here is what curl http://127.0.0.1:50030/print out:
> <HTML><HEAD><TITLE>Directory: /</TITLE></HEAD><BODY>
> <H1>Directory: /</H1><TABLE BORDER=0><TR><TD><A
> HREF="/WEB-INF">WEB-INF/ </TD><TD ALIGN=right>4096
> bytes </TD><TD>Nov 30, 2009 $:58:56 PM</TD></TR>
> </TABLE>
> </BODY></HTML>
>
> For the record, when I said the UI wasn't working, I meant I saw
> "directory..." etc, as you would expect from looking at the HTML above.
> Thanks!
>
> -Mark
>
> -----Original Message-----
> From: Todd Lipcon [mailto:todd@cloudera.com]
> Sent: Tuesday, December 01, 2009 1:45 PM
> To: common-user@hadoop.apache.org
> Subject: Re: Web Interface Not Working
>
> Hi Mark,
>
> Both web UIs went down but jobs can still be submitted, etc? This seems
> like
> a problem external to Hadoop, since the JT (port 50030) and NN (port 50070)
> are entirely separate processes. If they both became inaccessible at the
> same time, perhaps a firewall rule was added that inadvertently blocked
> them?
>
> If you ssh into the machine and run "jps", can you see the NN and JT
> running? From that machine can you 'curl http://127.0.0.1:50030/' ?
>
> -Todd
>
> On Tue, Dec 1, 2009 at 7:41 AM, Mark Vigeant
> <ma...@riskmetrics.com>wrote:
>
> > Hello-
> >
> > I have a namenode/JT with 3 slaves running cloudera's 0.20 release.
> > Everything was going fine until yesterday when the web interface randomly
> > went down (the http://hostname:50070 and http://hostname:50030). To my
> > knowledge everything else is fine, but I wanted to know if anyone else
> has
> > experienced a similar problem / what can I do to fix this?
> >
> > Thanks!
> >
> > Mark Vigeant
> > RiskMetrics Group, Inc.
> >
> >
> > This email message and any attachments are for the sole use of the
> intended
> > recipients and may contain proprietary and/or confidential information
> which
> > may be privileged or otherwise protected from disclosure. Any
> unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not an
> > intended recipient, please contact the sender by reply email and destroy
> the
> > original message and any copies of the message as well as any attachments
> to
> > the original message.
> >
>
> This email message and any attachments are for the sole use of the intended
> recipients and may contain proprietary and/or confidential information which
> may be privileged or otherwise protected from disclosure. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not an
> intended recipient, please contact the sender by reply email and destroy the
> original message and any copies of the message as well as any attachments to
> the original message.
>
RE: Web Interface Not Working
Posted by Mark Vigeant <ma...@riskmetrics.com>.
Hey Todd,
Yes, jobs are working. In fact, I have hbase running on top of it just fine right now, so I'm sort of confused. Jps shows the the namenode and jobtracker are running, and here is what curl http://127.0.0.1:50030/ print out:
<HTML><HEAD><TITLE>Directory: /</TITLE></HEAD><BODY>
<H1>Directory: /</H1><TABLE BORDER=0><TR><TD><A HREF="/WEB-INF">WEB-INF/ </TD><TD ALIGN=right>4096 bytes </TD><TD>Nov 30, 2009 $:58:56 PM</TD></TR>
</TABLE>
</BODY></HTML>
For the record, when I said the UI wasn't working, I meant I saw "directory..." etc, as you would expect from looking at the HTML above. Thanks!
-Mark
-----Original Message-----
From: Todd Lipcon [mailto:todd@cloudera.com]
Sent: Tuesday, December 01, 2009 1:45 PM
To: common-user@hadoop.apache.org
Subject: Re: Web Interface Not Working
Hi Mark,
Both web UIs went down but jobs can still be submitted, etc? This seems like
a problem external to Hadoop, since the JT (port 50030) and NN (port 50070)
are entirely separate processes. If they both became inaccessible at the
same time, perhaps a firewall rule was added that inadvertently blocked
them?
If you ssh into the machine and run "jps", can you see the NN and JT
running? From that machine can you 'curl http://127.0.0.1:50030/' ?
-Todd
On Tue, Dec 1, 2009 at 7:41 AM, Mark Vigeant
<ma...@riskmetrics.com>wrote:
> Hello-
>
> I have a namenode/JT with 3 slaves running cloudera's 0.20 release.
> Everything was going fine until yesterday when the web interface randomly
> went down (the http://hostname:50070 and http://hostname:50030). To my
> knowledge everything else is fine, but I wanted to know if anyone else has
> experienced a similar problem / what can I do to fix this?
>
> Thanks!
>
> Mark Vigeant
> RiskMetrics Group, Inc.
>
>
> This email message and any attachments are for the sole use of the intended
> recipients and may contain proprietary and/or confidential information which
> may be privileged or otherwise protected from disclosure. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not an
> intended recipient, please contact the sender by reply email and destroy the
> original message and any copies of the message as well as any attachments to
> the original message.
>
This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.
Re: Web Interface Not Working
Posted by Todd Lipcon <to...@cloudera.com>.
Hi Mark,
Both web UIs went down but jobs can still be submitted, etc? This seems like
a problem external to Hadoop, since the JT (port 50030) and NN (port 50070)
are entirely separate processes. If they both became inaccessible at the
same time, perhaps a firewall rule was added that inadvertently blocked
them?
If you ssh into the machine and run "jps", can you see the NN and JT
running? From that machine can you 'curl http://127.0.0.1:50030/' ?
-Todd
On Tue, Dec 1, 2009 at 7:41 AM, Mark Vigeant
<ma...@riskmetrics.com>wrote:
> Hello-
>
> I have a namenode/JT with 3 slaves running cloudera's 0.20 release.
> Everything was going fine until yesterday when the web interface randomly
> went down (the http://hostname:50070 and http://hostname:50030). To my
> knowledge everything else is fine, but I wanted to know if anyone else has
> experienced a similar problem / what can I do to fix this?
>
> Thanks!
>
> Mark Vigeant
> RiskMetrics Group, Inc.
>
>
> This email message and any attachments are for the sole use of the intended
> recipients and may contain proprietary and/or confidential information which
> may be privileged or otherwise protected from disclosure. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not an
> intended recipient, please contact the sender by reply email and destroy the
> original message and any copies of the message as well as any attachments to
> the original message.
>