library scan takes a long, long, long time

[Guest]

Hello,

quick and precise: my library scans runs since, i think tuesday.

im at (API value) 91.267870036101 Percent and yesterday it was at 89%.

As it seems, this seems to take till monday? Is there any way to make it faster?
My media library is quite big, (im a collector)

 

but while scanning, i cant watch anything

 

thanks for your help

[Guest]

Update: Ive started the library scan on the individual libraries, and it seemed to trigger an update, some items came into the library, but are not visible (got the update via notification)

Not it seemed to stop the update again...

[Luke 42078]

Please see how to report a problem:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

Thanks !

[Guest]

Please see how to report a problem:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

Thanks !

I cant give any log files at the moment, as there are none.

 

I will give logs when they are available

 

I run the docker container (not official image, my own)

I can generate logs BUT that would mean to restart to fix the container, but that would also interrupt the library scan, wouldnt it?...

Edited August 17, 2018 by cyberplay

[Luke 42078]

There is always an emby server log if you are running emby server.

[Guest]

There is always an emby server log if you are running emby server.

Ahhh... thats the problem.

 

Okay, the problem is, when i restart emby server from the web interface, the process gets killed, s6 in the container recognizes this and restarts it immediatly, before emby can restart it self.

when this happens, emby writes constantly to log "hey, i cant start, theres already a process running??" which is true, the log file is "occupied" by the emby process which would like to start, but cant.

The "workaround" for this issue is to restart the container, problem is, i cannot restart the container yet, as it would abrupt the library scan. and i dont want to wait 4 - 6 days again.

[Luke 42078]

Try using our official docker image for a better restart experience.

[Guest]

Got it the wrong way around:

emby successfully restarts itself, but s6 is constantly trying to start it.
As i want emby to be controlled by s6, is there a possibility to "disable" the restart button?

In the past there was only the "shutdown" button, can i have this again somehow?

 

I dont use the official image because im using my own image a long time and except this issue, i have no issues with it.

 

So my final question is now:

Can i disable the "restart" function in emby itself? In the past it was like this in docker containers.

[Luke 42078]

There's no way to disable the restart button.

[Guest]

There's no way to disable the restart button.

I just restarted the container now and restarted the library scan, now its controlled by s6 and i can provide logs for the issue in a short time.

 

EDIT: it didnt started on 0%, it started at 88.5%, so my theory is, pls @@Luke confirm if this is correct:

- The first full scan scans the entire library, from 0% to 100%

- If it gets interrupted, the scan continues at the position which it "remembers"

- If full first scan is completed, scanning takes a much shorter time, as it built a cache.

 

EDIT 2:

Also its actually possible to "deactivate" the restart button. Ive did this with a simple CSS trick:

Under custom css, add this:

#btnRestartServer {
display: none;
}

That removes it at least for me, to not accidentally click on it.

Edited August 17, 2018 by cyberplay