The fedora.log file does indeed provide greater insight. I traced this problem 
to the fedora/data/ directory being owned by root, I imagine caused by my 
running fedora-rebuild as root. I have now tried chown'ing the files to the 
fedora user and re-running the rebuild as the fedora user. That provided the 
same error, as did removing the lock files entirely and restarting tomcat. In 
both cases, I get the same FileNotFoundException/Permission Denied error.

Giving the data/ directory to tomcat results in broader-sounding errors, such 
as failure to recover the existing database.

****
FATAL 2009-09-21 10:32:23.006 [main] (Server) Module 
(fedora.server.resourceIndex.ResourceIndex) failed to initialize                
                                                        
fedora.server.errors.ModuleInitializationException: Error initializing RI       
                                                                                
                             
at 
fedora.server.resourceIndex.ResourceIndexModule.postInitModule(ResourceIndexModule.java:133)
    
<...>
Caused by: org.trippi.TrippiException: Couldn't create local database
<...>
Caused by: org.mulgara.query.QueryException: Couldn't create local database
<...>
Caused by: org.mulgara.server.SessionFactoryException: Could not instantiate 
TripleStoreImplementation from configuration. 
<...>
Caused by: java.lang.reflect.InvocationTargetException 
<...>
Caused by: org.mulgara.store.stringpool.StringPoolException: Couldn't construct 
string pool  
<...>
Caused by: java.io.FileNotFoundException: 
/home/fedora/operational/data/resourceIndex/xaStringPool/xa11.sp.lock 
(Permission denied) 

----- Original Message -----
From: "Chris Wilper" <[email protected]>
To: "Adam B. Ross" <[email protected]>
Cc: "fedora-commons-users" <[email protected]>
Sent: Wednesday, September 23, 2009 6:00:48 AM GMT -08:00 US/Canada Pacific
Subject: Re: [Fedora-commons-users] [500 Internal Server Error] The Fedora  
Server is Not Yet Running

Hi Adam,

Usually this error will be thrown if you try to hit any of Fedora's
APIs while Fedora is still in the process of starting up (it usually
takes a few seconds, rarely over 30).  But if you're getting this
error after waiting a minute or two, it looks like Fedora is having
trouble starting.  Check your $FEDORA_HOME/server/logs/fedora.log file
(near the end) for hints on why.

- Chris

On Tue, Sep 22, 2009 at 1:17 PM, Adam B. Ross <[email protected]> wrote:
> I am getting a 500 Error Code, as the Fedora Server is not coming back when I 
> restart Tomcat.
>
> I used the fedora-rebuild.sh script, and when done, I had a Fedora error 
> page. Troubleshooting efforts have revealed the Tomcat process hadn't quit 
> properly before I ran the script.
>
> I have proceeded to stop and start the fedora apps and clear them from the 
> Tomcat work/ directory for Tomcat to repopulate, both to no avail. Any 
> Tomcatters out there with the next step?
>
> ****************************************
> 500 Internal Server Error
> Error getting Fedora Server instance: The Fedora server is not yet running.
>
> javax.servlet.ServletException: Error getting Fedora Server instance: The 
> Fedora server is not yet running.
>        at 
> fedora.server.access.FieldSearchServlet.init(FieldSearchServlet.java:734)
>        at javax.servlet.GenericServlet.init(GenericServlet.java:211)
>        at 
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
>        at 
> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
>        at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
>        at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>        at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
>        at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>        at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>        at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>        at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>        at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>        at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>        at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>        at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>        at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>        at java.lang.Thread.run(Thread.java:619)
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Fedora-commons-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to