Scan doesn't scan entire photo's folder, and stops randomly.

[flee541]

Hi, I am looking to replace Google photos and stumbled into Photoview. I have setup Photoview via docker (Portainer Stacks) and it seems to be working. Only thing is when I hit scan, it stops a few minutes into the scan of my mounted photos drive.

I am also seeing in the logs that the Localhost is making an unauthenticated api calls? Unsure what that means.

Below is my docker compose file (or the Portainer Stack). The volumes are volumes I created in Portainer and the photo is actually an NFS mount via portainer's volume manager.

Any help would be greatly appreciated.

version: "2.1"

services:
  db:
    image: mariadb:latest
    restart: always
    network_mode: host
    environment:
      - MYSQL_DATABASE=photoview
      - MYSQL_USER=photoview
      - MYSQL_PASSWORD=photosecret
      - MYSQL_RANDOM_ROOT_PASSWORD=1
    volumes:
      - photoview_db:/var/lib/mysql

  photoview:
    image: viktorstrate/photoview:2
    restart: always
    ports:
      - "8800:80"
    depends_on:
      - db

    environment:
      - PHOTOVIEW_DATABASE_DRIVER=mysql
      - PHOTOVIEW_MYSQL_URL=photoview:photosecret@tcp(192.168.1.82)/photoview
      - PHOTOVIEW_LISTEN_IP=192.168.1.82
      - PHOTOVIEW_LISTEN_PORT=80
      - PHOTOVIEW_MEDIA_CACHE=/app/cache
      
      # Optional: If you are using Samba/CIFS-Share and experience problems with "directory not found"
      # Enable the following Godebug
      # - GODEBUG=asyncpreemptoff=1
      
      
      # Optional: To enable map related features, you need to create a mapbox token.
      # A token can be generated for free here https://account.mapbox.com/access-tokens/
      # It's a good idea to limit the scope of the token to your own domain, to prevent others from using it.
      # - MAPBOX_TOKEN=<YOUR TOKEN HERE>

    volumes:
      - photoview_data:/app/cache

      # Change This: to the directory where your photos are located on your server.
      # If the photos are located at `/home/user/photos`, then change this value
      # to the following: `/home/user/photos:/photos:ro`.
      # You can mount multiple paths, if your photos are spread across multiple directories.
      - terranas-photos:/photos:ro

volumes:
  db_data:
  api_cache:

[flee541]

I have noticed that if I restart the scan, it will go through the notion but it doesn't continue to scan. I am unsure if this is because it has scanned everything already or it's just stopping.
A suggestion would be to display some indication of progress on scan, and perhaps a message to say whether it has finished scanning all possible folders and is currently just watching for updates or something.

Also, instead of having a little pop up to indicate progress, perhaps having it on the left navigation, bottom of navigation, a progress bar or log may help understand what is happening behind the scenes?

I may stick with Photoprism for now as it is a bit more polished but I love the timeline in Photoview as it helps the family migrate from Google Photos.

Best of luck

[flee541]

I forgot to mention, running a scan hogs up the memory on my server, like up to 85%, however once the scan stops, it does not release this memory until I restart the server. Unsure if this is just me or not. I'm running this within a virtual machine (ubuntu) and docker on ubuntu.

[kanwarplaha]

This behaviour of needing a server restart is still noticed (on OpenSUSE Tumbleweed). However, even after restart, I am unable to coax photoview to scan the photos directory tree.

What else can I try? I am using postgres as the database.

[kkovaletp]

@flee541, @kanwarplaha, 1st of all, we don't support Portainer, as well as any other abstraction layers on top of Docker. Please try to recreate the Docker containers using Docker directly (by shutting down the stack in Portainer and running docker compose up -d from the folder on the server, where the compose file is located).

My 2nd advice would be to switch to the master tag for the photoview service and recreate your compose config according to the guide in the Readme, as we've merged a lot of fixes and refactored Docker setup, so there is a chance that the issue is already fixed there.

Also, I'd like to mention that the noticed unauthorized requests from localhost are generated by the photoview container's healthcheck. You could ignore them.
Finally, I don't think that this issue is related to the DB, as both of you don't use SQLite (which is still pretty limited in our project), however, I'd recommend using the LTS image of MariaDB (if you use MariaDB). PostgreSQL image doesn't provide any stable image, so you can use 16-alpine

[kanwarplaha]

@kkovaletp I didn't use portainer, just plain old docker-compose. Also, I switched back to mariadb/MySQL and it seems to be working.
Maybe something specific to postgres perhaps?

[kkovaletp]

If there are DB-related issues during the scan process, you should see the corresponding errors in the photoview log (like db connections limit exceeded, or anything else, clearly pointing to the DB). Also, the DB log might have some unexpected records at the same time.

If the log is clean from such errors, most likely it is not related to the DB.