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

[BUG] Fastresume files being ignored #307

Closed
1 task done
remy33 opened this issue May 16, 2024 · 7 comments
Closed
1 task done

[BUG] Fastresume files being ignored #307

remy33 opened this issue May 16, 2024 · 7 comments

Comments

@remy33
Copy link

remy33 commented May 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Fastresume has no impact on client, whenever container restart all the torrents do 'checking'.

After fidling this does not happened if qbittorrent is set to use "SQlite database (experimental)"

Expected Behavior

Files shouldn't be ignored and the download shall resume to be "seeding" without checking process, just like they're when enabling SQlite database.

Steps To Reproduce

  1. Have a torrent seeding.
  2. Restart container ( docker restart qbittorrent , or docker compose up -d if changed settings)
  3. See that torrent is checked.

Environment

- OS: 
Ubuntu20.04
- How docker service was installed: 
docker script from the official repository.

CPU architecture

x86-64

Docker creation

qbittorrent:
    image: lscr.io/linuxserver/qbittorrent
    container_name: qbittorrent
    environment:
      - WEBUI_PORT=XXXX
      - TORRENTING_PORT=XXXX
    volumes:
      - ./qbittorrent-config:/config
      - ./downloads:/downloads
    network_mode: service:wireguard
    restart: unless-stopped

Container logs

There is no error shown in log:

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

[custom-init] No custom files found, skipping...
QtSingleCoreApplication: listen on local socket failed, QLocalServer::listen: Unknown error 95
WebUI will be started shortly after internal preparations. Please wait...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:XXXX

Connection to localhost (::1) XXXX port [tcp/*] succeeded!
[ls.io-init] done.
Catching signal: SIGTERM
Exiting cleanly
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@remy33
Copy link
Author

remy33 commented Jun 15, 2024

If additional feedback is needed, tell me what I should add.
Maybe can we change the default container to use the experimental SQlite database?

@j0nnymoe
Copy link
Member

Try using the required ENV's from our documentation and see if that helps. No other reports of this not working.

@remy33
Copy link
Author

remy33 commented Jun 15, 2024

I tried with the default Environment from docs at first, maybe I messed up some setting? IDK since I use nearly default config.
Anyways, if no one else have it, I guess issue can be closed and if someone else will have the bug, they will know how to get around it and might contribute.

@remy33 remy33 closed this as completed Jun 15, 2024
@j0nnymoe
Copy link
Member

It could be a permissions issue, you haven't provided full volume paths and you really using be using the suggested env's for permissions etc.

Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

3 participants