[Urgent] Daily ls-remote rate limit exceeded

lucamilanesio

unread,

Sep 9, 2015, 4:22:47 AM9/9/15

to Repo and Gerrit Discussion

Hi all,

with great surprise this morning the gerrit-ci.gerritforge.com site stopped working because of this error:

https://gerrit.googlesource.com/gerrit-ci-scripts +refs/changes/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: remote error: Daily ls-remote rate limit exceeded for IP 188.165.175.132.

What is the daily limit of Git requests to gerrit.googlesource.com? Is there a way to increase that limit?

If not, I would need to start looking at different strategies to fetch code for the Continuous Integration server :-(

Luca.

lucamilanesio

unread,

Sep 9, 2015, 4:52:17 PM9/9/15

to Repo and Gerrit Discussion

ping ... any Googler around?

lucamilanesio

unread,

Sep 9, 2015, 5:16:42 PM9/9/15

to Repo and Gerrit Discussion

I checked the SCM polling time I had on Jenkins and it was honestly too low (5 mins).

As there are around 150 jobs, it would have meant over 43K calls per day ... and I reckon the daily limit if far below that threshold.

With [1] I've reduced by 10 time the number of calls but I need to know if 4.3K calls per day are still acceptable for Google's Git Servers.

Feedback is more than appreciated :-)

Luca.

[1] https://gerrit-review.googlesource.com/#/c/70767/

Shawn Pearce

unread,

Sep 9, 2015, 7:31:07 PM9/9/15

to lucamilanesio, Repo and Gerrit Discussion

Heh. Yes, we have a rate limit pretty far below 43K git calls per-day per-IP for anonymous clients.

If you get a cookie from the https://gerrit.googlesource.com/new-password link and use that the client will be authenticated, which moves its rate limit around (+3x) as we can more easily contact (or block) an abusive client we "know".

Björn Pedersen

unread,

Sep 10, 2015, 3:07:53 AM9/10/15

to Repo and Gerrit Discussion

Hi,

One general idea would be to use the gerrit-trigger plugin that listens to stream-events. This way you do not need to poll.

Björn

Luca Milanesio

unread,

Sep 10, 2015, 3:20:10 AM9/10/15

to Björn Pedersen, Repo and Gerrit Discussion

I know … that would be the *BEST* option instead of pulling 43K times a day :-)

The problem is: Gerrit hosted in the Google’s infrastructure does not expose SSH and Gerrit stream events are not (yet) available over HTTP.

I discussed the issue with Robert Sandell (current maintainer of the Jenkins Gerrit Trigger plugin) and after the discussion we agreed that HTTP WebSockets are possibly the best solution.

Another possibility is RabbitMQ but I guess Google doesn’t easily provide that either ;-(

Luca.

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Pursehouse

unread,

Sep 10, 2015, 3:30:18 AM9/10/15

to Luca Milanesio, Björn Pedersen, Repo and Gerrit Discussion

On 09/10/2015 04:20 PM, Luca Milanesio wrote:
> I know … that would be the *BEST* option instead of pulling 43K times a
> day :-)
> The problem is: Gerrit hosted in the Google’s infrastructure does not
> expose SSH and Gerrit stream events are not (yet) available over HTTP.
>
> I discussed the issue with Robert Sandell (current maintainer of the
> Jenkins Gerrit Trigger plugin) and after the discussion we agreed that
> HTTP WebSockets are possibly the best solution.

This is something that might be possible after Martin's refactoring of
the events framework is merged.

