-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Synlogy DS220j - Snapshots from different watches are getting mixed up #2885
Comments
which model synology exactly? whats the hardware? |
It's the DS220j: CPU: Realtek RTD1296 4-core 1.4 GHz It's not running anything aside from the base synology NAS features and changedetection.io, so the Synology shows only about half of the memory used, with CPU cycles to spare - but it's excruciatingly slow. |
hmm the usage of chrome browsers is very very very tough on a machine if it doesnt have much grunt |
what about memory usage? can you check? is it using any swap memory? |
I'm not using Chrome, just the plain crawler - the Synology would crash completely if I was running Chrome. Memory usage isn't crazy - about 50% is utilised, and it doesn't swap (or just a few KB now and then). Caveat: I only have a few hours of data as I had to reboot it after trying to batch-rerun a few watches yesterday evening, which seemed to have taken down the changedetection.io Docker container - it won't try to crawl until later today.) |
any chance you can add some logs in .zip format here? |
or better if its possible - to add your backup 'zip' file here if theres nothing important in your data |
Describe the bug
Different snapshots are sometimes written to a different "watch", or even get "merged" into a different watch for a different domain, creating baffling results. This (seems to) coincide with one of the websites suddenly reporting an empty snapshot. It does not always affect the same pages.
It happens often (once every other day across ~100 websites being checked once a day).
Version
v0.48.01
How did you install?
Docker
To Reproduce
Not happening reliably, retrying use
Steps to reproduce the behavior:
Example watches:
(This specific pair of watches hasn't had the issue before.)
Expected behavior
I expect the snapshots to stay distinct
Screenshots
n/a
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The app is running on a very underpowered Synology (500 MB memory), not sure that has an impact. I'm watching ~100 pages across a dozen domains. As far as I have observed, the problem occurs across different domains. It does not impact the same pages or domains every time.
The text was updated successfully, but these errors were encountered: