Re: [Boost-testing] Reporting down, Repo access problems

Subject: Re: [Boost-testing] Reporting down, Repo access problems
From: DongInn Kim (dikim_at_[hidden])
Date: 2011-04-03 10:49:05

Hi Noel,

I found that there is a Sandia IP address(198.102.153.2) in my blacklist. I am wondering if this is the cause. I just removed the IP address from the blacklist.
Can you please try it again to see what happens?
The script is a little bit changed to not block any IPs from "sandia.gov" and "ornl.gov". Are there any other organization to put into this kind of list?

Regards,

On 4/3/11 3:39 AM, Belcourt, K. Noel wrote:
> Hi Steven,
> 
> On Apr 1, 2011, at 11:00 AM, Steven Watanabe wrote:
> 
>> On 04/01/2011 09: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
>>> (http://svn.boost.org)
>>>
>>
>> What is the svn command that triggers this?
>> You shouldn't need a password for http access.
> 
> Hi Steven,
> 
> I apologize for the late response.  Here's the command I issued from
> inside a cron script:
> 
>     svn co http://svn.boost.org/svn/boost/trunk
> 
> Due to internal changes, it seems that I'm no longer able to run the
> above command from a (non-interactive) cron script (worked fine until
> Thursday evening MST).  Sadly, it (http) also fails interactively so my
> options are limited.  I did try using https but, while that works
> interactively, it also fails from a cron script.  I'm hoping that Monday
> I can find a way to continue to contribute to Boost though right now I'm
> not optimistic.  I have not yet tried specifying my Boost
> (svn.boost.org) username and password as arguments to svn though I'll
> give that a try soon.
> 
> Thanks again for your help with the results reporting Steven, I really
> appreciate you stepping up on short notice.
> 
> -- Noel
> 
> 
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-testing

-- 
- DongInn