> Another possibility is RabbitMQ but I guess Google doesn’t easily
> provide that either ;-(
>
> Luca.
>
>> On 10 Sep 2015, at 08:07, Björn Pedersen <ice...@googlemail.com

>> <mailto:ice...@googlemail.com>> wrote:
>>
>> Hi,
>>
>> One general idea would be to use the gerrit-trigger plugin that
>> listens to stream-events. This way you do not need to poll.
>>
>> Björn
>>
>> Am Mittwoch, 9. September 2015 10:22:47 UTC+2 schrieb lucamilanesio:
>>
>> Hi all,
>> with great surprise this morning the gerrit-ci.gerritforge.com

>> <http://gerrit-ci.gerritforge.com/> site stopped working because
>> of this error:
>>
>> https://gerrit.googlesource.com/gerrit-ci-scripts <https://gerrit.googlesource.com/gerrit-ci-scripts> +refs/changes/*:refs/remotes/origin/*" returned status code 128:

>> stdout:
>> stderr: fatal: remote error: Daily ls-remote rate limit exceeded for IP 188.165.175.132.
>>
>>

>> What is the daily limit of Git requests togerrit.googlesource.com <http://gerrit.googlesource.com/>? Is there a way to increase that limit?

>>
>> If not, I would need to start looking at different strategies to fetch code for the Continuous Integration server :-(
>>
>>
>> Luca.
>>
>>
>> --
>> --
>> To unsubscribe, email repo-discuss...@googlegroups.com

>> <mailto:repo-discuss...@googlegroups.com>

>> More info at http://groups.google.com/group/repo-discuss?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "Repo and Gerrit Discussion" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to repo-discuss...@googlegroups.com

>> <mailto:repo-discuss...@googlegroups.com>.

>> For more options, visit https://groups.google.com/d/optout.
>

> --
> --
> To unsubscribe, email repo-discuss...@googlegroups.com
> More info at http://groups.google.com/group/repo-discuss?hl=en
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Repo and Gerrit Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to repo-discuss...@googlegroups.com

> <mailto:repo-discuss...@googlegroups.com>.

Luca Milanesio

unread,

Sep 10, 2015, 3:34:12 AM9/10/15

to David Pursehouse, Björn Pedersen, Repo and Gerrit Discussion

It should be possible even now to implement stream events over HTTP WebSockets as plugin, similarly to the RabbitMQ implementation.
… or I am missing something?

Luca.

lucamilanesio

unread,

Sep 10, 2015, 4:22:11 AM9/10/15

to Repo and Gerrit Discussion, luca.mi...@gmail.com

Hi Shawn, thanks for the cookie suggestion: all set-up now, let's see how it goes.

Do you reckon I would be allowed to perform 4-5K calls per day HTTPS/Cookie authentication?

Luca.

xin...@intel.com

unread,

Dec 15, 2016, 2:56:55 AM12/15/16

to Repo and Gerrit Discussion

I have two copies of chromium code. One rebased successfully. After a mount , when I tried to rebase the second copy, it failed with below:

$gclient sync
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/libFuzzer/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/libFuzzer/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/libphonenumber/dist failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/liblouis/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/liblouis/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/liblouis/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/liblouis/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/lss failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/mesa/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/minigbm/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/openh264/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/lss failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/mesa/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/minigbm/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/openh264/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/lss failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/mesa/src failed; will retry after a short nap...
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /d1/chromium/src/third_party/minigbm/src failed; will retry after a short nap...
Syncing projects: 60% (49/81) src/third_party/mesa/src

src/third_party/liblouis/src (ERROR)
----------------------------------------
[0:00:37] Started.
[0:00:41] fatal: remote error: Daily ls-remote rate limit exceeded for IP xxx.xx.xx.xx
[0:00:43] fatal: remote error: Daily ls-remote rate limit exceeded for IP xxx.xx.xx.xx
[0:00:45] fatal: remote error: Daily ls-remote rate limit exceeded for IP xxx.xx.xx.xx
[0:00:49] fatal: remote error: Daily ls-remote rate limit exceeded for IP xxx.xx.xx.xx

git rebase-update
Fetching origin

fatal: remote error: Daily ls-remote rate limit exceeded

Dave Borowitz

unread,

Dec 15, 2016, 12:56:40 PM12/15/16

to xin...@intel.com, Repo and Gerrit Discussion

The "Daily ls-remote rate limit exceeded for IP" message means you are not authenticating to the service. Follow Shawn's instructions earlier in this thread for getting a cookie that will authenticate you and grant you higher quota.

--
--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com

More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss+unsubscribe@googlegroups.com.

Reply all

Reply to author

Forward