Hello,

I am having some frustrations in the setup of the reviewboard tool. It has 
to do with the login to an git
server over SSH. Within the web interface, I add the correct git path, 
however when outputting debug
information, I can see that it tries to login with root, a user I did not 
setup. I have installed version 1.6.6

***********************************
reviewboard.log
***********************************
2012-05-31 14:19:37,865 - DEBUG - Ciphers agreed: local=aes128-ctr, 
remote=aes128-ctr
2012-05-31 14:19:37,865 - DEBUG - 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
2012-05-31 14:19:37,931 - DEBUG - Switch to new keys ...
2012-05-31 14:19:37,973 - DEBUG - userauth is OK
2012-05-31 14:19:37,989 - INFO - Authentication (password) successful!
2012-05-31 14:19:38,089 - DEBUG - EOF in transport thread
2012-05-31 14:19:38,415 - ERROR - Git: Failed to find valid repository 
ssh://git.mynet/git/buildroot/buildroot.git: Error connecting to server: No 
authentication methods available (USERNAME=root PASSWORD=None)
fatal: The remote end hung up unexpectedly


NOTE: I have added the username and password output to rbssh.py so see what 
user the reviewboard uses (root is shown 2nd line from last).  The
entries I have entered in the web interface are not as above.

*************************************************
rbssh.log
*************************************************

05-31 14:28 root               DEBUG    ['/usr/bin/rbssh', 'git.mynet', 
"git-upload-pack '/git/buildroot/buildroot.git'"]
05-31 14:28 root               DEBUG    PID 4332
05-31 14:28 root               DEBUG    !!! git.ttnet, root, 
["git-upload-pack '/git/buildroot/buildroot.git'"]
05-31 14:28 paramiko.transport DEBUG    starting thread (client mode): 
0xa6e542cL
05-31 14:28 paramiko.transport INFO     Connected (version 2.0, client 
OpenSSH_4.3)
05-31 14:28 paramiko.transport DEBUG    kex 
algos:['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', 'arcfour', 'rijndael-...@lysator.liu.se'] 
server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] 
client mac:['hmac-md5', 'hmac-sha1', 'hmac-ripemd160', 
'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server 
mac:['hmac-md5', 'hmac-sha1', 'hmac-ripemd160', 
'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client 
compress:['none', 'z...@openssh.com'] server compress:['none', 
'z...@openssh.com'] client lang:[''] server lang:[''] kex follows?False
05-31 14:28 paramiko.transport DEBUG    Ciphers agreed: local=aes128-ctr, 
remote=aes128-ctr
05-31 14:28 paramiko.transport DEBUG    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
05-31 14:28 paramiko.transport DEBUG    Switch to new keys ...
05-31 14:28 root               ERROR    Error connecting to server: No 
authentication methods available  (USERNAME=root PASSWORD=None)
05-31 14:28 paramiko.transport DEBUG    EOF in transport thread



Why does it use root user? When I was using local files as the backend, it 
works fine...

Help??

BTW, really cool tool!


/Ryan

-- 
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