Troubleshooting SVN indexing issues in FishEye and Crucible
This page lists the troubleshooting tips required to investigate some common SVN issues reported while indexing a repository in FishEye and Crucible.
Debugging slow indexing
Command line tool
- Monitor the size of your
<FISHEYE_INST>/var/cache/repository_namefolder on disk as this should be similar to your SVN repository on the server. If there is a huge size mismatch, that is usually an indication of incorrect SVN branch and tag mapping in FishEye.
- If you observe a large size mismatch, you can use the 'svnrules' command line tool to identify missing svn symbolic rules. The tool is shipped with the latest version of FishEye. For more information, see Verifying SVN symbolic rules.
This command may take a while as it runs svn log -v against the specified repository. It attempts to analyze all the copy operations in your repository and reports where it is most likely that there are missing svn symbolic rule definitions. Once the tool has finished, check the end of the generated <Repo Name>-svn-rules.log file – it contains a summary of the 10 most common folders for which symbolic rules may be missing.
You don't need to stop your current FishEye instance to perform this check. Please note that the tool may report false positives, as sometimes it is genuine activity in the repository to copy some files or folders within the trunk.
Analyzing debug logs
- With debug logging enabled, look for log entries beginning with
. These entries correspond to indexing related tasks currently running in the application and the Thread No. corresponds to which thread is being used to complete the task on that repository. Using the timestamp on the log, you can then investigate the last time that FishEye ran an incremental/initial index on a repository. and [
InitialPinger<Thread No.><Repository Name>]
- Debug logs will also report the exact commands being run on the repository at the time of initial and incremental indexing, for example:
In the above example, the "Starting process" and "Finished process" are the messages used to track the start and end of a command and how long did it take to complete - "took 33ms" in this case. This can be helpful in identifying some long running commands or if they do not complete at all when there are no corresponding "Finished process" log entries. You may then run the same commands via the command line directly on your server and compare the results.
- Logs will also lodge the time taken to index a particular repository, for example:
- With debug logging enabled, you can also look for the exact command that FishEye is failing at while indexing, for example:
In the above example, the command is "svn ls -r HEAD". You can run it via the command line to check the result returned from your SVN server.
Was this helpful?
Thanks for your feedback!