Fisheye Writing to subVersion Apache Logs - Causing Subversion space error

[Bryan Trummer - ReleaseTEAM]

Hi,

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?

[Piotr Swiecicki · Accepted solution]

Hi Bryan,

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.

Kind regards,
Piotr

[Bryan Trummer - ReleaseTEAM]

Thanks for the answer. This makes sense I will see what we can do. Another issue I was trying to have 3 repositories update at the same time and it was erroring out as well.

[Nick]

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.