Apologies for a tardy reply Gav, in essence you are 100% correct. I'm about to update a wiki on our setup with the cleaned-up version of my install process with the fixes (including the Tomcat security - put the specific stuff in rather than the grant all if you can), and making sure that the correct ownership and permissions apply to all the components that you install.
Basically it was my gaff in the first place. I have spent most of my 20 odd years with *NIX doing stuff as Root, and when you issue the *ant* commands to build and deploy the wookie components and widgets - it all gets done as root, which means Tomcat can't work with the structure for sure in an Ubuntu / Debian base. Glad it worked for you first time round. I know it would be fine if I went ahead and did it now. Funnily enough I had no probs building Tomcat using apt-get. best wishes all Steve On 04/04/2010 00:32, Gav... wrote: > > >> -----Original Message----- >> From: Mark Johnson [mailto:[email protected]] >> Sent: Tuesday, 30 March 2010 2:10 AM >> To: [email protected] >> Subject: Re: Wookie 404 error >> >> On Monday 29 Mar 2010 15:20:04 Paul Sharples wrote: >> >>> Looking through the old posts, it sounds like it might be a problem >>> >> that >> >>> Steve & Sander also had to do with Tomcat's security manager. >>> >>> info here... >>> >>> http://markmail.org/message/iskmmnbvmzlm3yf5 >>> >>> ..and here.. >>> >>> http://incubator.apache.org/wookie/downloading-and-installing- >>> >> wookie.html >> >>> Paul >>> >> Aha! I had found that earlier but dismissed it as I couldn't find a >> .policy file >> where I expected it to be. >> >> For anyone reading this in search of answers, Ubuntu installs policy >> files to >> /etc/tomcat6/policy.d >> I removed the files that Ubuntu had created and replaced them with a >> single >> catalina.policy containing the "grant all" statement described by >> Sander. >> >> Thanks for your help! >> >> Mark >> > I've read this and the other threads regarding Wookie and Tomcat/mySQL > (especially on Ubuntu it seems) and was expecting the same deal when I come > to install it on the demo server. > > However, maybe just lucky me, but I experienced no such problems and had to > do none of this workaround stuff or alter any security settings. > > There may be a difference in the way I did some things which is why I am > mentioning it here. > > I created a user 'wookie' for installing and running the 'wookie' stuff. > I created a 'tomcat' user for installing and running 'tomcat' > I downloaded the tomcat .tar.gz and extracted it to > /usr/local/tomcat-$version > I pointed the webapp dir as appropriate to > /usr/local/tomcat-$version/webapps > I did chown -R tomcat:wookie on the webapps dir > I did chmod g+w on the webapps dir (giving the wookie user/group write > access) > > subversion/mysql/java etc and all other prereqs were installed with apt-get > but NOT Tomcat > > As you've experienced, Tomcat via apt-get is a mess and I don't recommend > using it, downloading the .tar.gz file from tomcat.apache.org/download.html > and extracting it is all the installation it needs. > > HTH > > Gav... > > > > -- Manchester Metropolitan University Learning Systems Manager LRT Manchester Metroopolitan University Before acting on this email or opening any attachments you should read the Manchester Metropolitan University's email disclaimer available on its website http://www.mmu.ac.uk/emaildisclaimer etc... and so on.
