Closed david85091 closed 5 months ago
go to settings and enable watcher or is it enabled?
it is enabled. I restarted the service and rebooted the server. also this is a windows server 2022. wondering if that makes a difference. with all the updates.
Hi, is the library that is not getting watched on local storage (i.e. a local disk drive), or on extrernal storage (a network drive or file system)?
local file system local on machine drive i tried a network drive and that didnt matter. right now its set for a mapped letter network drive not a unc fp production Config C:\Audiobookshelf\config C:\Audiobookshelf\metadata [2024-05-28 10:28:30.645] INFO: === Starting Server === [2024-05-28 10:28:30.650] INFO: [Server] Init v2.9.0 [2024-05-28 10:28:30.652] INFO: [Database] Initializing db at "C:\Audiobookshelf\config\absdatabase.sqlite" [2024-05-28 10:28:30.686] INFO: [Database] Db connection was successful [2024-05-28 10:28:30.749] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider [2024-05-28 10:28:30.772] INFO: [LogManager] Init current daily log filename: 2024-05-28.txt [2024-05-28 10:28:30.783] INFO: [BackupManager] 0 Backups Found [2024-05-28 10:28:30.784] INFO: [BackupManager] Auto Backups are disabled [2024-05-28 10:28:31.536] INFO: [BinaryManager] Found valid binary ffmpeg at C:\Audiobookshelf\ffmpeg.exe [2024-05-28 10:28:31.536] INFO: [BinaryManager] Updating process.env.FFMPEG_PATH [2024-05-28 10:28:31.865] INFO: [BinaryManager] Found valid binary ffprobe at C:\Audiobookshelf\ffprobe.exe [2024-05-28 10:28:31.865] INFO: [BinaryManager] Updating process.env.FFPROBE_PATH [2024-05-28 10:28:31.865] INFO: [Watcher] Initializing watcher for "Audio Books". Warning: connect.session() MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process. [2024-05-28 10:28:31.870] INFO: Listening on port :11111 [2024-05-28 10:28:31.960] INFO: [Watcher] "Audio Books" Ready [2024-05-28 10:28:35.024] INFO: [SocketAuthority] Socket Connected xxxxxxxxxxxxxxxx [2024-05-28 10:29:02.891] INFO: [SocketAuthority] Socket ixxxxxxxxxxxxxxxxx disconnected from client "dxxxx" after 27867ms (Reason: transport close)
That Warning Looks Interesting!
The reason I was asking because the file system watcher will not work for network mapped drives.
If you can put your library on a local drive, the watcher should be working (you will still need to initially perform an initial library scan though, because the watcher will only start after the library is created).
The warning is normal, you can ignore it.
its kind of a hassle to move them back. i loose all the metadata to the books. what a pain to reset. maybe this can get fixed in another release. i think i may just keep pushing scan when i upload an audiobook. which is all i am using it for right now. i use calibre-web for books. but i like the way this does audiobooks better. it doesnt have good options for metadata for some books. and i dont see any way to have the program get the covers for non published books. like pdf. but i do like this program. and cant wait to see what it becomes.
You still have the option to set up an automatic library scan every x minutes/hours.
I understand the need for a tool that automatically migrates a library and its metadata from one location to another. It was actually one of the first bugs opened for windows version, since there are users who would like to migrate their old Docker Windows installation to this native installation, but are currently unable to do it without re-scanning.
I'm going to work on that tool soon.
good idea didnt think about autoscan
watcher not seeing new audiobooks when uploaded. if i go to settings libraries and scan it will see it then.