I am currently running Fisheye 3.3.1 to use for our subversion repositories. Just as a visual GUI for the most part. The issue we ran into is that fisheye is writing to the apache log and it created a HUGE file and brought down our subversion server. How can I have fisheye not write to the apache log on the subversion server?
Can you please give more information - few examples of the messages logged in the apache logs perhaps, are those access logs or rather error logs? Also, what is the oldest and newest message in the log, do you rotate the logs, is FishEye the only server hitting that subversion repositories?
FishEye indeed needs to run several commands to index the repository so with extensive trace logging it can perhaps cause your apache log file to grow quickly. But it should be possible to revisit the logging configuration on the apache side to manage this.
How can I have fisheye not write to the apache log on the subversion server?
One way to achieve this, and is also a recommendation to improve performance, is to simply use svnsync to synchronise your svn repository to the same machine as FishEye is running on, and then use the file:/// or svn:// protocols instead of http://. This will bypass apache altogether.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs