slow media scan

[metropical]

v10.9.7
MacOS 12.7.5
2 ext drives on LAN'd MacPro3,1
48% after 30 mins or is that normal?
~2.5T.

log - https://pastebin.com/zy3yYvYD 

[TheDreadPirate]

That is not out of the ordinary for a first time scan. Especially if you have trickplay and chapter image extraction enabled during library scans.

[metropical]

music only and now stuck at 48%.
I assume that trickplay and chapter image extraction have to do with video/film/tv.

[TheDreadPirate]

I did see a couple log entries about not being able to reach MusicBrainz. I'm wondering if you hit an API rate limit or something.

[metropical]

"I'm wondering if you hit an API rate limit or something. "
?

[TheDreadPirate]

TMDB, TVDB, and all of the online metadata sources only let users make a certain number of accesses over a period of time before they throttle how quickly you pull down data. Since your music library is so large it may take a while to fully scan.

https://musicbrainz.org/doc/MusicBrainz_...e_Limiting

Is the scan still going?

[metropical]

I stopped it as it was stuck at 48% for a day.
Judging from that link I'll try at a different time.
Is there some way I could use the Emby scan/library?

[TheDreadPirate]

Can you turn on debug logging and try initiating the scan again?

https://jellyfin.org/docs/general/admini...ug-logging

[metropical]

a bit above my pay grade. Though I am familiar with Terminal (command line for MacOS) and have used it, when I enter "--configdir", I get back "zsh: command not found: --configdir".
I'm gonna assume that this is normally a "hidden" file in the OS. Where might I find it if it exists?

---

ooo, just found it in "hidden" - .config/jellyfin/logging.default.json.
lemme see what I can figure out.

edited - .config/jellyfin/logging.default.json. as per the linked instruction, but I saw no change when I pasted it in.
closed it and am rerunning the scan.

[TheDreadPirate]

From your log.

Code:

Main: Config directory path: "/Users/fritz/.local/share/jellyfin/config"

That is where you would create the logging.json file with the content specified in the doc I linked.