Skip to content
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

Search returns 500 API error #119

Closed
ruben-herold opened this issue Sep 16, 2016 · 9 comments
Closed

Search returns 500 API error #119

ruben-herold opened this issue Sep 16, 2016 · 9 comments

Comments

@ruben-herold
Copy link

hi,

If I try the search I ever got an 500 API error.

@tuxis-ie
Copy link
Owner

Version? Php-error logs? pdns Error logs?

A bit more information is useful. My primary reaction to such an issue is 'Ok, thanks for the information' and then just close the bug.

@skfigved
Copy link

I had the same problem after updating to PowerDNS 4. In my case it was that some zones actually contained bad data which threw an 500 API error when i searched for those zones. I was able to fix the issue by identifying the bad zones and deleting the records manually in mysql

@richard-underwood
Copy link
Contributor

I had a similar problem after importing a zone from bind - there were duplicate records in the zone which needed thinning out. It was a powerdns problem, not nsedit.

@tuxis-ie
Copy link
Owner

Ok. So mainly, the errorhandling needs to be better.

@skfigved
Copy link

I guess it might be related to this?
PowerDNS/pdns#4195

@tuxis-ie
Copy link
Owner

@skf82 No. This issue is about search, not about importing. But thank you for pointing out that issue, it is something we are using. :)

@telefax
Copy link

telefax commented Oct 8, 2016

I just did a bulk import to pdns mysql via zone2sql and got the same problem when searching for a specific term in nsedit ui.

The httpd instance that run nsedit had nothing in its error logs.
But if you check the powerdns web statistics page (port 8081) you would see something like:

HTTP ISE for "/api/v1/servers/localhost/zones/some.zone.": STL Exception: Parsing record content (try 'pdnsutil check-zone'): Data field in DNS should start with quote (") at position 2 of '""v=spf1 mx ip4:1.1.1.1,2.2.2.2 -all""'

So, problem in this case was that I had a TXT record which was surrounded by extra quotes (probably had never worked at the place where the zones originates from).
Quick fix mysql query was to locate the records and then remove the extra quotes:

SELECT * FROMpowerdns_db.records where content like '""%""';

So again, not an nsedit problem it self, but it's having a hard time interpreting syntax errors in zones :)

@tuxis-ie
Copy link
Owner

Yes, we have to find out if we get these messages from PDNS. I don't know yet.

@tuxis-ie
Copy link
Owner

I've created issue #128 for these issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants