[Bug]: Watcher not working for files in folder root #368

Closed
opened 2026-04-24 23:06:30 +02:00 by adam · 12 comments
Owner

Originally created by @BDaddyG on GitHub (May 20, 2022).

Describe the issue

Since updating to 2.0.14, books added to the library are not automatically detected, and I have to manually run Scan to detect them.

I'm guessing the issue is with my setup, as 2.0.14 has been out for a number of days and no one else has reported it.

What can I do to help troubleshoot the issue?

Thanks

Running docker on UnRAID.

Steps to reproduce the issue

  1. Add files to the watched directory.

Audiobookshelf version

2.0.14

How are you running audiobookshelf?

Docker

Originally created by @BDaddyG on GitHub (May 20, 2022). ### Describe the issue Since updating to 2.0.14, books added to the library are not automatically detected, and I have to manually run Scan to detect them. I'm guessing the issue is with my setup, as 2.0.14 has been out for a number of days and no one else has reported it. What can I do to help troubleshoot the issue? Thanks Running docker on UnRAID. ### Steps to reproduce the issue 1. Add files to the watched directory. ### Audiobookshelf version 2.0.14 ### How are you running audiobookshelf? Docker
adam added the bug label 2026-04-24 23:06:30 +02:00
adam closed this issue 2026-04-24 23:06:30 +02:00
Author
Owner

@advplyr commented on GitHub (May 22, 2022):

Is the volume you are mapping a networked file system?

@advplyr commented on GitHub (May 22, 2022): Is the volume you are mapping a networked file system?
Author
Owner

@BDaddyG commented on GitHub (May 22, 2022):

No.

Running as a docker on unRAID with:

container path: /audiobooks mapped to /mnt/user/Media/Audiobooks/ (which is local to the unRAID server)

@BDaddyG commented on GitHub (May 22, 2022): No. Running as a docker on unRAID with: container path: /audiobooks mapped to /mnt/user/Media/Audiobooks/ (which is local to the unRAID server)
Author
Owner

@advplyr commented on GitHub (May 22, 2022):

Are you putting files directly into the library folder? Or inside a subdirectory?

If you view the docker logs when you start the server are you able to see logs in the first 20 - 30 lines saying that the Watcher was initialized?

@advplyr commented on GitHub (May 22, 2022): Are you putting files directly into the library folder? Or inside a subdirectory? If you view the docker logs when you start the server are you able to see logs in the first 20 - 30 lines saying that the Watcher was initialized?
Author
Owner

@BDaddyG commented on GitHub (May 22, 2022):

putting files directly into the libary folder with the path of: Author/Book/

Here is the log entries (yes, watcher is being initialized)

Config /config /metadata
[2022-05-22T21:27:01.740Z] INFO: === Starting Server ===
[2022-05-22T21:27:01.741Z] INFO: [Server] Init v2.0.15
Config /config /metadata
[2022-05-22T21:27:01.740Z] INFO: === Starting Server ===
[2022-05-22T21:27:01.741Z] INFO: [Server] Init v2.0.15
[2022-05-22T21:27:02.058Z] INFO: [DB] 3 Users Loaded
[2022-05-22T21:27:02.065Z] INFO: [DB] 2 Collections Loaded
[2022-05-22T21:27:02.067Z] INFO: [DB] 1 Libraries Loaded
[2022-05-22T21:27:02.074Z] INFO: [DB] 577 Series Loaded
[2022-05-22T21:27:02.081Z] INFO: [DB] 596 Authors Loaded
[2022-05-22T21:27:03.502Z] INFO: [DB] 1737 Library Items Loaded
[2022-05-22T21:27:03.740Z] INFO: [Server] Purged 12 unused library item metadata
[2022-05-22T21:27:03.743Z] INFO: [BackupManager] 0 Backups Found
[2022-05-22T21:27:03.743Z] INFO: [BackupManager] Auto Backups are disabled
[2022-05-22T21:27:03.748Z] INFO: [LogManager] Removed daily log: 2022-05-13.txt
[2022-05-22T21:27:03.749Z] INFO: [LogManager] Removed daily log: 2022-05-14.txt
[2022-05-22T21:27:03.751Z] INFO: [LogManager] Init current daily log filename: 2022-05-22.txt
[2022-05-22T21:27:03.757Z] INFO: [Watcher] Initializing watcher for "Main".
[2022-05-22T21:27:03.779Z] INFO: Listening on http://0.0.0.0:80
[2022-05-22T21:27:08.311Z] INFO: [Server] Socket Connected LcLSGMKXEPnNvsbYAAAB
[2022-05-22T21:27:08.311Z] INFO: [Server] Socket Connected LcLSGMKXEPnNvsbYAAAB

@BDaddyG commented on GitHub (May 22, 2022): putting files directly into the libary folder with the path of: Author/Book/<book files> Here is the log entries (yes, watcher is being initialized) Config /config /metadata [2022-05-22T21:27:01.740Z] INFO: === Starting Server === [2022-05-22T21:27:01.741Z] INFO: [Server] Init v2.0.15 Config /config /metadata [2022-05-22T21:27:01.740Z] INFO: === Starting Server === [2022-05-22T21:27:01.741Z] INFO: [Server] Init v2.0.15 [2022-05-22T21:27:02.058Z] INFO: [DB] 3 Users Loaded [2022-05-22T21:27:02.065Z] INFO: [DB] 2 Collections Loaded [2022-05-22T21:27:02.067Z] INFO: [DB] 1 Libraries Loaded [2022-05-22T21:27:02.074Z] INFO: [DB] 577 Series Loaded [2022-05-22T21:27:02.081Z] INFO: [DB] 596 Authors Loaded [2022-05-22T21:27:03.502Z] INFO: [DB] 1737 Library Items Loaded [2022-05-22T21:27:03.740Z] INFO: [Server] Purged 12 unused library item metadata [2022-05-22T21:27:03.743Z] INFO: [BackupManager] 0 Backups Found [2022-05-22T21:27:03.743Z] INFO: [BackupManager] Auto Backups are disabled [2022-05-22T21:27:03.748Z] INFO: [LogManager] Removed daily log: 2022-05-13.txt [2022-05-22T21:27:03.749Z] INFO: [LogManager] Removed daily log: 2022-05-14.txt [2022-05-22T21:27:03.751Z] INFO: [LogManager] Init current daily log filename: 2022-05-22.txt [2022-05-22T21:27:03.757Z] INFO: [Watcher] Initializing watcher for "Main". [2022-05-22T21:27:03.779Z] INFO: Listening on http://0.0.0.0:80 [2022-05-22T21:27:08.311Z] INFO: [Server] Socket Connected LcLSGMKXEPnNvsbYAAAB [2022-05-22T21:27:08.311Z] INFO: [Server] Socket Connected LcLSGMKXEPnNvsbYAAAB
Author
Owner

@advplyr commented on GitHub (May 22, 2022):

It was only recently added to allow files directly in the library folder. The Watcher isn't able to pick these up yet, I'll try to get this updated in the next release.

@advplyr commented on GitHub (May 22, 2022): It was only recently added to allow files directly in the library folder. The Watcher isn't able to pick these up yet, I'll try to get this updated in the next release.
Author
Owner

@BDaddyG commented on GitHub (May 22, 2022):

Was there a change in v2.0.14? As Watcher was able to notice the new books being added prior to v2.0.14..

@BDaddyG commented on GitHub (May 22, 2022): Was there a change in v2.0.14? As Watcher was able to notice the new books being added prior to v2.0.14..
Author
Owner

@advplyr commented on GitHub (May 22, 2022):

I misunderstood, you are not putting files directly into the library folder.
In your logs you shared I can see the watcher started initializing, but did it ever finish? Is there another watcher log below saying it finished initializing?
Also, roughly how many folders do you have inside the Main library.

@advplyr commented on GitHub (May 22, 2022): I misunderstood, you are not putting files directly into the library folder. In your logs you shared I can see the watcher started initializing, but did it ever finish? Is there another watcher log below saying it finished initializing? Also, roughly how many folders do you have inside the Main library.
Author
Owner

@BDaddyG commented on GitHub (May 23, 2022):

Searching the log I only find the watcher initializing, I don't see it finishing. I restarted the docker and after 15 minutes I still don't see a finished message.

Currently, there are about 2,600 folders (Authors -> Series (if there is one) -> Book)

@BDaddyG commented on GitHub (May 23, 2022): Searching the log I only find the watcher initializing, I don't see it finishing. I restarted the docker and after 15 minutes I still don't see a finished message. Currently, there are about 2,600 folders (Authors -> Series (if there is one) -> Book)
Author
Owner

@advplyr commented on GitHub (May 23, 2022):

This may be related to the bug I found in the watcher library: https://github.com/fabiospampinato/watcher/issues/8

@advplyr commented on GitHub (May 23, 2022): This may be related to the bug I found in the watcher library: https://github.com/fabiospampinato/watcher/issues/8
Author
Owner

@BDaddyG commented on GitHub (May 23, 2022):

OK. Maybe the new activity on your ticket will help with movement on the issue you opened with the watcher library.

Unless you can think of something else, I guess that I'll have to wait for the watcher library to be updated, and will continue to do manual library scans.

Thanks for taking a look.

@BDaddyG commented on GitHub (May 23, 2022): OK. Maybe the new activity on your ticket will help with movement on the issue you opened with the watcher library. Unless you can think of something else, I guess that I'll have to wait for the watcher library to be updated, and will continue to do manual library scans. Thanks for taking a look.
Author
Owner

@advplyr commented on GitHub (May 25, 2022):

Fixed the watcher issue that wasn't actually your issue in v2.0.16

@advplyr commented on GitHub (May 25, 2022): Fixed the watcher issue that wasn't actually your issue in [v2.0.16](https://github.com/advplyr/audiobookshelf/releases/tag/v2.0.16)
Author
Owner

@advplyr commented on GitHub (May 29, 2022):

Your underlying issue should now be fixed in v2.0.18

@advplyr commented on GitHub (May 29, 2022): Your underlying issue should now be fixed in [v2.0.18](https://github.com/advplyr/audiobookshelf/releases/tag/v2.0.18)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#368