Jump to content

Longer Library Scans than normal on upgrade to v4


bigverm23

Recommended Posts

bigverm23

so I ensured I have the Chapter Image Extraction option off, ran the scan after upgrading yesterday and its been at 89% for close to 24 hours.

 

Is there something else I should be looking for in the settings?

Link to comment
Share on other sites

PenkethBoy

did you turn off both options - i.e the one while a library scan takes place?

 

and did it for all libraries?

 

other than that just be patient - it does take a long time to upgrade - hence the release notes warning

 

89% is not that its stuck it updates very slowly as it works through each file in you library - and will depend on the size of your library

 

Look for ffmpeg processes - if you see them then things are still working - a low power server will take proportionally longer to complete

 

Once complete you next scan will be back to normal or quicker than before

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...
bigverm23

this is still not working if anyone is interested, although I have it working fine on the same host machine.

 

Running latest version of Docker-Compose, using Traefik with Let's Encrypt as reverse proxy to emby.domain.com - this setup although reachable never fully populates the media library, and does not fetch metadata

 

Running latest version of Ubuntu 18.04 - same host as that of the above docker set this Emby runs just fine.

 

 emby:
    image: emby/embyserver:latest
    container_name: emby
    volumes:
      - ${USERDIR}/docker/emby:/config
      - ${USERDIR}/Downloads1/completed:/downloads/completed
      - ${USERDIR}/media/movies:/movies
      - "/etc/localtime:/etc/localtime:ro"
      - ${USERDIR}/docker/shared:/shared
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
    ports:
      - "8097:8096"
      - "8921:8920"
    restart: always
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - GIDLIST=44
    networks:
      - traefik_proxy

Edited by bigverm23
Link to comment
Share on other sites

bigverm23

4.0.2 does not resolve the issue, this seems to be an issue specifically related to docker and reverse proxy.

 

I am able to reverse proxy my non-docker Emby version without issue....something with the docker setup.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...