lightninglabs / lightninglabs/loop

Standalone Loop+Pool 'unable to start server: unable to open macaroon db: timeout'

Open
#624 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
595
Forks
135
Avg merge
1d 8h
Merged PRs (30d)
12

Description

Searching for duplicates of this error yielded no results in Slack, telegram, github, etc. Bosworth suggested to open an issue, and I'm not really sure what it's telling me

'unable to start server: unable to open macaroon db: timeout'

Standalone Loop or Pool will succesfully start and run as expected when using one or the other, but starting both causes both to fail. The error itself appears on either Loop or Pool, dependent on which started first. Not sure if it's a config issue or what- to which any help would be appreciated on saving hours of trial and error

Attached are relevant configs & logs, with some information redacted. LND itself doesn't seem to spit out anything too interesting, but can pull those too if requested

[loop-logs_issue12.txt](https://github.com/lightninglabs/loop/files/12327929/loop-logs_issue12.txt)
[pool-logs_issue12.txt](https://github.com/lightninglabs/loop/files/12327930/pool-logs_issue12.txt)
[config_issue12.txt](https://github.com/lightninglabs/loop/files/12327931/config_issue12.txt)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the attached loop-logs_issue12.txt, pool-logs_issue12.txt, and config_issue12.txt, comparing startup when Loop and Pool run separately versus together. Reproduce the macaroon database timeout with the supplied configuration and trace which service fails first. Done means identifying the cause and documenting or fixing the configuration or startup behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.