hadoop-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dhaval Shah <prince_mithi...@yahoo.co.in>
Subject Re: HDFS Web UI - Incorrect context
Date Fri, 23 Nov 2012 22:00:11 GMT
50070 on namenode and 50075 on datanodes.. Both give the same output

 From: "Kartashov, Andy" <Andy.Kartashov@mpac.ca>
To: "user@hadoop.apache.org" <user@hadoop.apache.org>; Dhaval Shah <prince_mithibai@yahoo.co.in>

Sent: Friday, 23 November 2012 4:50 PM
Subject: RE: HDFS Web UI - Incorrect context

This is on port 50075, correct?  
From:Dhaval Shah [mailto:prince_mithibai@yahoo.co.in] 
Sent: Friday, November 23, 2012 3:28 PM
To: user@hadoop.apache.org
Subject: HDFS Web UI - Incorrect context
Hello everyone.. I have a very weird issue at hand.. I am using CDH4.0.0 on one of my clusters
and it works perfectly fine.. Now I tried deploying the same packages to another cluster with
very similar configs (the only difference is machine names).. Hadoop does come up but the
HDFS UI seems to have an incorrect Tomcat context.. The only thing it shows up is
Directory: /
webapps/         4096 bytes 
            Nov 23, 2012 2:44:13 PM
When I click on webapps, it shows an option for hdfs and when I click hdfs, it takes me to
http://localhost:50070/webapps/hdfs/dfshealth.jsp which throws a 404.. Ideally /webapps/hdfs
should have been the root context and this works correctly on my other cluster.. Any pointers?
NOTICE: This e-mail message and any attachments are confidential, subject to copyright and
may be privileged. Any unauthorized use, copying or disclosure is prohibited. If you are not
the intended recipient, please delete and contact the sender immediately. Please consider
the environment before printing this e-mail. AVIS : le présent courriel et toute pièce jointe
qui l'accompagne sont confidentiels, protégés par le droit d'auteur et peuvent être couverts
par le secret professionnel. Toute utilisation, copie ou divulgation non autorisée est interdite.
Si vous n'êtes pas le destinataire prévu de ce courriel, supprimez-le et contactez immédiatement
l'expéditeur. Veuillez penser à l'environnement avant d'imprimer le présent courriel 
View raw message