Boost Testing :
Subject: Re: [Boost-testing] Reporting down, Repo access problems (fwd)
From: DongInn Kim (dikim_at_[hidden])
Date: 2011-04-01 14:09:28
My name is DongInn Kim, systems administrator in the OSL. I am taking care of the boost SVN server (wowbagger).
First of all, I am sorry that I have not announced you the changes I made recently before this kind of incident happens.
Actually, I wrote a script to automatically block offensive and malicious IP addresses from the SVN server last week and I have been watching the SVN activities of the server. It seems that it was doing right until Jeremiah forward this email and I notice this problem.
Apparently my script is not to manage this issue.
Do you have any specific IP addresses to avoid the blocking? My script is checking the svn log to see if there are any heavy talks (IP addresses) making more than 1900 transaction within recent 10000 traffics and if so, the IPs are blocked. Of course, I have the white list to unblock the valid IP addresses no matter how many transactions they make.
These are the changes that I made last week.
1. The apache configuration to optimize for the current traffic and load in wowbagger
2. Run the script to block the IPs in the blacklist (heavy talkers making more than 1900 transaction within 10000 traffics).
Since these changes, wowbagger seems to be much more usable than before.
The daily loadaverage of wowbagger has changed from 9~20 to 1~3.
Any suggestion to improve my script or wowbagger performance would be really appreciated.
Again, I am so sorry for any inconvenience that my script caused.
On 4/1/11 12:53 PM, Jeremiah Willcock wrote:
> ---------- Forwarded message ----------
> From: Rene Rivera <grafikrobot_at_[hidden]>
> To: Running Boost regression tests <boost-testing_at_[hidden]>
> Date: Fri, 01 Apr 2011 11:53:15 -0500
> Subject: Re: [Boost-testing] Reporting down, Repo access problems
> Reply-To: Running Boost regression tests <boost-testing_at_[hidden]>
> On 4/1/2011 11:48 AM, Belcourt, K. Noel wrote:
>> Sometime late yesterday trunk and release reporting died. From what I
>> can tell, there's been no changes here that would affect this. Have
>> there been any changes to servers, authentication, or repo access that
>> could have caused this? Reporting is dead until we figure this out.
>> -- Noel
>> [kbelco_at_wsblade171 reporting_release]$ cat build_release.log
>> Authentication realm: <http://svn.boost.org:80> Boost SVN repository
>> Subversion Access
>> Password for 'kbelco': Authentication realm: <http://svn.boost.org:80>
>> Boost SVN repository Subversion Access
>> Username: svn: PROPFIND request failed on '/svn/boost/trunk'
>> svn: PROPFIND of '/svn/boost/trunk': authorization failed
> I haven't done any server changes recently. Any one else?
-- - DongInn