mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
System.NullReferenceException raised during library scan #660
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#660
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @YanzheL on GitHub (May 1, 2019).
Describe the bug
I use the Official Jellyfin docker image with docker compose.
The server can be reached via hostname:8096 without problem.
During the library scan process, no matter how long I wait, the progress bar just sticks at 86.4%. Only one TV series was shown on the homepage.
The output of
docker-compose logs -fshows:It seems like network errors caused the
System.NullReferenceException.However, I can still see some new images show up on home page, which means that the container itself can reach the internet.
I changed the network option in
docker-compose.ymlfromto
Then this issue was solved. Library scanning works fine and finishes in time as expected. New images show up normally.
To Reproduce
docker-compose.ymlas shown.You can omit the
environmentanddevicessection because it is related tonvidia-dockersupport.docker-compose up -d --buildI cleaned all contents in
cachedirectory before starting the containerReplace existing images.docker-compose logs -f.Expected behavior
Finish the library scan normally.
Logs
Log.txt
Screenshots
System (please complete the following information):
Additional context
I also tried to build the docker image byself according to Offical Documentation with the current master head
61d7bed181But it still shows the same error.
@stale[bot] commented on GitHub (Jul 29, 2019):
Issues go stale after 60d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 7d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.
@icofans commented on GitHub (Sep 14, 2019):
I meet this problem in Debian9, library scan Stuck in 86%,it looks doesn't work,I just can look many logs like: