Thanks for the quick response! I'm not sure how I missed seeing that bug 
report, my Google-Fu must have been lacking yesterday.
 
Can I assume that 1.6.11 fixes the bug as well, or should I actually go 
back to 1.6.9?

On Monday, July 30, 2012 9:29:40 PM UTC-4, Christian Hammond wrote:

> Drop back down to 1.6.9. There's a bug, and I'll be releasing a patch 
> tonight.
>
> Christian
>
> -- 
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Mon, Jul 30, 2012 at 5:59 PM, Bill Frerking 
> <moonlitjour...@gmail.com>wrote:
>
>> I recently updated from 1.6.5 to 1.6.10 and since updating, can no longer 
>> connect to my repositories(that were functioning fine in 1.6.5).
>>  
>> SSH Keys are properly configured from the apache user on my ReviewBoard 
>> server to the rbsvn user on my repository server. From a command line as 
>> apache, I can do "svn info svn+ssh://rbsvn@sc/export/svn/repos/SSTS" and 
>> get a valid response. Within the python shell, I can get the same 
>> information using pysvn and Client.info2(). When I attempt to reconfigure a 
>> repository in the admin section, I get the following results:
>>  
>>  
>> 20:51:44DEBUG
>>
>> Logging to /opt/ReviewBoard/logs/reviewboard.log with a minimum level of 
>> DEBUG
>>
>> 20:51:44DEBUG 
>>
>> Log file for Review Board v1.6.10 (PID 20887)
>>
>> 20:51:45DEBUG
>>
>> SVNTool: Attempting ssh connection with host: sc, username: rbsvn
>>
>> 20:51:45DEBUG 
>>
>> starting thread (client mode): 0xb5f76eecL
>>
>> 20:51:46INFO
>>
>> Connected (version 2.0, client OpenSSH_5.8)
>>
>> 20:51:46DEBUG
>>
>> kex algos:['diffie-hellman-group-exchange-sha256', 
>> 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 
>> 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client 
>> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
>> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
>> 'aes192-cbc', 'aes256-cbc'] server encrypt:['aes128-ctr', 'aes192-ctr', 
>> 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 
>> 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour'] client 
>> mac:['hmac-md5', 'hmac-sha1' <%27hmac-sha1...@openssh.com%27>, 
>> 'hmac-ripemd160', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hmac-md5', 
>> 'hmac-sha1', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none'] server 
>> compress:['none'] client lang:[''] server lang:[''] kex follows?False
>>
>> 20:51:46DEBUG
>>
>> Ciphers agreed: local=aes128-ctr, remote=aes128-ctr
>>
>> 20:51:46DEBUG
>>
>> using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local 
>> aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; 
>> compression: local none, remote none
>>
>> 20:51:46DEBUG
>>
>> Switch to new keys ...
>>
>> 20:51:46DEBUG
>>
>> Trying SSH key e186f3e82d1b2098616d5c0806c0961b
>>
>> 20:51:46 DEBUG
>>
>> userauth is OK
>>
>> 20:51:47INFO
>>
>> Auth banner:
>> You are accessing a Private Information System (IS) that is provided for
>> authorized use only.
>>
>> By using this IS (which includes any device attached to this IS), you consent
>> to the following conditions. We routinely intercept and monitor 
>> communications
>> on this IS for purposes including, but not limited to, penetration testing,
>> COMSEC monitoring, network operations and defense, personnel misconduct, law
>> enforcement, and counterintelligence investigations. At any time, we may
>> inspect and seize data stored on this IS. Communications using, or data 
>> stored
>> on, this IS are not private, are subject to routine monitoring, interception,
>> and search, and may be disclosed or used for any authorized purpose. This IS
>> includes security measures (e.g., authentication and access controls) to
>> protect our interests -- not for your personal benefit or privacy.
>>
>>
>> 20:51:47INFO
>>
>> Authentication (publickey) successful!
>>
>> 20:51:47DEBUG
>>
>> EOF in transport thread
>>
>> 20:51:48 ERROR
>>
>> SVN: Failed to get repository information for 
>> svn+ssh://rbsvn@sc/export/svn/repos/SSTS: To better debug SSH connection 
>> problems, remove the -q option from 'ssh' in the [tunnels] section of your 
>> Subversion configuration file.
>> Network connection closed unexpectedly
>>
>>
>> I have multiple repositories that are all responding in the same fashion, 
>> and am not sure where to go with troubleshooting this further.
>>  
>> -- 
>> Want to help the Review Board project? Donate today at 
>> http://www.reviewboard.org/donate/
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> -~----------~----~----~----~------~----~------~--~---
>> To unsubscribe from this group, send email to 
>> reviewboard+unsubscr...@googlegroups.com
>> For more options, visit this group at 
>> http://groups.google.com/group/reviewboard?hl=en
>
>
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to