Hello, I guess you get several helpful hints here, but they go slightly different ways to get results. I guess you have to pick just one way and go along with it. The most natural approach for me with my knowledge seems to be the one Kyle suggests.
So far, you try to set up the whole thing at once, including postgres, tomcat, apache and mod_jk. For now, just forget about apache. If you can see your pages under tomcat directly you can try to integrate with apache via mod_jk later on. You can even forget about postgres for now, because you will see a dspace error message in your browser if dspace cant connect to the database. But that is certainly not your problem because you have proven that it works by running fresh_install successfully. You listed your version numbers in the first post and I wondered how you had been able to build dspace when you had only a JRE installed but as it worked you should have a javac in place. You might check this. If my understanding ist fine, the tomcat JSP container uses this javac to compile JSPs at runtime. This is, it wont work properly without a JDK installed. Prove me wrong. Did you compile dspace on the same machine? You probably have ant installed in a recent version? You can see the tomcat homepage which means that tomcat is running. It also recognizes the .war files and unpacks them which means that automatic deployment is working too. Surely, there is no permissions problem at this point. tomcat only reads the .war files, so they can be owned by anybody as long as everybody may read them. While tomcat unpacks these files, it has to be allowed to write to the /webapps dir which it obviously is. It is probably allowed to write to /work which it needs to run any .jsp. You might want to check this. The files tomcat writes to /webapps/dspace are then owned by tomcat which is fine. The only thing not discussed so far is the dspace install directory. You should check whether tomcat is able to write to /dspace-install/assetstore or /dspace-install/history and so on. DSpace is not running which means that you dont have a dspace.log which in turn means that you dont have detailed error messages. If I am wrong with my JRE vs. JDK idea, then the only thing where you can find a fault is in your dspace configuration files. The web.xml does not get changed during a default install, so I would just replace it with the default version if you edited that. Then check the first third of your dspace.cfg file which contains all the important path, database and email settings. The rest of this file deals with special datastores, different thumbnail display and cosmetic stuff. The last thing to look at besides dspace.cfg is the log4j configuration file for dspace. Check whether it makes sense to you. I hope you can find the culprit. Bye, Christian Am 16.11.2007 um 02:59 schrieb Drrty Byl: > Thanks Graham. Here is one loop from repetitive output in > /var/log/tomcat5/catalina.out : > > INFO: HTMLManager: start: Starting web application at '/dspace' > 15-Nov-07 7:49:19 PM org.apache.catalina.core.StandardContext start > SEVERE: Error in dependencyCheck > 15-Nov-07 7:49:20 PM org.apache.catalina.core.StandardContext start > SEVERE: Error getConfigured > 15-Nov-07 7:49:20 PM org.apache.catalina.core.StandardContext start > SEVERE: Context [/dspace] startup failed due to previous errors > 15-Nov-07 7:49:20 PM org.apache.catalina.core.StandardContext stop > INFO: Container > org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/ > dspace] > has not been started > 15-Nov-07 7:49:21 PM org.apache.catalina.core.ApplicationContext log > INFO: HTMLManager: list: Listing contexts for virtual host 'localhost' > > Nothing in my /usr/share/tomcat5/conf/web.xml points to > /dspace/dspace.cfg -- should it? It almost looks like part of Tomcat > isn't loading? By the way, /tomcat5/webapps/dspace/ and > /tomcat5/webapps/dspace-oai/ directories do contain installation > files. I am not running SELinux, nor am I blocking any services or > port 8080. Could this be caused by a permissions-related issue? > Other Tomcat-related applications (such as jsp examples) are working. > > On Nov 15, 2007 4:10 PM, Graham Triggs <[EMAIL PROTECTED]> > wrote: >> Then the application is falling over during startup. The two most >> obvious causes: >> >> 1) The configuration item in web.xml that points to dspace.cfg >> does not >> match the location of the file. >> >> 2) The initialisation servlet is throwing an exception due to running >> under a security manager, and therefore it can't read the system >> properties. >> >> Either way, you need to check the Tomcat log files to see what error >> message is being written. >> >> G >> >> >> Drrty Byl wrote: >>> Yes, I have the manager application installed. I logged in as you >>> suggested -- low and behold neither the /dspace nor /dspace-oai >>> applications are running. When I click either of these to start >>> them, >>> the page refreshes and they do not start. Also please note that I >>> have uncommented the code which adds the port connection for the >>> mod_jk module in the tomcat configuration file ( <Connector >>> port="8082" maxThreads="150" minSpareThreads="25" >>> maxSpareThreads="75" >>> enableLookups="false" acceptCount="100" connectionTimeout="20000" >>> proxyPort="80" disableUploadTimeout="true" /> ) as instructed in >>> the >>> mod_jk connector install directions. Should there be some kind of >>> DSpace entry in server.xml that could be missing? Also, should >>> there >>> be a line in the $dspace.source/config/dspace.cfg file that >>> points to >>> the Tomcat server.xml upon compilation? There is nothing in the >>> Display Name field in the Tomcat manager application for DSpace. >>> Thanks, Billy >>> >>> >>> On Nov 15, 2007 12:20 PM, Graham Triggs >>> <[EMAIL PROTECTED]> wrote: >>> >>>> Do you have the manager application installed on Tomcat? >>>> (http://localhost:8080/manager/html) >>>> >>>> If so, what does it say about the status of the DSpace application? >>>> >>>> Have you checked the Tomcat log files? >>>> >>>> Is Tomcat running under a security manager? (I'm not sure how >>>> this is / >>>> would be configured under Fedora). If it is, the configuration >>>> manager >>>> probably won't get loaded, and the application will fail to >>>> initialise >>>> correctly. >>>> >>>> G >>>> >>>> >>>> Drrty Byl wrote: >>>> >>>>> Hello, I have been trying to install DSpace on my Fedora Core 5 >>>>> server >>>>> to use in a school project for the past several days. I am >>>>> able to >>>>> successfully build and install the package, but still cannot >>>>> access >>>>> the web interface. Here are the specifications for my project >>>>> along >>>>> with the steps I have tried to get it working: >>>>> >>>>> Fedora Core 5 (kernel 2.6.15-1.2054_FC5, i386) >>>>> DSpace version 1.4.2 >>>>> dspace.dir = /dspace dspace.url = http://localhost:8080/dspace >>>>> dspace.hostname = localhost >>>>> Java version "1.6.0_03" Java(TM) SE Runtime Environment (build >>>>> 1.6.0_03-b05) >>>>> Tomcat 5 (installed from Redhat Package Manager/yum interface) >>>>> Apache 2.2 (installed from Redhat Package Manager/yum interface) >>>>> PostgreSQL 8.1.9 >>>>> >>>>> 1 - Regular sequence of Postgres database creation is >>>>> successful, "ant >>>>> fresh_install" build is successful, software installed at "/ >>>>> dspace". >>>>> 2 - Tomcat and Apache are restarted >>>>> 3 - visiting http://localhost:8080 with Firefox displays Apache >>>>> Test Page >>>>> 4 - visiting http://localhost:8080/dspace results in a 404 >>>>> error: Not Found >>>>> 5 - visiting http://localhost:8080/dspace/ results in a 503 error: >>>>> Service Temporarily Unavailable >>>>> >>>>> I am positive that both Tomcat and Apache are running; port >>>>> 8080 is >>>>> NOT firewalled. The next step I tried was installing the mod_jk >>>>> connector using the directions at: >>>>> http://wiki.dspace.org/index.php/ModJk . This did not resolve the >>>>> problem. Should "ProxyRequests On" and "NameVirtualHost *:80" be >>>>> uncommented in Apache httpd.conf? Also, do I need to define a < >>>>> location > in this file? Does anyone have a working Apache >>>>> configuration file with changes made in respect to DSpace >>>>> installation? I get the impression this might somehow be >>>>> related to >>>>> the problem. It looks as though Tomcat, although running, is not >>>>> serving DSpace. Any help to get this functioning is greatly >>>>> appreciated! Billy >>>>> >>>>> ------------------------------------------------------------------ >>>>> ------- >>>>> >>>>> This SF.net email is sponsored by: Splunk Inc. >>>>> Still grepping through log files to find problems? Stop. >>>>> Now Search log events and configuration files using AJAX and a >>>>> browser. >>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>>>> _______________________________________________ >>>>> DSpace-tech mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech >>>>> >>>>> >>>> >> >> > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
