Обсуждение: [HACKERS] git down

Поиск
Список
Период
Сортировка

[HACKERS] git down

От
Erik Rijkers
Дата:
git.postgresql.org is down/unreachable

( git://git.postgresql.org/git/postgresql.git )



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] git down

От
Andreas Karlsson
Дата:
On 10/27/2017 10:51 PM, Erik Rijkers wrote:
> git.postgresql.org is down/unreachable
> 
> ( git://git.postgresql.org/git/postgresql.git )

Yes, I noticed this too, but 
https://git.postgresql.org/git/postgresql.git still works fine.

I guess it makes sense to remove unencrypted access, but in that case 
https://git.postgresql.org/gitweb/?p=postgresql.git;a=summary should not 
advertise supporting the git protocol. I have not seen any announcement 
either, but that could just be me not paying enough attention.

Andreas



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] git down

От
Magnus Hagander
Дата:


On Mon, Oct 30, 2017 at 2:35 AM, Andreas Karlsson <andreas@proxel.se> wrote:
On 10/27/2017 10:51 PM, Erik Rijkers wrote:
git.postgresql.org is down/unreachable

( git://git.postgresql.org/git/postgresql.git )

Yes, I noticed this too, but https://git.postgresql.org/git/postgresql.git still works fine.

I guess it makes sense to remove unencrypted access, but in that case https://git.postgresql.org/gitweb/?p=postgresql.git;a=summary should not advertise supporting the git protocol. I have not seen any announcement either, but that could just be me not paying enough attention.

We definitely still support the unencrypted git protocol. I do recommend using https, but that doesn't mean git shouldn't work. There seems to have been some network issues and the git daemon doesn't do a very good job of handling hung sessions. I've cleaned up for now and it seems to be working again, and we'll do some more digging into what actually was the root cause. 


--

Re: [HACKERS] git down

От
Sandeep Thakkar
Дата:
Hi,

I'm seeing this warning (git.postgresql.org[0: 2620:122:b000:7::243]: errno=Network is unreachable) on one of the buildfarm animals (anole) from last few weeks. The git version is 1.7.4.2. When I use https, it errors "fatal: cannot exec 'git-remote-https': Permission denied"

On Mon, Oct 30, 2017 at 2:32 PM, Magnus Hagander <magnus@hagander.net> wrote:


On Mon, Oct 30, 2017 at 2:35 AM, Andreas Karlsson <andreas@proxel.se> wrote:
On 10/27/2017 10:51 PM, Erik Rijkers wrote:
git.postgresql.org is down/unreachable

( git://git.postgresql.org/git/postgresql.git )

Yes, I noticed this too, but https://git.postgresql.org/git/postgresql.git still works fine.

I guess it makes sense to remove unencrypted access, but in that case https://git.postgresql.org/gitweb/?p=postgresql.git;a=summary should not advertise supporting the git protocol. I have not seen any announcement either, but that could just be me not paying enough attention.

We definitely still support the unencrypted git protocol. I do recommend using https, but that doesn't mean git shouldn't work. There seems to have been some network issues and the git daemon doesn't do a very good job of handling hung sessions. I've cleaned up for now and it seems to be working again, and we'll do some more digging into what actually was the root cause. 


--



--
Sandeep Thakkar


Re: [HACKERS] git down

От
Tom Lane
Дата:
Sandeep Thakkar <sandeep.thakkar@enterprisedb.com> writes:
> I'm seeing this warning (git.postgresql.org[0: 2620:122:b000:7::243]:
> errno=Network is unreachable) on one of the buildfarm animals (anole) from
> last few weeks. The git version is 1.7.4.2. When I use https, it errors
> "fatal: cannot exec 'git-remote-https': Permission denied"

Well, the rest of the buildfarm seems fine, so the problem must be local.
Maybe the permissions on that file (git-remote-https) got messed up?

FWIW, 1.7.4.2 is pretty durn ancient.  Consider just installing a new git
revision instead of troubleshooting the one you've got.

            regards, tom lane