Did you run that from within UC Davis? There is quite a number of academic networks that subscribe to the "if we filter out ICMP at the network border we can't be hacked" fallacy. A better test would be:
$ ssh g...@trac.sagemath.org PTY allocation request failed on channel 0 hello vbraun, this is git@trac running gitolite3 3.5.3.1-2 (Debian) on git 1.9.1 R W gitolite-admin R W sage Connection to trac.sagemath.org closed. PS: the github url is for releases, so if you want to work on tickets you need to be able to connect to trac... On Friday, April 28, 2017 at 5:22:38 PM UTC+2, Anne Schilling wrote: > > But for me this still does not work. I cannot even ping trac: > > ping sine.math.ucdavis.edu > PING sine.math.ucdavis.edu (169.237.99.79): 56 data bytes > 64 bytes from 169.237.99.79: icmp_seq=0 ttl=57 time=13.852 ms > 64 bytes from 169.237.99.79: icmp_seq=1 ttl=57 time=16.273 ms > .... > > anne$ ping trac.sagemath.org > PING trac.sagemath.org (104.197.143.230): 56 data bytes > Request timeout for icmp_seq 0 > Request timeout for icmp_seq 1 > ... > > anne$ ping git.sagemath.org > PING trac.sagemath.org (104.197.143.230): 56 data bytes > Request timeout for icmp_seq 0 > Request timeout for icmp_seq 1 > ... > > Should I be using the github url > > url = git://github.com/sagemath/sage.git > > This is not what my current set-up does (but it has always worked before): > > anne$ git remote -v > origin git://trac.sagemath.org/sage.git (fetch) > origin git://trac.sagemath.org/sage.git (push) > trac git://trac.sagemath.org/sage.git (fetch) > trac g...@trac.sagemath.org:sage.git <javascript:> (push) > > > Best, > > Anne > On Friday, April 28, 2017 at 3:49:02 AM UTC-7, Kwankyu Lee wrote: >> >> Hi, >> >> For the remote origin, the usual configuration is >> >> [remote "origin"] >> url = git://github.com/sagemath/sage.git >> fetch = +refs/heads/*:refs/remotes/origin/* >> >> If the same fetch setting is used for the remote trac, then the git >> client would try to download all heads from the trac. >> >> I confess that I mistakenly committed this "crime" recently :-( and fixed >> it as soon as I recognized it. >> >> Might this be a cause of the recent trac slowdown? By the way, I did not >> experience it myself... I am not sure if this is related and/or makes >> sense... >> >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
