-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API timeout for GET /api/v1/servers/localhost/zones in PDNS 4.9 - It even crashes OS #14720
Comments
Some initial questions:
|
Thanks for the followup, sorry for the missing info. |
Would you by any chance be able to check how much memory is used during that test? Do you know if the operating system reports an out-of-memory condition? Knowing how much the same operation uses with version 4.1 would be very useful as well. |
We upscale the instance to a xlarge (4vcpu 16gb ram) assuming it was related to this. We can check the OS yes. But not right away sadly |
Found a solid lead This change, cascades into other issues within PDA so is not a fix for us. Could this help in pinpointing the cause of it? |
We migrated from PDNS (Authorative) v4.1.X to v4.9.
We noticed that the PDNS API is not working properly with
/api/v1/servers/localhost/zones
it just times out.
Running the same curl command in the old version (4.1) works as expected taking under 1 minute.
We ran other api calls just to be sure is not a connectivity issue and they worked as expected.
This makes PDA unusable, as it relays on GET localhost/zones, to sync its UI...
So to summarize:
curl -H 'X-API-Key: <apikey>' http://127.0.0.1:8081/api/v1/servers/localhost/zones/domain1.com
--> OKcurl -H 'X-API-Key: <apikey>' http://127.0.0.1:8081/api/v1/servers/localhost/zones
--> OK (under 1 minute)curl -H 'X-API-Key: <apikey>' http://127.0.0.1:8081/api/v1/servers/localhost/zones/domain1.com
--> OKcurl -H 'X-API-Key: <apikey>' http://127.0.0.1:8081/api/v1/servers/localhost/zones
--> ERROR (Times out after 10 minutes, also sometimes crashes the whole VM)We have around 300k domains managed by this PDNS server.
Conducted several more tests:
Test 1:
On the Rocky Linux 9 -->
It didn't work in any case
Test 2:
On the CentOS 7 -->
Environment
Issue Type and Service
Expected behaviour
for the PDNS api to call to
http://127.0.0.1:8081/api/v1/servers/localhost/zones
to respond under 5 minutesActual behaviour
The request timesout (sometimes even crashes the VM)
Other information
This worked perfectly on version 4.1
The text was updated successfully, but these errors were encountered: