[Sugar-devel] GIT.sugarlabs.org changes?
georgejhunt at gmail.com
Wed Nov 3 06:22:14 EDT 2010
I tried the push from another ip address. Same result, so it's probably not
the blacklist problem.
The literature suggests that I should check for world or group writeability
on the path from root to .ssh/known_hosts on the server, and on the client
machine. I have double checked my client. Don't have shell access to server.
On Sun, Oct 31, 2010 at 10:30 AM, Aleksey Lim <alsroot at member.fsf.org>wrote:
> On Sat, Oct 30, 2010 at 07:58:00PM -0400, George Hunt wrote:
> > Hi Aleksey,
> > Thanks for the response.
> > The ssh step fails. Trying ssh -vvv gitorious at git.sugarlabs.orgindicates
> > that the negotiation proceeds in what looks to be a normal manner, until
> > point where the client determines that public key method is authorized,
> > client is offering my public key, and the next response is "connection
> > closed".
> > <snip>
> > debug1: Next authentication method: publickey
> > debug1: Offering public key:
> > debug3: send_pubkey_test
> > debug2: we sent a publickey packet, wait for reply
> > Connection closed by 22.214.171.124
> > </snip>
> "Connection closed" seems suspiciously. We had problem w/ blacklisting
> of some IPs.
> Can you try to ssh connect from different IP?
> (I'm CCing it to systems@)
> > I guessed that the server has forgotten my public key, so I uploaded it
> > again. I don't know if it is related, but the listserve forgot that I was
> > receiving the "digest" form of the list on Oct 16 or so.
> > After the upload still no luck -- though there may be some form of
> > authorization required and/or delay built in, since when I first uploaded
> > public key last year, it didn't work for at least a day.
> > George
> > On Sat, Oct 30, 2010 at 5:53 PM, Aleksey Lim <alsroot at member.fsf.org>
> > > On Sat, Oct 30, 2010 at 05:34:34PM -0400, George Hunt wrote:
> > > > I have 2 projects that I have been pushing git commits to for almost
> > > > year. In one I created a new branch, and was concerned that my local
> > > change
> > > > was preventing the successful "git push". But the other project has
> > > > structural changes, and still gets the response "fatal: the remote
> > > hung
> > > > up unexpectedly" -- which I see has been a source of lots of
> > > for
> > > > the inner circle.
> > > >
> > > > Should I just wait for 6 hours, and try again? How to proceed?
> > >
> > > Check if:
> > >
> > > * `ssh gitorious at git.sugarlabs.org` outputs "PTY allocation request.."
> > > * `git config remote.origin.url` output is equal to particular push
> > > on your project web page on git.sl.o
> > >
> > > --
> > > Aleksey
> > >
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel