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

Better info on node errors #17

Closed
smsearcy opened this issue Apr 11, 2022 · 2 comments
Closed

Better info on node errors #17

smsearcy opened this issue Apr 11, 2022 · 2 comments

Comments

@smsearcy
Copy link
Owner

Currently, when unable to connect to a node the IP address is logged but no database entry is created, and thus any links to that node are not created (even though the new API provides a fair amount of data about the link).

A better solution would seem to be doing a reverse DNS lookup on the IP address, so that with a name and IP we should have enough information to create a minimal node entry and thus can populate the links from the "good" side of the link.

I have a branch (in GitLab?) where I have most of the reverse DNS code working. Need to polish that up and then incorporate it into the error processing.

@smsearcy
Copy link
Owner Author

This could work if the node is temporarily having problems (i.e. we have a record for the node), otherwise there won't be any coordinates for mapping.

@smsearcy
Copy link
Owner Author

Reviewing this issue, I think I've done everything I can for now so I'm closing it.

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

1 participant