LBRY slow at starting - "Error at starting up" but starts up anyway
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
I get this when starting LBRY.
My LBRY dir is on a NAS, contains 1.5 TB, 40000 blobfiles, 5000 mp4-files, so if LBRY has to stat every single file when starting, that will explain why it is slow.
$ lbrynet version
{
"build": "release",
"desktop": "KDE",
"distro": {
"codename": "focal",
"id": "ubuntu",
"like": "debian",
"version": "20.04",
"version_parts": {
"build_number": "",
"major": "20",
"minor": "04"
}
},
"lbrynet_version": "0.106.0",
"os_release": "5.4.0-96-generic",
"os_system": "Linux",
"platform": "Linux-5.4.0-96-generic-x86_64-with-debian-bullseye-sid",
"processor": "x86_64",
"python_version": "3.7.12",
"version": "0.106.0"
}
Contributor guide
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
Reproduce the startup delay with the NAS-backed LBRY directory using the lbrynet entry point and the reported 1.5 TB dataset. Trace the startup path that emits “Error at starting up,” checking whether it examines the listed blobfiles and MP4 files; done means startup completes without the misleading error and the observed delay has a confirmed cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100