SSLMate / certspotter

Certificate Transparency Log Monitor
https://sslmate.com/certspotter
Mozilla Public License 2.0
978 stars 84 forks source link

GetLeavesByRange request failed: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4579991 vs. 4194304) #98

Closed schildbach closed 4 months ago

schildbach commented 4 months ago

I get lots of errors with recently added logs, like this:

certspotter_1  | 2024/06/28 07:44:33 error downloading entries from https://wyvern.ct.digicert.com/2025h2/: GET https://wyvern.ct.digicert.com/2025h2/ct/v1/get-entries?start=18000&end=18999: 403 Forbidden (Forbidden
certspotter_1  | backend GetLeavesByRange request failed: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4579991 vs. 4194304)
certspotter_1  | )

The affected logs are stuck. Yet, they keep growing so they seem to be active.

AGWA commented 4 months ago

This has been reported to the log operator here: https://groups.google.com/a/chromium.org/g/ct-policy/c/2ySfg9xucqc

6267062BA18944F0882B9536EEDB2588 commented 4 months ago

Hello,

I've also experienced this


2024/06/28 17:33:00 error downloading entries from https://sphinx.ct.digicert.com/2024h2/: GET https://sphinx.ct.digicert.com/2024h2/ct/v1/get-entries?start=953000&end=953999: 403 Forbidden (Forbidden | f0e52392af49440cbe6361c13aebb718 | certspotter

June 28, 2024 at 13:33 (UTC-4:00) | backend GetLeavesByRange request failed: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4195259 vs. 4194304)

2024/06/28 17:48:44 error downloading entries from https://mammoth2024h2.ct.sectigo.com/: GET https://mammoth2024h2.ct.sectigo.com/ct/v1/get-entries?start=133855488&end=133856487: 403 Forbidden (Forbidden
AGWA commented 4 months ago

This will resolve once the log operator fixes their broken logs. You can follow the ct-policy mailing list (linked above) for updates.

AGWA commented 4 months ago

The logs have been fixed.

schildbach commented 4 months ago

Confirming it has indeed been fixed.