|
well, it happened twice.
Haven't tried reinstalling from scratch since. It sort of looks as if it could have been a permissions problem, except that jira did generate the other two directories ok (issues and comments). Here's the log that was generated. When the next update comes out I'll let you know if it happens again. log follows : Hi Joshua,
In logs you have provided this line appears: WARNING: Directory /Users/jira/Database/Index/plugins/atlassian-subversion-revisions does not exist - perhaps it was delete$ Was this line cut off in you installation? The line should be WARNING: Directory /Users/jira/Database/Index/plugins/atlassian-subversion-revisions does not exist - perhaps it was deleted? Creating.... Also does the directory /Users/jira/Database/Index/plugins have any read/write restrictions on it? Thanks, no idea why the lines are truncated like that - probably because i just copied and pasted from the scrollback buffer in my terminal - in reality the whole line is there in the log, it's not actually truncated.
The App server should have read and write permission for that directory. In fact, you can see from the logs that it did successfully manage to create the /Users/jira/Database/Index/issues and /Users/jira/Database/Index/Comments directories. I suppose it's possible there was an odd permissions problem somewhere - my machine is set up with a "jira" user and the database is written to this users' home directories. The appserver doesn't run as this user - however it does have permission to write to the relevant directories. It's difficult to imagine what the permissions problem could be that would allow it to successfully create the other two directories in the same place though. Thanks for the update. We will try to reproduce it and fix in JIRA 3.2.2. If you hit this problem again and have more clues please let us know.
Thanks again, Hi Joshua,
We have been able to reproduce this issue. The problem is that the plugin tries to initialize itself before you have initialized Jira and told it where to place the index directory. In my case, it created a null/plugins/atlassian-subversion-revisions directory from where I launched the application because it had permission to do so. I am thinking that for you, the user whom the app server is running as does not have permission to create the directory there. We will be looking at this so that we can resolve it. In the mean time, the work-around of restarting the app server once Jira has been properly configured should work. The plugin has been changed (and the way Jira handles its scheduler a bit) so that the plugin will now handle the index creation, initialization, and recovery from deletion is a more robust fashion. The changes require that the plugin runs against jira 3.3 and will be released when 3.3 is release.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
on first install subversion plugin can't create it's index directory
Unfortunately we have troubles reproducing this behaviour. can you reproduce it reliably? If so could you please provide a set of steps that you go through?
Thanks,
Anton