Ok. Perhaps this is not the place, but I'm a little tripped up due to my lack of java experience. These new RPM builds from 4.0 also seem to have changed the logging, the server is going to /var/log/cloud/management/catalina.out instead of the old /var/log/cloud/management/management-server.log, and I haven't yet found where the agent is logging, even though the file /etc/cloud/agent/log4j-cloud.xml hasn't changed.
log4j:WARN No appenders could be found for logger (com.cloud.utils.component.ComponentLocator). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. log4j:ERROR Could not create an Appender. Reported error follows. java.lang.ClassNotFoundException: org.apache.log4j.rolling.RollingFileAppender On Thu, Sep 6, 2012 at 11:53 AM, Edison Su <edison...@citrix.com> wrote: > Yeah, need to install jakarta-taglibs-standard, I think I added it in the rpm > dependence, but seems not got installed automatically. > >> -----Original Message----- >> From: Marcus Sorensen [mailto:shadow...@gmail.com] >> Sent: Thursday, September 06, 2012 10:31 AM >> To: cloudstack-dev@incubator.apache.org >> Cc: Edison Su >> Subject: Re: RPM build is fixed, sort of... >> >> nevermind, just bitten by the stuff not being included anymore and had >> to install a few more dependencies. >> >> On Thu, Sep 6, 2012 at 11:27 AM, Marcus Sorensen <shadow...@gmail.com> >> wrote: >> > So, the RPMs build fine for me with the current 4.0 tree, but >> > installing them and trying to use them, it seems something was missed, >> > getting a 500 on the client: >> > >> > The absolute uri: http://java.sun.com/jsp/jstl/core cannot be >> resolved >> > in either web.xml or the jar files deployed with this application >> > >> > On Thu, Sep 6, 2012 at 9:40 AM, David Nalley <da...@gnsa.us> wrote: >> >> On Thu, Sep 6, 2012 at 5:47 AM, Rohit Yadav <rohit.ya...@citrix.com> >> wrote: >> >>> >> >>> On 06-Sep-2012, at 3:06 PM, Hugo Trippaers >> <htrippa...@schubergphilis.com> wrote: >> >>> >> >>>> Hey Edison, >> >>>> >> >>>> That should be easy to do once the build is "mavenized". I'm >> starting to seriously dislike waf already, so would be happy to see it >> go. >> >>> >> >>> What technical difficulties are you facing with waf? Let's not take >> decision based on one's preference. >> >>> >> >>> If we decide to get rid of war, then I can try to write cmake based >> packaging scripts that package debs and rpm. >> >>> (I package/release debs/rpm for VideoLAN's VLMC, >> https://github.com/bhaisaab/cmakeqt) >> >>> >> >>> Rohit >> >>> >> >> >> >> >> >> So I personally don't see why maven + rpmbuild or maven + dpkg >> >> couldn't be enough for packaging. >> >> Don't we really want people to be able to install CloudStack using >> >> maven? Certainly from a developer standpoint I think that is an end >> >> goal. Aside from the fact that it exists, I don't see anything that >> >> waf currently does that maven can't do. >> >> >> >> --David
