[server-admins] bug tracker is dead

[DM Smith]

It happens if at startup the file exists.  After successful startup it creates the file. So that leads me to believe that the process ended w/o deleting the file.

Maybe add the conditional delete on reboot?
-- DM 

Sent from my phone

On Sep 17, 2010, at 8:33 AM, "Troy A. Griffitts" <scribe at crosswire.org> wrote:

> Hey guys, I removed the file yesterday when the problem was reported
> (SSH on my phone is cool).  Do we know why this happens?  What can we do
> to prevent this or automate a fix in the future?
> 
> Troy
> 
> 
> On 09/16/2010 07:03 PM, DM Smith wrote:
>> On 09/16/2010 01:16 PM, Karl Kleinpaste wrote:
>>> http://crosswire.org/bugs/JiraLockedError
>>> 
>>> _______________________________________________
>>> server-admins mailing list
>>> server-admins at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/server-admins
>> I went to fix the problem (i.e. rm ~jira/jira-home/.jira-home.lock and
>> restart jira in tomcat) but couldn't as everything is owned by tomcat
>> and not jira. Somehow the permissions flipped.
>> 
>> Troy, can you either give me permissions again or do it for me.
>> 
>> Thanks,
>>    DM
>> 
>> _______________________________________________
>> server-admins mailing list
>> server-admins at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/server-admins
> 
> 
> _______________________________________________
> server-admins mailing list
> server-admins at crosswire.org
> http://www.crosswire.org/mailman/listinfo/server-admins