broken pipe error here too,
was working fine 2hours ago

On Tuesday 11 July 2017  12:23, Mike Blumenkrantz wrote :
> I've now lost all ssh access to all enlightenment-related servers on all my
> machines. The one computer which was previously working now fails with a
> broken pipe error, and the rest have the same connection closed error.
> 
> On Tue, Jul 11, 2017 at 6:22 AM Stefan Schmidt <ste...@osg.samsung.com>
> wrote:
> 
> > Hello.
> >
> > On 07/11/2017 11:37 AM, Stefan Schmidt wrote:
> > >
> > >
> > > On 07/10/2017 09:24 PM, Davide Andreoli wrote:
> > >> 2017-07-10 15:33 GMT+02:00 Mike Blumenkrantz
> > >> <michael.blumenkra...@gmail.com <mailto:michael.blumenkra...@gmail.com
> > >>:
> > >>
> > >>     Hi,
> > >>
> > >>     I've been getting this error for some time now on one of my machines
> > >>     when I
> > >>     try to do git/ssh operations:
> > >>
> > >>     ssh_exchange_identification: Connection closed by remote host
> > >>     fatal: Could not read from remote repository.
> > >>
> > >>     Please make sure you have the correct access rights
> > >>     and the repository exists.
> > >>
> > >>     Others have been experiencing this issue as well, so it seems to be
> > >>     a new
> > >>     issue with server configuration.
> > >>
> > >>
> > >> Same here, I cannot perform any git operation anymore
> > >
> > > My situation is that I can pull and push to git just fine. But in the
> > > exact same shell I get a error when trying to log into a shell of our
> > > server.
> > >
> > > stefan@work efl (master) $ ssh download.enlightenment.org
> > > ssh_exchange_identification: Connection closed by remote host
> > >
> > > This blocks the upload of any efl beta2 tarballs right now.
> > > I will try to debug this a bit further on my end. As far as I can do
> > that.
> >
> > It looks like we have two different problems here:
> >
> > 1) Git access over ssh does not work. Zmike(?) as well as Dave seem to
> > have this problem. A lot of people are pushing and pulling without a
> > problem at the same time though.
> >
> > 2) SSH shell access to our server. Thanks to some hints from Marcel I
> > think we can narrow it down to a problem with our ssh proxy command
> > setup. I can access git.e.org as well as devs.e.org without a problem.
> > Both of them are not accessed via the proxy command, but directly.
> > For all server where I would need the proxy command (download, build,
> > etc) it fails for me and it also fails for Marcel. Which sounds to me
> > like a server side problem and nothing local.
> >
> > regards
> > Stefan Schmidt
> >
> >
> > ------------------------------------------------------------------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > enlightenment-devel mailing list
> > enlightenment-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> >
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
--- Hell'O from Yverdoom

Jérémy (jeyzu)

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to