![]() |
Library scanning looking for old location - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: Library scanning looking for old location (/t-library-scanning-looking-for-old-location) |
Library scanning looking for old location - Space12 - 2025-02-24 In my jellyfin server setup, the media is stored on a remote network location (different vlan, but still local gig/multi-gig connected). for the sake of this, Jellyfin ip: 192.168.1.12 - original media location 192.168.2.10\media. this has worked perfect. After a hardware upgrade, the media location moved to 192.168.2.11\media I updated the library location and everything is working, the old media host is now gone/off the network. in the jellyfin server logs, daily, I see the media scan task go out and look etc. no error no issues However, in my firewall logs within a minute of the media scan, I also see an IP "attempt" to the old IP address 1) it's blocked but more important 2) it's not there anymore. every 24 hours this happens, a good media scan and with no errors in the logs and see an attempt at nearly the same time to the old IP. I have looked everywhere and I am stuck. In the GUI there is zero mention of the old IP (192.168.2.10) the Library is only set to the new IP. Where else can I look, it feels like there is an old pointer/config that is "stuck" RE: Library scanning looking for old location - TheDreadPirate - 2025-02-24 Check playlists for the old path. Playlists use absolute paths and are not dynamically updated. RE: Library scanning looking for old location - Space12 - 2025-03-03 That did not help as well as setting deubg for logging did not show any errors. Since I really could not prove it was an app issue and not the OS, I decided to do a new VM, new app install and start over. Since then the errors have gone away. |