lightninglabs / lightninglabs/lndmon
postgres backend - LND v0.14.1-beta "lnd compatibility check failed"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 160
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Need help understanding what's going on with my setup or if this is a bug.
Note, currently running lndmon for many nodes using the standard bbolt/boltdb backend.
For some reason it seems like I'm getting errors when using LND with postgres.
logs:
2021-12-22 02:39:55.978 [INF] LNDMON: Starting Prometheus exporter...
2021-12-22 02:39:55.978 [INF] HTLC: Starting Htlc Monitor
2021-12-22 02:39:55.979 [INF] LNDMON: Prometheus active!
Lndmon exiting with error: GraphCollector DescribeGraph failed with: rpc error: code = DeadlineExceeded desc = context deadline exceeded
2021-12-22 02:40:35.757 [INF] HTLC: Stopping Htlc Monitor
2021/12/22 02:40:35 Stopping Prometheus Exporter
GraphCollector DescribeGraph failed with: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sometimes I'll just get this for the error in the logs:
lnd compatibility check failed: unable to get info for lnd node: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce lndmon with LND v0.14.1-beta and the postgres backend, starting from the GraphCollector and compatibility-check errors in the logs; done means determining whether the timeout is caused by lndmon or the setup and documenting a confirmed fix or diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgres, prometheus
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100