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

ethClient "NOT_AVAILABLE" #77

Open
vikipedia48 opened this issue Apr 4, 2024 · 0 comments
Open

ethClient "NOT_AVAILABLE" #77

vikipedia48 opened this issue Apr 4, 2024 · 0 comments

Comments

@vikipedia48
Copy link

I can successfully connect to a Hyperledger Besu network, but health checks keep failing every 5 seconds.

This is the /api/actuator/health response:
{"status":"UP","components":{"discoveryComposite":{"description":"Discovery Client not initialized","status":"UNKNOWN","components":{"discoveryClient":{"description":"Discovery Client not initialized","status":"UNKNOWN"}}},"ethClient":{"status":"NOT_AVAILABLE","details":{"error":"java.lang.IllegalArgumentException: Value must not be null"}},"mongo":{"status":"UP","details":{"latestIndexedBlock":84892}},"node":{"status":"UP","details":{"projectVersion":"3.3.10","nodeEndpoint":"http://172.20.76.6:31311"}},"ping":{"status":"UP"},"redis":{"status":"UP","details":{"version":"7.2.4"}},"refreshScope":{"status":"UP"}}}

While I'm fairly certain the problem is on my side, how does Chainlens get the ethClient field, whose nullness produces the error? How would I set it on my network so that the health check returns a valid response?

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