Skip to contentSkip to conversation

Problems with the git://linux-nfs.org/ server

DISCUSSION Boaz Harrosh 3 participants 6 messages Sep 28, 2010 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

It looks like the git daemon on git://linux-nfs.org/ is down

Thanks
Boaz

#1 lore raw
Quoted 4 lines · Boaz Harrosh

It looks like the git daemon on git://linux-nfs.org/ is down

Thanks
Boaz

It's working for me...

[trondmy@heimdal linux-2.6]$ git remote update linux-nfs Fetching linux-nfs

Cheers
Trond

A message that is not in the archive (sent off-list or not yet received): 1285679386.9185.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org

#3 lore raw
Quoted 6 lines · Trond Myklebust
Quoted 4 lines · Boaz Harrosh

It looks like the git daemon on git://linux-nfs.org/ is down

Thanks
Boaz

Quoted 8 lines

It's working for me...

[trondmy@heimdal linux-2.6]$ git remote update linux-nfs Fetching linux-nfs

Cheers
Trond

Thanks. I still get problems so I guess it's related to this side of the ocean, I'm trying for example:

$ git ls-remote git://git.linux-nfs.org/~trondmy/nfs-2.6.git
And get: git.linux-nfs.org[0: 173.201.45.137]: errno=Connection timed out

But ping git.linux-nfs.org works (8% packet loss)

I'll wait for things to calm down, I guess

Boaz

#4 lore raw
Quoted 16 lines · Boaz Harrosh
Quoted 6 lines · Trond Myklebust
Quoted 4 lines · Boaz Harrosh

It looks like the git daemon on git://linux-nfs.org/ is down

Thanks
Boaz

Quoted 8 lines

It's working for me...

[trondmy@heimdal linux-2.6]$ git remote update linux-nfs Fetching linux-nfs

Cheers
Trond

Quoted 6 lines

Thanks. I still get problems so I guess it's related to this side of the ocean, I'm trying for example:

$ git ls-remote git://git.linux-nfs.org/~trondmy/nfs-2.6.git
And get: git.linux-nfs.org[0: 173.201.45.137]: errno=Connection timed out

Yes. The above too works for me, and I can't see anything in the logs that indicates anything wrong.

Could it perhaps be that you are hitting one of those ancient BSD-based routers that are broken w.r.t. TCP explicit congestion notification (a.k.a. ECN) and/or TCP window scaling? You might try turning those off on your client and see if that helps.

Cheers
Trond

A message that is not in the archive (sent off-list or not yet received): 1285681777.9185.13.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org

#6 lore raw
Quoted 24 lines · Trond Myklebust
Quoted 16 lines · Boaz Harrosh
Quoted 6 lines · Trond Myklebust
Quoted 4 lines · Boaz Harrosh

It looks like the git daemon on git://linux-nfs.org/ is down

Thanks
Boaz

Quoted 8 lines

It's working for me...

[trondmy@heimdal linux-2.6]$ git remote update linux-nfs Fetching linux-nfs

Cheers
Trond

Quoted 6 lines

Thanks. I still get problems so I guess it's related to this side of the ocean, I'm trying for example:

$ git ls-remote git://git.linux-nfs.org/~trondmy/nfs-2.6.git
And get: git.linux-nfs.org[0: 173.201.45.137]: errno=Connection timed out
Quoted 7 lines

Yes. The above too works for me, and I can't see anything in the logs that indicates anything wrong.

Could it perhaps be that you are hitting one of those ancient BSD-based routers that are broken w.r.t. TCP explicit congestion notification (a.k.a. ECN) and/or TCP window scaling? You might try turning those off on your client and see if that helps.

hmm, we also see ~16% packet loss over PING :-(

Benny

Quoted 4 lines

Cheers
Trond

#7 lore raw
Quoted 28 lines · Benny Halevy
Quoted 27 lines · Trond Myklebust
Quoted 16 lines · Boaz Harrosh
Quoted 6 lines · Trond Myklebust
Quoted 4 lines · Boaz Harrosh

It looks like the git daemon on git://linux-nfs.org/ is down

Thanks
Boaz

Quoted 8 lines

It's working for me...

[trondmy@heimdal linux-2.6]$ git remote update linux-nfs Fetching linux-nfs

Cheers
Trond

Quoted 6 lines

Thanks. I still get problems so I guess it's related to this side of the ocean, I'm trying for example:

$ git ls-remote git://git.linux-nfs.org/~trondmy/nfs-2.6.git
And get: git.linux-nfs.org[0: 173.201.45.137]: errno=Connection timed out

Yes. The above too works for me, and I can't see anything in the logs that indicates anything wrong.

Quoted 6 lines
Quoted 4 lines

Could it perhaps be that you are hitting one of those ancient BSD-based routers that are broken w.r.t. TCP explicit congestion notification (a.k.a. ECN) and/or TCP window scaling? You might try turning those off on your client and see if that helps.

hmm, we also see ~16% packet loss over PING :-(

But I don't see this from Panasas' US hosts so it's somewhere in between Israel and linux-nfs.org

Benny

Quoted 11 lines

Benny

Quoted 4 lines

Cheers
Trond

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html