Looks like I broke the build. See https://issues.apache.org/jira/browse/CHUKWA-438 for details. I will have a fix when I am sober in the morning. Merry Christmas
Regards, Eric On 12/23/09 4:14 PM, "Joe Hammerman" <jhammer...@videoegg.com> wrote: > Eric - thanks again for you responsiveness. > > I navigated to the trunk and downloaded the latest build two days ago. I > cannot get the build to compile with ANT version 1.7.1. > > I have attached the console output - am I doing something wrong? > > Thanks in advance! > -----Original Message----- > From: Eric Yang [mailto:ey...@yahoo-inc.com] > Sent: Monday, December 21, 2009 11:15 PM > To: chukwa-user@hadoop.apache.org > Subject: Re: Chukwa build issue (should read Chukwa collector issue)[solved] > > This is a bug in HICC. When I converted from Tomcat to jetty in Chukwa 0.3, > there is a conflict between tag lib jsp engine and jetty's servlet > implementation. I rewrote the view manager for HICC in trunk, which uses > jersey and HDFS to store HICC views. Therefore, I recommend to upgrade to > trunk to get HICC dashboard builder working. > > Regards, > Eric > > > On 12/21/09 10:58 PM, "Joe Hammerman" <jhammer...@videoegg.com> wrote: > >> Gentlemen; first of all thanks for all of your help. >> >> The root cuase of the issue described here became evident after I used the >> jettyCollector.sh script per Ari's recommendation. The user I was launching >> the script as did not have write permissions to the hadoop cluster. >> >> Another issue that is not mentioned in the documentation (and to be fair, is >> not a fault of the Chukwa devlopment team in any way) is that the RPM'd >> version of ANT (1.6.5-2jpp.2 ) will fail when you issue the build command. >> >> I had to go get ANT 1.7.1 :) >> >> I am now encountering an issue with the HICC. I believe I followed the >> documentation (famous last words). When I direct my browser to the page, this >> is the output when I click Dasboard view: >> >> HTTP ERROR: 500 >> >> INTERNAL_SERVER_ERROR >> >> RequestURI=/hicc/jsp/workspace/manage_view.jsp >> Caused by: >> >> java.lang.NullPointerException >> at org.apache.hadoop.chukwa.hicc.Views.length(Views.java:130) >> at org.apache.hadoop.chukwa.hicc.ViewsTag.doTag(ViewsTag.java:35) >> at >> org.apache.jsp.jsp.workspace.manage_005fview_jsp._jspx_meth_my_findViews_0(or>> g >> .apache.jsp.jsp.workspace.manage_005fview_jsp:141) >> at >> org.apache.jsp.jsp.workspace.manage_005fview_jsp._jspService(org.apache.jsp.j>> s >> p.workspace.manage_005fview_jsp:114) >> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) >> at >> > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373> > > ) >> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470) >> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) >> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) >> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) >> 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:729) >> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >> at >> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColle>> c >> tion.java:206) >> at >> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114>> ) >> 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:505) >> at >> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:8>> 4 >> 3) >> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647) >> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) >> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) >> at >> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395) >> at >> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488) >> >> >> If I click Options -> Add Widget the page hangs on loading indefinitely. >> >> Is there any guidance anyone could provide here? >> >> Thanks so much! >> ________________________________________ >> From: Eric Yang [ey...@yahoo-inc.com] >> Sent: Thursday, December 17, 2009 7:12 PM >> To: chukwa-user@hadoop.apache.org >> Subject: Re: Chukwa build issue (should read Chukwa collector issue) >> >> You can try to send a kill -3 11135 and capture the output in >> chukwa-chukwizzle-jettyCollector.sh-hadoopm102.sacpa.videoegg.com.out >> >> It may provide more information for debug. Ditto what Ari said, use >> ./bin/start-collector.sh is better, tools/init.d only works as >> /etc/init.d/chukwa-collector, if you are building with "ant rpm" and >> installed the RPM package. I also notice the bash error that you should >> create var/tmp in /usr/local/chukwa to avoid the bash errors. >> >> Regards, >> Eric >> >> >> On 12/17/09 6:47 PM, "Joe Hammerman" <jhammer...@videoegg.com> wrote: >> >>> Eric, >>> >>> Thank you for the response! No I'm not running on an IPv6 network: >>> >>> [r...@hadoopm102.sacpa ~]# ifconfig -a >>> eth0 Link encap:Ethernet HWaddr 00:18:FE:71:E3:50 >>> inet addr:10.1.75.12 Bcast:10.1.95.255 Mask:255.255.224.0 >>> inet6 addr: fe80::218:feff:fe71:e350/64 Scope:Link >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:2217102 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:723565 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:641183690 (611.4 MiB) TX bytes:142622303 (136.0 MiB) >>> Interrupt:169 Memory:f8000000-f8012100 >>> >>> eth1 Link encap:Ethernet HWaddr 00:18:FE:71:E3:4E >>> BROADCAST MULTICAST MTU:1500 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >>> Interrupt:177 Memory:fa000000-fa012100 >>> >>> lo Link encap:Local Loopback >>> inet addr:127.0.0.1 Mask:255.0.0.0 >>> inet6 addr: ::1/128 Scope:Host >>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>> RX packets:8737 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:8737 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:20724963 (19.7 MiB) TX bytes:20724963 (19.7 MiB) >>> >>> sit0 Link encap:IPv6-in-IPv4 >>> NOARP MTU:1480 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >>> >>> I believe the capitalized 'C' was a result of Outlook's auto-capitalization. >>> The filename is not capitalized on the filesystem. >>> >>> -----Original Message----- >>> From: Eric Yang [mailto:ey...@yahoo-inc.com] >>> Sent: Thursday, December 17, 2009 6:42 PM >>> To: chukwa-user@hadoop.apache.org >>> Subject: Re: Chukwa build issue >>> >>> Hi Joe, >>> >>> Normally, it will say which port it runs on in the .out file. Like this: >>> >>> 2009-12-18 01:36:37.201::INFO: Logging to STDERR via >>> org.mortbay.log.StdErrLog >>> 2009-12-18 01:36:37.232::INFO: jetty-6.1.11 >>> 2009-12-18 01:36:37.528::INFO: Started selectchannelconnec...@0.0.0.0:8080 >>> started Chukwa http collector on port 8080 >>> >>> Are you running on IPv6 network? From your message, >>> chukwa-collector-conf.xml is spelled Chukwa-collector.conf.xml. Maybe it >>> was a typo. >>> >>> Regards, >>> Eric >>> >>> >>> On 12/17/09 6:11 PM, "Joe Hammerman" <jhammer...@videoegg.com> wrote: >>> >>>> Hello all, >>>> Trying to get a Chukwa 0.3.0 installation up and running >>>> for >>>> our Hadoop (Hadoop hadoop-0.20.1+152 from Cloudera) logs here. I¹ve read >>>> all >>>> the documentation, and the archives; I can¹t find anyone who seems to have >>>> encountered my error before. I followed the instructions here for Collector >>>> configuration: http://www.cs.berkeley.edu/~asrabkin/chukwa/admin.html. ant >>>> test runs without any test failures. >>>> >>>> The problem is that when I run >>>> tools/init.d/chukwa-collector >>>> I >>>> don¹t see the daemon listening on port 8080. Here is the output from the >>>> program launch: >>>> >>>> [r...@hadoopm102.sacpa init.d]# ./chukwa-collector start >>>> Starting chukwa-collector: /usr/local/chukwa/bin/chukwa-daemon.sh: line >>>> 110: >>>> /usr/local/chukwa/bin/../var/tmp/cron.200912180201: No such file or >>>> directory >>>> /usr/local/chukwa/bin/chukwa-daemon.sh: line 114: >>>> /usr/local/chukwa/bin/../var/tmp/cron.200912180201: No such file or >>>> directory >>>> /usr/local/chukwa/bin/chukwa-daemon.sh: line 121: >>>> /usr/local/chukwa/bin/../var/tmp/cron.200912180201: No such file or >>>> directory >>>> Registering watchdog..done >>>> starting jettyCollector.sh, logging to >>>> >> > /var/chukwa/log/chukwa-chukwizzle-jettyCollector.sh-hadoopm102.sacpa.videoegg>> > >> >> . >>>> com.out >>>> 2009-12-18 02:01:15.677::INFO: Logging to STDERR via >>>> org.mortbay.log.StdErrLog >>>> 2009-12-18 02:01:15.704::INFO: jetty-6.1.11 >>>> >>>> I have attached output showing that Chukwa is configured according to the >>>> documentation to file, in order to keep the thread clear of clutter. >>>> >>>> Does anyone have troubleshooting suggestions? >>>> >>>> Thanks in advance for any help! >>>> >>> >> >
