There seems to be a 5-minute timeout, is your internet connection really slow?
[13/Jun/2015:07:57:35 -0700] "GET /sage.git/info/refs?service=git-upload-pack HTTP/1.1" 200 431350 [13/Jun/2015:07:57:37 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 1125 [13/Jun/2015:07:57:38 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 1912 [13/Jun/2015:07:57:38 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 3630 [13/Jun/2015:07:57:39 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 6635 [13/Jun/2015:07:57:39 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 12723 [13/Jun/2015:07:57:40 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 22931 [13/Jun/2015:07:57:41 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 50308 [13/Jun/2015:07:57:43 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 100612 [13/Jun/2015:07:57:45 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 160013 [13/Jun/2015:07:57:48 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 200 222889 [Sat Jun 13 08:02:55 2015] [error] [client x.x.x.x] (70007)The timeout specified has expired: Error reading request entity data [13/Jun/2015:07:57:52 -0700] "POST /sage.git/git-upload-pack HTTP/1.1" 500 638 On Saturday, June 13, 2015 at 8:18:36 PM UTC+2, Emmanuel Charpentier wrote: > > I do not know how to find your email address, and I don't know how to PM > you friom Google's Groups. I have to search for this... > > -- > Emmanuel Charpentier > > . > Le samedi 13 juin 2015 17:56:06 UTC+2, Volker Braun a écrit : >> >> Can you PM me your IP number, then I'll grep through the log... >> >> >> >> >> >> On Saturday, June 13, 2015 at 2:17:37 PM UTC+2, Emmanuel Charpentier >> wrote: >>> >>> [ got a famillial NMI. Sorry for the delay... ] >>> >>> Dear Volker, >>> >>> First of all, thank you for your attention to my petty troubles ! >>> >>> Le samedi 13 juin 2015 12:05:57 UTC+2, Volker Braun a écrit : >>>> >>>> Which version of git are you using? Have you tried the git version that >>>> is included in Sage? >>>> >>> >>> From another directory : >>> >>> charpent@asus16-ec:~/Perso/Free$ git --version >>> git version 2.1.4 >>> >>> After installing Sage's git, same difference (again...) : >>> >>> charpent@asus16-ec:/usr/local/sage-6.8$ ./sage -git --version >>> git version 2.3.0 >>> charpent@asus16-ec:/usr/local/sage-6.8$ ./sage -git fetch -v >>> POST git-upload-pack (gzip 12731 to 6418 bytes) >>> POST git-upload-pack (gzip 13281 to 6704 bytes) >>> POST git-upload-pack (gzip 14831 to 7489 bytes) >>> POST git-upload-pack (gzip 17481 to 8821 bytes) >>> POST git-upload-pack (gzip 22981 to 11608 bytes) >>> POST git-upload-pack (gzip 33931 to 17183 bytes) >>> POST git-upload-pack (gzip 56881 to 28664 bytes) >>> POST git-upload-pack (gzip 103831 to 51903 bytes) >>> POST git-upload-pack (gzip 148581 to 74060 bytes) >>> POST git-upload-pack (gzip 199481 to 99218 bytes) >>> POST git-upload-pack (gzip 228636 to 113642 bytes) >>> error: RPC failed; result=22, HTTP code = 500 >>> fatal: The remote end hung up unexpectedly >>> >>> >>> HTH, >>> >>> -- >>> Emmanuel Charpentier at the end of his rope... >>> >>> >>>> sage -f git >>>> sage -git fetch -v >>>> >>> >>> >>> >>>> >>>> >>>> >>>> On Saturday, June 13, 2015 at 11:50:07 AM UTC+2, Emmanuel Charpentier >>>> wrote: >>>>> >>>>> [ I didn't know that option. Interesting... ] Anyway, same difference : >>>>> >>>>> charpent@asus16-ec:/usr/local/sage-6.8$ git config http.postBuffer >>>>> 524288000charpent@asus16-ec:/usr/local/sage-6.8$ git fetch -v >>>>> POST git-upload-pack (gzip 12681 to 6392 bytes) >>>>> POST git-upload-pack (gzip 13231 to 6679 bytes) >>>>> POST git-upload-pack (gzip 14781 to 7465 bytes) >>>>> POST git-upload-pack (gzip 17431 to 8795 bytes) >>>>> POST git-upload-pack (gzip 22931 to 11585 bytes) >>>>> POST git-upload-pack (gzip 33881 to 17159 bytes) >>>>> POST git-upload-pack (gzip 56831 to 28643 bytes) >>>>> POST git-upload-pack (gzip 103781 to 51882 bytes) >>>>> POST git-upload-pack (gzip 148531 to 74038 bytes) >>>>> POST git-upload-pack (gzip 199431 to 99200 bytes) >>>>> POST git-upload-pack (gzip 228586 to 113622 bytes) >>>>> error: RPC failed; result=22, HTTP code = 500 >>>>> fatal: The remote end hung up unexpectedly >>>>> >>>>> I am at loss : It's not on my side (I even went to te extremity of >>>>> rebooting my machine). >>>>> >>>>> Le samedi 13 juin 2015 00:45:35 UTC+2, Volker Braun a écrit : >>>>>> >>>>>> I tried cloning just the repo and then fetching all of trac and it >>>>>> worked. My git version seems to be more recent though, the output is all >>>>>> different. Have you tried increasing the post buffer? >>>>>> >>>>>> git config --global http.postBuffer 524288000 >>>>>> git fetch -v >>>>>> >>>>>> >>>>>> On Friday, June 12, 2015 at 10:46:18 PM UTC+2, Emmanuel Charpentier >>>>>> wrote: >>>>>>> >>>>>>> Things seem still flaky now (22:42 CET) : git fetch still hangs. But >>>>>>> git fetch -v gives some signs of life before hanging : >>>>>>> >>>>>>> git fetch -v >>>>>>> POST git-upload-pack (gzip 12481 to 6253 bytes) >>>>>>> POST git-upload-pack (gzip 13031 to 6539 bytes) >>>>>>> POST git-upload-pack (gzip 14581 to 7322 bytes) >>>>>>> POST git-upload-pack (gzip 17231 to 8652 bytes) >>>>>>> POST git-upload-pack (gzip 22731 to 11443 bytes) >>>>>>> POST git-upload-pack (gzip 33681 to 17013 bytes) >>>>>>> POST git-upload-pack (gzip 56631 to 28499 bytes) >>>>>>> POST git-upload-pack (gzip 103581 to 51743 bytes) >>>>>>> POST git-upload-pack (gzip 148331 to 73896 bytes) >>>>>>> POST git-upload-pack (gzip 199231 to 99039 bytes) >>>>>>> POST git-upload-pack (gzip 228286 to 113433 bytes) >>>>>>> error: RPC failed; result=22, HTTP code = 500 >>>>>>> fatal: The remote end hung up unexpectedly >>>>>>> >>>>>>> Is there anything I can do at my end to fix this ? Or pray for >>>>>>> Malaysian to recover reason (an possibly sacrificing another manager) ? >>>>>>> >>>>>>> -- >>>>>>> Emmanuel Charpentier >>>>>>> >>>>>>> >>>>>>> >>>>>>> Le vendredi 12 juin 2015 11:16:41 UTC+2, Volker Braun a écrit : >>>>>>>> >>>>>>>> I've seen it now, too. The connection is pretty flaky even when it >>>>>>>> works, e.g. massive packet loss (look at the sequence numbers): >>>>>>>> >>>>>>>> >>>>>>>> $ ping trac.sagemath.org >>>>>>>> PING trac.sagemath.org (128.208.178.249): 56 data bytes >>>>>>>> 64 bytes from 128.208.178.249: seq=6 ttl=46 time=512.834 ms >>>>>>>> 64 bytes from 128.208.178.249: seq=7 ttl=46 time=514.608 ms >>>>>>>> 64 bytes from 128.208.178.249: seq=9 ttl=46 time=475.129 ms >>>>>>>> 64 bytes from 128.208.178.249: seq=15 ttl=46 time=512.305 ms >>>>>>>> 64 bytes from 128.208.178.249: seq=27 ttl=46 time=478.100 ms >>>>>>>> 64 bytes from 128.208.178.249: seq=29 ttl=46 time=476.673 ms >>>>>>>> >>>>>>>> >>>>>>>> Tracing it, the problem seems to originate at the Telia -> Level3 >>>>>>>> boundary. So there is nothing we can do, just wait for the big guys to >>>>>>>> fix >>>>>>>> it. >>>>>>>> >>>>>>>> >>>>>>>> On Friday, June 12, 2015 at 11:04:17 AM UTC+2, Nathann Cohen wrote: >>>>>>>>> >>>>>>>>> Desperately trying to push something, the function hangs. I also >>>>>>>>> cannot get to load the ticket I want to update [1] :-P >>>>>>>>> >>>>>>>>> Nathann >>>>>>>>> >>>>>>>>> [1] http://trac.sagemath.org/ticket/18681 >>>>>>>>> >>>>>>>> -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
