-
Notifications
You must be signed in to change notification settings - Fork 44
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
WUD_WATCHER_LOCAL_CRON Config Help/Question #437
Comments
Hi, At startup, the cron value is printed; is the parsed value correct? May you try to enclose the env var with quotes?
|
I see the following int he logs: |
You are providing a timezone via environment variable and by mounting your servers timezone into the container. Any chance those two are different? Maybe that could cause weird behavior? I'd remove one of those regardless. |
They are not different, but I have removed the volume mount for timezone and will see if it makes any difference. |
Removing the volume mount made no difference. WUD ran at midnight last night which is the same time a script kicks off that runs the plextraktsync container. The container ran for about 3 mins. It appears that every time a new container comes on line, goes offline, or is removed, WUD is performing a new scan and ignoring the cron schedule. The WUD log below shows it knows what time it is supposed to run, but seems to have ignored the schedule and ran anyway.
|
That's likely because of the |
That seems to have made an impact. When A few suggestions (take them or leave them) I have would be as follows:
Another possibility could be to add a WATCHEVENTS to each registry type so it could be controlled by registry, but that seems a bit more complex to implement. In that scenario each event would have to be processed, determine which registry the event belongs to, see if the it is set to true or false, and then scan or not based on _WATCHEVENTS. One last question, I noticed that the logs only contain the time and not the date. I am not seeing anything in the docs about configuring the content of a log message to be able to include the date. Am I missing something or is date just not added to the logs by design? |
I believe I have WUD configured correctly yo run each day at 1:00 AM, but it is running multiple times a day. It has been up 2 days and has run 122 times instead of 2. Hoping someone can help point me to what I am missing in the config.
Docker compose for WUD
docker ps -a --filter "name=whatsupdocker"
docker logs whatsupdocker 2>&1 | grep 'Cron finished'
The text was updated successfully, but these errors were encountered: