I stopped Tomcat, deleted the Magnolia dirs, rebooted the system, and am still unable to open Magnolia. Here some of the contents from catalina.out. I did not see any errors that suggested memory problems to me.
Created MBeanServer with ID: [UID: 291272,1144950097847,-32768]:fedora1.pryermachine.com:1 13-Apr-06 1:41:47 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre/lib/i386 13-Apr-06 1:41:47 PM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 13-Apr-06 1:41:47 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 7044 ms 13-Apr-06 1:41:48 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina 13-Apr-06 1:41:48 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.15 13-Apr-06 1:41:49 PM org.apache.catalina.core.StandardHost start INFO: XML validation disabled 13-Apr-06 1:41:56 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive magnoliaPublic.war Initializing Log4J Setting the magnolia root system property: [magnolia.public.root] to [/usr/share/tomcat5/webapps/magnoliaPublic] Initializing Log4J from [WEB-INF/config/default/log4j.xml] log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /usr/share/tomcat5/webapps/magnoliaPubliclogs/magnolia-activation.log (No such file or directory) . . . ERROR info.magnolia.cms.beans.config.ContentRepository ContentRepository.java(loadRepositories :275) 13.04.2006 13:43:32 System : Failed to load JCR "userroles" Configuration file syntax error.: Premature end of file. info.magnolia.repository.RepositoryNotInitializedException: Configuration file syntax error.: Premature end of file.: Configuration file syntax error.: Premature end of file.: Premature end of file. at info.magnolia.jackrabbit.ProviderImpl.init (ProviderImpl.java:118) at info.magnolia.cms.beans.config.ContentRepository.loadRepository (ContentRepository.java:292) at info.magnolia.cms.beans.config.ContentRepository.loadRepositories (ContentRepository.java:274) at info.magnolia.cms.beans.config.ContentRepository.init (ContentRepository.java:176) at info.magnolia.cms.beans.config.ConfigLoader.load (ConfigLoader.java:106) at info.magnolia.cms.beans.config.ConfigLoader.<init> (ConfigLoader.java:90) . . . INFO info.magnolia.cms.beans.config.Bootstrapper Bootstrapper.java(bootstrapRepositories :77) 13.04.2006 13:43:33 Trying to initialize repositories from [/usr/share/tomcat5/webapps/magnoliaAuthor/WEB-INF/bootstrap] INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(load :135) 13.04.2006 13:43:34 Init virtualMap INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(load :137) 13.04.2006 13:43:35 Init i18n INFO info.magnolia.cms.i18n.Messages MessagesManager.java(load :130) 13.04.2006 13:43:36 Config : loading i18n configuration - i18n FATAL info.magnolia.cms.servlets.Initializer Initializer.java(contextInitialized :116) 13.04.2006 13:43:36 java.lang.NullPointerException at info.magnolia.cms.i18n.MessagesManager.load (MessagesManager.java:130) at info.magnolia.cms.i18n.MessagesManager.init (MessagesManager.java:117) at info.magnolia.cms.beans.config.ConfigLoader.load (ConfigLoader.java:138) at info.magnolia.cms.beans.config.ConfigLoader.<init> (ConfigLoader.java:90) at info.magnolia.cms.servlets.Initializer.contextInitialized (Initializer.java:111) at org.apache.catalina.core.StandardContext.listenerStart (catalina.jar.so) . . . -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Thursday, April 13, 2006 12:05 PM To: [email protected] Subject: Re: [magnolia-user] Problem installing Magnolia on Fedora Core 5 [VASCL:A103A5C1BEB] Magnolia is running, but that does not mean that the repositories are working. The first time you deploy magnolia it will try to initialize the repositories. If this fails on the first attempt (because of too little memory allocation), you probably need to clean out the exploded magnolia-dirs, in other words undeploy magnoliaPublic and magnoliaAuthor. Now, with the JAVA_OPTS set to increased memory, try deploying the wars again. Also, search your logs for anything related to 'memory' to see if this was the cause. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
