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

issue with greenlight node connecting to something #564

Closed
imaginator opened this issue Jan 17, 2025 · 2 comments
Closed

issue with greenlight node connecting to something #564

imaginator opened this issue Jan 17, 2025 · 2 comments

Comments

@imaginator
Copy link

imaginator commented Jan 17, 2025

As mentioned in breez/breez-sdk-greenlight#1158, we see errors connecting via the breez SDK that looks like a greenlight issue.

https://gist.github.com/imaginator/bf504ca536d5b3e8f7685f94e8be3e87 is a full log where it looks like the greenlight node is having issues connecting to a plugin.

Received log [ INFO ]:  node-logs: UNUSUAL plugin-gl-plugin-internal: JSON-RPC interface not yet available. Delaying 50ms. IoError(Os { code: 2, kind: NotFound, message: \"No such file or directory\" })

Please let me know what other info I can send to help debug.

@imaginator
Copy link
Author

Update: it appears that this JSON-RPC interface not yet available every 50ms warning has resolved and we are now able to create invoices again.

I'd still be curious to understand where this error was coming from though, especially as we get closer to rolling our service out to users.

@cdecker
Copy link
Collaborator

cdecker commented Jan 20, 2025

@imaginator the root cause for this issue is that the node ended up being scheduled in a host that was already under heavy load. This means that startup can take considerable time, exceeding the 10s we allow for startup. RPC calls are held for up to those 10s, but let through if the timeout expires, which then results in the JSON-RPC socket file not having been created yet due to the slow startup.

It's a pure server side issue, and we need to solve for it on the servers. I saw your report, and it caused me to add a bunch of capacity to our servers, but I must've forgotten to add a comment here. Apologies 🙏

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

No branches or pull requests

2 participants