This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC Bugzilla (and other) timeouts


On Wed, 26 Feb 2020 at 14:42, Jason Merrill <jason@redhat.com> wrote:
>
> On Wed, Feb 26, 2020 at 3:39 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>>
>> On Tue, 25 Feb 2020 at 18:25, Martin Sebor wrote:
>> >
>> > Bugzilla has been slow lately, and today to the point of timing out
>> > (I see the same problem with Git).  This seems to be a recurring theme
>> > around the time of a GCC release.  Is anyone else experiencing this
>> > problem and if so, does anyone know what the cause it and an ETA for
>> > a solution?  Is the upcoming hardware upgrade expected to solve it?
>> >
>> > Thanks
>> > Martin
>> >
>> > $ git pull
>> > Connection closed by 209.132.180.131 port 22
>> > fatal: Could not read from remote repository.
>> >
>> > Please make sure you have the correct access rights
>> > and the repository exists.
>>
>> What URL are you using to pull? (git remote get-url origin)
>>
>> Bugzilla and httpd are very slow, but I haven't had any git timeouts.
>> If you're using anonymous access that gets throttled more aggressively
>> than authenticated access (using git+ssh:// for the protocol).
>
>
> Yes, I used to use git:// for pulls and ssh:// for pushes, but switched to ssh:// for both because I was getting too many rejected connections.

Another trick I use to improve round trip time of git operations is to
use an ssh control path, see ControlMaster in man 5 ssh_config.

In my ~/.ssh/config I have:

Host gcc.gnu.org
  User redi
  Protocol 2
  ForwardX11 no
  ForwardAgent no
  Compression yes
  # instead of ControlMaster=auto you can open a master connection
with ssh -M -N -f redi@gcc.gnu.org
  ControlMaster auto
  # OpenSSH 5.6 and later:
  ControlPersist yes
  ControlPath /tmp/ssh_%h

This keeps a persistent connection open to the server which gets
reused every time I connect over ssh. The downside is that sometimes
after a network change the control path gets stuck and needs to be
manually closed with 'ssh -O exit gcc.gnu.org' (it will get
automatically recreated by the next ssh connection or git fetch/push).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]