All our git commits have 0 changed files according to fisheye/crucible
Asked by Kris:

We have a project in GIT and we're using Jira, confluence and fisheye/crucible to manage it. About half a year ago we moved from SVN to GIT and lost fisheye/crucible functionality but recently we've been wanting trying to get it back up and running on the GIT repository..

Our latest issue is a real mindblower to me though; it looks like all commits are seen, including committer, commit message etc. but all commits have 0 files and i can't find my way to a single line of sourcecode through fisheye/crucible.

Google hasn't been helpful, and our resident "expert" also has not been able to fix it over the course of about a week. Any help getting this issue resolved would be greatly appreciated.

**Additional information:**

* **Server software**: Ubuntu 8.04.4 LTS
* **Git version** on server: 1.5.4.3
* With debug log switched on, hercules log analyzer: points me to <https://jira.atlassian.com/browse/FE-4082> which doesn't help at all. I haven't found a way to see the actual log file with my own eyes though. debug log has been on for about 6 hours in which there have been quite a few commits.

**In the mean time:**

We've had an unexplained authentication issue (we're using gitolite) where it looks like the fisheye generated key changed. the backend was changed to mysql from something totally foreign to me that I don't recall the name of. And we're trying to still get actual work done, now reviewing work at colleagues desks pre-push.

Fisheye is still indexing 0 files per commit after reindexing the whole thing multiple times.

**Yet later:**

I've created another repository in fisheye and painstakingly configured new key, user, environment etc. in gitolite. The new fisheye repository (pointing to the same git repo) ends up looking exactly like the first. 0 files per commit.

Nothing has really changed.


Answers:
author: Nick
body: This is an odd one. It may be best to enable DEBUG logging as Jeff mentions in the comment, then re-index that repository and then raise a support request. Have a look through the DEBUG logs during indexing to see if there are any clues as to what could be up.

If you don't want to re-index the repository, simply add another repository in FishEye which points to the same git repository. This will also ensure you are starting from a clean slate (ie. no other configuration such as includes/excludes will be defined etc).

comments: author: Kris
body: debug logging has been enabled since Jeff's comment but i have not had any luck getting my hands on the actual file. I've let crucible reindex from the exixting clone and it's been busy for well over 24 hrs, still without any file or author but I do get to see a commit graph that at least looks up to date.


author: Jeff Thomas
body: I'm not sure if any of these questions will help, but it's worth a shot:

* Which operating system is your Crucible server running on?
* What version of Git is installed on the server?
* Have you enabled debugging and looked at the logs for additional information? You can turn on debugging in Administration \> Global Settings \> Server Debug Logging


Tags: fisheye-crucible-administration