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] Automatic Library Scanning stopped working #5850

Closed
1 of 3 tasks
vmirage opened this issue Dec 19, 2023 · 7 comments · Fixed by #5951
Closed
1 of 3 tasks

[BUG] Automatic Library Scanning stopped working #5850

vmirage opened this issue Dec 19, 2023 · 7 comments · Fixed by #5951

Comments

@vmirage
Copy link

vmirage commented Dec 19, 2023

The bug

Automatic Library Scanning seems to have stopped working since v1.91

The OS that Immich Server is running on

Debian

Version of Immich Server

v1.91.3

Version of Immich Mobile App

v1.91.3

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: ["start.sh", "immich"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /mnt/photo:/mnt/photo:ro
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - 2283:3001
    depends_on:
      - redis
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    extends:
      file: hwaccel.yml
      service: hwaccel
    command: ["start.sh", "microservices"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /mnt/photo:/mnt/photo:ro
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    depends_on:
      - redis
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

  database:
    container_name: immich_postgres
    image: tensorchord/pgvecto-rs:pg14-v0.1.11
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

volumes:
  pgdata:
  model-cache:

Your .env content

UPLOAD_LOCATION=./library
IMMICH_VERSION=release
DB_PASSWORD=postgres
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
IMMICH_REDIS_HOSTNAME=immich_redis

Reproduction steps

1. Ensure External Libary is already setup with the correct import path for user.
2. Copy some new photos into external library.
3. Go to Administration -> Settings -> Library -> Scanning
4. Enable automatic library scanning
5. Set cron expression to */15 * * * *
6. Save Settings.
6. Wait for 15 minutes, but no photos imported.

Additional information

No response

@johndoe0815
Copy link

I confirm, automatic scanning does nothing at all.

@frascu
Copy link

frascu commented Dec 21, 2023

Waiting for the fix of this issue, I created a python script that uses the immich api to scan every external library.
I put the script in the linux cron to execute every X minutes/hours.
https://github.com/frascu/immich-scan-library

@nortuzar
Copy link

Same here, it was working until a few versions, i didn't change anything. In my case is an external library

@lilws
Copy link

lilws commented Jan 5, 2024

So this is fix on 1.91.4 yet? I tried to trigger it with cron every hour but it seems not working.

@smeingast
Copy link

So this is fix on 1.91.4 yet? I tried to trigger it with cron every hour but it seems not working.

I have the same problem and do not see the related PRs included in 1.91.4.

@frascu
Copy link

frascu commented Jan 5, 2024

The 1.91.4 has been released on 19 Dec, while the pull request #5951 has been merged on 23 Dec.
Therefore we have to wait the next version for the fix.

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

Successfully merging a pull request may close this issue.

7 participants
@vmirage @smeingast @frascu @lilws @nortuzar @johndoe0815 and others