Hello,

I'm trying to figure out why my ssh-pushes from the same machine aren't 
working.

I found the problem in the gitorious_auth.log and tried to debug it but I 
can't figure out how to fix it.

F, [2011-07-05 22:42:49#2629] FATAL -- : Net::HTTPBadResponse wrong status 
line: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">": 
/usr/local/lib/ruby/1.8/net/http.rb:2030:in `read_status_line'
  /usr/local/lib/ruby/1.8/net/http.rb:2017:in `read_new'
  /usr/local/lib/ruby/1.8/net/http.rb:1051:in `request'
  /usr/local/lib/ruby/1.8/net/http.rb:772:in `get'
  /var/www/gitorious/script/../lib/gitorious/ssh/client.rb:84:in 
`configuration'
  /var/www/gitorious/script/../lib/gitorious/ssh/client.rb:58:in `real_path'
  /var/www/gitorious/script/../lib/gitorious/ssh/client.rb:72:in 
`to_git_shell_argument'
  /usr/local/bin/gitorious:63

These lines causing the get-request 
in /var/www/gitorious/lib/gitorious/ssh/client.rb (def configuration):

        if @configuration.empty?
          query_url = "/#{@project_name}/#{@repository_name}/config"
          #$stderr.puts "Querying #{query_url}" if $DEBUG
          resp = connection.get(query_url)
          #$stderr.puts resp
          parse_configuration(resp.body)
        end

Trying to access the repo-config via wget including headers succeeded like:

### HEADERS START ###
HTTP/1.1 200 OK
Date: Tue, 05 Jul 2011 20:55:46 GMT
Server: Apache/2.2.16 (Debian)
X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.7
ETag: "967f22334213f237608607a1be3b21e8"
X-Runtime: 2
Cache-Control: public, max-age=600
Content-Length: 83
Status: 200
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/x-yaml; charset=utf-8
### HEADERS END ###
real_path:243/ba4/bf5e64f2231efd34690f0fbe4c5552dcd1.git
force_pushing_denied:false

So everything SEEMS to work but it doesn't. Any ideas how to fix this thing?

Thank you,
Stefan

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Reply via email to