Hi, When attempting to update an in-addr.arpa object today, I repeatedly get: Unexpected error: please retry later Did not happen yesterday. Is it just me or everyone? Regards, Hank
On 28/02/2025 10:20, Hank Nussbacher wrote:
Hi,
When attempting to update an in-addr.arpa object today, I repeatedly get:
Unexpected error: please retry later
Did not happen yesterday. Is it just me or everyone?
Regards,
Hank
I should note that even though I get the error messages of: Update of domain failed, please see below for more details Unexpected error: please retry later the update did go through and was updated! Weird. -Hank
Good morning Hank,
On 28 Feb 2025, at 09:23, Hank Nussbacher <hank@interall.co.il> wrote:
On 28/02/2025 10:20, Hank Nussbacher wrote:
Hi,
When attempting to update an in-addr.arpa object today, I repeatedly get:
Unexpected error: please retry later
Did not happen yesterday. Is it just me or everyone?
If this happened around 04:41 - 05:01 UTC it may have been related to this incident with one of our loadbalancers : https://manage.statuspage.io/pages/wbqx0dgqy4n6/incidents#incidents
Regards,
Hank
I should note that even though I get the error messages of:
Update of domain failed, please see below for more details
Unexpected error: please retry later
the update did go through and was updated! Weird.
I will investigate how this happened. Regards Ed Shryane RIPE NCC
Hi Hank, Colleagues,
On 28 Feb 2025, at 09:23, Hank Nussbacher <hank@interall.co.il> wrote:
... I should note that even though I get the error messages of:
Update of domain failed, please see below for more details
Unexpected error: please retry later
I investigated further. The "Unexpected error: please retry later" message is generated by the DB web application, not by Whois. The DB web application calls Whois to perform the update with a 1 minute request timeout. I found that twice when you updated a domain object around 08:15 UTC, Whois took just over a minute each time to respond. For domain object updates, Whois calls the Zonemaster DNS check service (https://zonemaster.ripe.net/), which can take some time. I propose that we fix this by making the request timeout longer in the DB web application (say 5 minutes).
the update did go through and was updated! Weird.
The Whois update request still succeeded because the DB application gives up after a minute, but the Whois update will continue even if the client HTTP request is interrupted (closed). Thanks Hank for reporting this issue. Regards Ed Shryane RIPE NCC
participants (2)
-
Edward Shryane -
Hank Nussbacher