New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watchdog ocassionally stops reacting to changes on filesystems #3
Comments
@pulpul-s Has this solution been adequate for you for the past few months? I'm running my Jellyfin scans every 15 mins but this seems like a better solution, though I do not want to tinker around much. If setting this as a service with auto restart has been flawless for the past few months I think I'd bite the bullet. |
Yes. I have been running it as once a day restarting service for quite some time now and have not observed any times that the library would not update like it is supposed to. |
The python script takes quite a while for it to fully boot up for me and I'm not sure why. It also never seems to start with systemd. This is my config:
I'm running this on an ubuntu 22.04 install that just has docker, and a jellyfin container. |
Try to make sure you don't have any problems with the configuration options in the start of the script. Also try to run it normally without it being a service first to check that it works like it is supposed to. You can just try to create files to the watched filesystem with: This is the systemd service I'm using currently:
|
After running the script for longer times e.g. three days, watchdog does not react to filesystem changes anymore. This seems like an issue with the watchdog library itself rather than a problem with watchertoucher.
At the moment the only reasonable fix is to run the script as a systemd service and have it restart every 24 hours. This does not cause any downtime.
Any help on the issue is appreciated, since I have been unable to fix it completely.
The text was updated successfully, but these errors were encountered: