Open arkaeins opened 4 days ago
Please check the logs in config/logs and see if there is anything in there. Some systems might have too many folders and not enough ionotify limit or some systems aren't supported at the OS level.
Internal buffer has been overflown multiple times in past 10 minutes. Suspending file watching for an hour. Restart count: 2 Too many restarts occured, you either have limited inotify or an OS constraint. Kavita will turn off folder watching to prevent high utilization of resources Folder watching is disabled at the server level, thus ignoring any requests to create folder watching
There seems to be a problem when adding more than two libraries while the Folder Watching feature is enabled. Is there a way to turn it back on if Folder Watching is disabled at the server level?
What Kavita is telling you is that you don't have the appropriate amount of inotify bandwidth to handle the changes, so the folder watching restarts and after 2 restarts turns off at the server level.
This can be due to having a large collection of files/folders or just not enough inotify handlers. You can adjust the limit, documented on our wiki.
You need to solve the issue before you turn if back on, otherwise Kavita will turn it back off when it hits this issue again.
I use folder watcher exclusively on my large library with no issues.
What happened?
The folder watching feature in the settings won't turn on. Even when I press the button to enable it, when I refresh the settings page or navigate to another page and return, the feature is turned off again. kavita20241031.log
What did you expect?
Foalder watching feature turn on
Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.
0.8.3 - Stable
What operating system is Kavita being hosted from?
Synology Docker
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Edge, Firefox
If the issue is being seen on Mobile, what OS are you running where you see the issue?
None
If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?
No response
Relevant log output
No response
Additional Notes
No response