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

Ledger cache is probably not working as expected #2221

Open
jleach opened this issue Oct 11, 2024 · 0 comments
Open

Ledger cache is probably not working as expected #2221

jleach opened this issue Oct 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jleach
Copy link
Member

jleach commented Oct 11, 2024

If you log the ledger node cache on line 409 of Splash.tsx it appers to contain defunct nodes when tested with nmap or nc. I think the idea behind the cache is it is mean to cache the reconsiled (know to be good) nodes for a given ledger:

setStep(4)
const cachedLedgers = await loadCachedLedgers()
console.log('************** cached ledgers = ', JSON.stringify(cachedLedgers))
const ledgers = cachedLedgers ?? indyLedgers

Taking two node IPs from the output and testing them with nc shows one to be working and another to be down. If the list was reconciled then one would expect all nodes to be active.

Failed Node on sovrin:test

core git:(main) nc -zv -G 5 52.64.96.160 9702
nc: connectx to 52.64.96.160 port 9702 (tcp) failed: Operation timed out

Active Node on bcovrin:test

core git:(main) nc -zv -G 5 138.197.138.255 9702                
Connection to 138.197.138.255 port 9702 [tcp/*] succeeded!
@jleach jleach added the bug Something isn't working label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant