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] create-library and update-library do not work - resultant library.ydb is empty #60

Open
Chlorus opened this issue Feb 8, 2024 · 6 comments

Comments

@Chlorus
Copy link

Chlorus commented Feb 8, 2024

When running the create-library or update-library commands within this container, it creates a database file that is totally blank for each library. If a populated database file already exists, it will not update it after running update-library.


Expected Behavior

It should populate a .yacreaderlibrary/library.ydb file that isn't empty, or if it exists, it should update it with new entries.

Current Behavior

After running the create-library or update-library commands, the resulting .yacreaderlibrary/library.ydb file is totally empty. The cover metadata directory seems to populate as expected.

Steps to Reproduce

  1. Delete .yacreaderlibrary directory, if one exists.
  2. Run docker-compose up -d with specified docker-compose.yml
  3. Attempt to create a library for /comics/Super\ Play directory, comprised of .cbz files
  4. docker exec -it YACReaderLibraryServer YACReaderLibraryServer create-library "Super Play" /comics/Super\ Play
    Processing comics................................................Done!
    Number of comics processed = 48
  5. Attempt to display contents of library.ydb
  6. (utils) root@faramir:/home/aalles/Sources/YACReaderHeadless# docker exec -it YACReaderLibraryServer cat /comics/Super\ P
    lay/.yacreaderlibrary/library.ydb
    (no output)
  7. Attempt to connect to YACReader instance with the YACReader mobile app and import via the YACReaderLibrary connection: listed library is totally empty (see screenshot)

Screenshots

yacreader_empty
Screenshot 2024-02-08 122721
IMG_2315

Environment

OS: Ubuntu 22.04.2 LTS container, Linux faramir 4.19.0-26-amd64 #1 SMP Debian 4.19.304-1 (2024-01-09) x86_64 GNU/Linux host
CPU architecture: x86_64

Command used to create docker container (run/create/compose/screenshot)

---
version: "3"
services:
  yacreaderlibrary-server-docker:
    container_name: YACReaderLibraryServer
    image: xthursdayx/yacreaderlibrary-server-docker:latest
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Phoenix
    volumes:
      - ./config:/config
      - /mnt/Documents/Books/Gaming/Periodicals:/comics
    ports:
      - 9080:8080
    restart: unless-stopped

Docker logs

(utils) root@faramir:/home/aalles/Sources/YACReaderHeadless# docker logs YACReaderLibraryServer
[migrations] started
[migrations] no migrations found

----------------------------------------------------------
   _  __________  ____  ______  _____ ____  _____  ___  __
  | |/ /_  __/ / / / / / / __ \/ ___// __ \/   \ \/ / |/ /
  |   / / / / /_/ / / / / /_/ /\__ \/ / / / /| |\  /|   /
 /   | / / / __  / /_/ / _, _/___/ / /_/ / ___ |/ //   |
/_/|_|/_/ /_/ /_/\____/_/ |_|/____/_____/_/  |_/_//_/|_|

Brought to you by xthursdayx
----------------------------------------------------------
GID/UID
----------------------------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

[custom-init] No custom files found, skipping...
INFO  2024-02-08T12:26:20.830 YACReaderLibraryServer attempting to start
INFO  2024-02-08T12:26:20.830 ---------- System & configuration ----------
INFO  2024-02-08T12:26:20.830 OS: "Ubuntu 22.04.2 LTS" Version:  "22.04"
INFO  2024-02-08T12:26:20.830 Kernel: "linux" "4.19.0-26-amd64" Architecture: "x86_64"
INFO  2024-02-08T12:26:20.830 Libraries:  QMap(("N64 Magazine", QPair(2,"/comics/N64 Magazine")))
INFO  2024-02-08T12:26:20.830 --------------------------------------------
INFO  2024-02-08T12:26:20.830 YACReaderLibrary starting
INFO  2024-02-08T12:26:20.831 Running on "192.168.16.2:8080"

INFO  2024-02-08T12:26:20.832 "███████████████████████████████"
INFO  2024-02-08T12:26:20.832 "███████████████████████████████"
INFO  2024-02-08T12:26:20.832 "█████ ▄▄▄▄▄ █▄██▀▀█ ▄▄▄▄▄ █████"
INFO  2024-02-08T12:26:20.832 "█████ █   █ █▀▄█▀▄█ █   █ █████"
INFO  2024-02-08T12:26:20.832 "█████ █▄▄▄█ █ █ ▄ █ █▄▄▄█ █████"
INFO  2024-02-08T12:26:20.832 "█████▄▄▄▄▄▄▄█ ▀ █▄█▄▄▄▄▄▄▄█████"
INFO  2024-02-08T12:26:20.832 "█████ █▀█ ▀▄▄▄▄ █ ▄▄▄ ▄▀▀▄█████"
INFO  2024-02-08T12:26:20.832 "█████▀▄ ▀▄█▄█▀██▀ █▀██▀█ ▀█████"
INFO  2024-02-08T12:26:20.832 "█████▄███▄█▄▄ ▀▀▄▀█▄▀▀█▄  █████"
INFO  2024-02-08T12:26:20.832 "█████ ▄▄▄▄▄ █▄▀█ █▄▄   ██▄█████"
INFO  2024-02-08T12:26:20.832 "█████ █   █ █▄ ▄█ ▀ ▀█▀▄ ▀█████"
INFO  2024-02-08T12:26:20.832 "█████ █▄▄▄█ ███▄ ███ ▀▄▀█▀█████"
INFO  2024-02-08T12:26:20.832 "█████▄▄▄▄▄▄▄█▄█▄▄▄▄▄▄▄█▄▄▄█████"
INFO  2024-02-08T12:26:20.832 "███████████████████████████████"
INFO  2024-02-08T12:26:20.832 "███████████████████████████████"
[ls.io-init] done.

Additional information

If I create the libraries via the YACReaderLibrary desktop application, then everything works as expected - I can even serve them just fine with this container (but reading progress isn't saved)

@xthursdayx
Copy link
Owner

I haven't been able to reproduce this issue locally, but I have also been in the process of updating the docker image(s). Could you try pulling the updated version of the docker image, create a new container, and see if you're still having this issue?

@Chlorus
Copy link
Author

Chlorus commented Feb 27, 2024

Pulled down latest tag, removed all the .yacreaderlibrary folders, and wiped the .ini in /config/.local and the issue persists. I wonder if it has something to do with the fact that those files live on a samba mount and there's some ACL complications happening.

Copy link

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

@ubghacking
Copy link

I am also having this same exact issue. I run this in a CentOS vm hosting my docker containers, with my content hosted on my media server via an SMB share.

I can manually update from YACServerLibrary running from my Windows PC to update with new comics, however running the update-library command provided does not:

[(redacted)@ubuntu-docker (redacted)]$ docker exec YACReaderLibraryServer YACReaderLibraryServer update-library /comics
WARNING: Error loading config file: /root/.docker/config.json: read /root/.docker/config.json: is a directory
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- zip.c:104: Skipping directory entry "(redacted)/"
! _7z.c:191: 7z support requires 7z SDK (define HAVE_7Z)
- rar.c:65: Skipping directory entry "(redacted)"
- rar.c:65: Skipping directory entry "(redacted)"
- rar.c:65: Skipping directory entry "(redacted)"
Processing comics.............................Done!
Number of comics processed = 29

@ubghacking
Copy link

Been looking more into this. Looks like it's a SQLite database issue over SMB. Looks like some of the recommended fixes through the Internet also don't solve this problem. Can't find a workaround.

Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants