jpillora / jpillora/node-torrent-cloud
Loaded torrents disappear after restarting container
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 185
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Description
In the log of cloud-torrent inside the container I see:
/ # cloud-torrent -l
2018/06/06 17:05:37 Loaded new search providers
2018/06/06 17:05:38 couldn't open piece completion db in "/downloads": timeout
2018/06/06 17:05:38 initial configure failed: listen tcp 0.0.0.0:50007: bind: address already in use
Please help me, I wanna use this as my main torrent downloader.
Thanks a lot.
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
Start by reproducing the restart in the cloud-torrent container and review the startup log, especially the piece completion database error for /downloads and the port 50007 bind failure. Determine whether the loaded torrents and their completion state survive a container restart; done means the service starts cleanly and previously loaded torrents remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100