Doug,

Did you ever get any replies to this?
Just wondering since I am running into the same issue... Installed clean 
CentOS v6.3 and from there installed Gitorious.
Initially the git-daemon starts on port 9400 (netstat shows the process) 
and I can use "git clone...." from my desktop.

However after running yum to update some packages and then a reboot. The 
git-daemon never comes back up
and while everything else is running just fine, I can't use the git clone 
command from my desktop anymore.
I also see the same messages in the proxy.log1 file and I'm at a loss on 
how to fix it..

Jeroen



On Monday, October 29, 2012 8:24:22 PM UTC-4, Doug Crawford wrote:
>
> I just installed gitorious on a fresh centos 6.3 vm using the new 
> installer at getgitorious.org.  I migrated a slightly older database and 
> tarball of repositories.  I ran the db:migrate script.  I can work with my 
> repositories using the ssh links but straight git always produces this 
> message in log/git-proxy.log1:
>
> Accepted 10.5.5.50:57610
> Looking up "/overo/packages-apps-maxtime.git"
> 10.5.5.50:57610 {:data=>"0063git-upload-pack 
> /6fe/67d/de9b43f1a18de0e75141a3f8d5f1791840.git\000host=gitorious.intelight.local\000",
>  
> :remote=>"localhost:9400"}
> Establishing new connection with localhost:9400
> Retrying connection with localhost:9400 (#1)
> Establishing new connection with localhost:9400
> Retrying connection with localhost:9400 (#2)
> Establishing new connection with localhost:9400
> Retrying connection with localhost:9400 (#3)
> Establishing new connection with localhost:9400
> ...
>
> I see something is trying to connect to localhost:9400.  But, when I run 
> netstat -a I see nothing is listening on 9400.  I do see something 
> listening on 9418 which is the default git port.  Searching for 9400 
> reveals git-proxymachine.rb:        :remote => "localhost:9400".  I am 
> assuming this is correct.  I am guessing that I should have a process 
> listening on 9400, but I don't see it?
>
>

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to