Emby server no scan o reset scan

[HombreCojin 1]

Hello, I have an Emby server on Ubuntu 22.04 running with Docker (the file I’m attaching) working perfectly.

A friend wanted to set up his server, and to avoid scanning everything from scratch, since we share content, I compressed my Emby directory into a tar.gz and shared it with him, setting it up exactly the same way as I did and following these instructions:

• Install Emby with Docker (file attached).

• Decompress and copy the contents of the tar, deleting files like user, mc, etc., beforehand.

• Apply these two commands to set the correct permissions:

sudo chown -R root:root /var/lib/docker/volumes/home_emby1-config

sudo chmod -R 777 /var/lib/docker/volumes/home_embyserver(3)(2).txtdocker-compose(1).yamlStart(1).txtemby1-config

 

He claimed the server, and all the content appears and plays perfectly. The first scan took a long time (I think it applied ffprobe to all the files).

Once the first scan, which took about a week, was completed, he tried to scan again, but either the scan doesn’t run at all, or it’s extremely slow.

Do you know how this issue could be resolved and whether it’s a permissions problem or a misconfiguration?

 

I use this backup in tar in other server and work well

 

 

 

[Luke 42077]

Hi, please attach the emby server log from when you ran the library scan:

How to Report a Problem

You may (or may not) see better scan performance by:

• Removing the auto collections plugin
• Disabling the realtime monitor on each library

With a log covering a larger period of time we may be able to find more suggestions. Thanks.

[HombreCojin 1]

Thx for info , i agree emby log embyserver.txt

[Luke 42077]

@HombreCojindid you try what I suggested?

[HombreCojin 1]

@Lukethanks foy ur time¡¡¡

I have used the backup to set up another server with the same processor and features in case the .tar.gz was corrupt. The second server scanned the first scan relatively quickly and the consecutive ones in a matter of seconds since there were no changes.

 

The first server continues to have problems, despite receiving two complete scans every time I put it to scan, it takes a long time to start and continues with a relatively low %. I have disabled what you told me and there seems to be no improvement, I have attached a log from the last reboot. It remains at 3.6% and the % that is scanned from any of them does not appear in libraries

embyserver(2).txt

[Luke 42077]

So is the only problem the length of time on the scan? 

[HombreCojin 1]

Hace 14 horas, Lucas dijo:

Entonces, ¿es el único problema el tiempo en el escaneo? 

Yes, it's curious because I have kept both servers updated at the same time for testing. Once the days had passed, both scanned quickly and everything was ok, but today one of them scanned quickly or the other once again had an excessively sloembyserver(3).txtw scan. I think it may be some problem with ffmpeg, I attached log

[Luke 42077]

On 1/24/2025 at 5:04 AM, HombreCojin said:

Yes, it's curious because I have kept both servers updated at the same time for testing. Once the days had passed, both scanned quickly and everything was ok, but today one of them scanned quickly or the other once again had an excessively sloembyserver(3).txtw scan. I think it may be some problem with ffmpeg, I attached log

@HombreCojinthe scan in this log started at 06:57, and then the log file ends 8 minutes later. Are you sure this is the right log file?