Replies: 4 comments 5 replies
-
|
No specified schedule means "Run this every time PMM runs". If you want PMM to run every hour, but some collections to run less frequently, you need to schedule those less-frequent things to run during one or more of of the hourly runs. With the docker settings you have above, this will run the watchlist every hour and the mm-Filme metadata file once a day at 10. You could also do this by adding flags to that hourly run to only process the one metadata file, and then add a separate once-a-day container to run the rest of it. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Those 2 suggestions are very helpful! I just need to decide which one I like better.
Ok, I did it the other way around, guessing PMM would handle it (the way I understood the wiki)... Thank you so far, I will report which one worked out for me! (but I guess, the second container will be a more complex scenario overall) |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I did not set up a 2nd docker container, because of the extra maintenance. I want to complete my tasks in one single docker container. So I changed my config to have the long lasting tasks scheduled at 5 o clock and the short tasks every hour, as guided by your helpful words:
But I have something missing I guess, because only hourly tasks are done by PMM. 5 o clock tasks are somehow ignored. This is my the Unfortunately those all are ignored on the hourly wake ups of PMM. (PMM runs for over a week now and I can see that there are only Any Idea/Help is very much appreciated! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Do you have a log from one of these 5:00 runs which shows the problem? Also, I'm not sure I understand how setting up a second container once is somehow more maintenance than keeping track of multiple schedule lines in a single config file. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I have. Its the But I'm afraid, it shows the same info. Interestingly enough, it shows No idea, why and what this menas. I would have expected the time mentioned would be the time when PMM woke up starts the scheduled task. here you go: 5 o clock run: https://pastebin.com/raw/53xK3pWy (pastebin because github complained: You can't comment at this time — your comment is too long (maximum is 65536 characters).)
Do I not have to keep track of all the second configs? for the second container, do I not need to copy and alter all the configs? Thank you. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
You can point the second container at all the same configs. All you're changing is the runtime flags on that container. A second container does not, by itself, require a second set of configs. |
Beta Was this translation helpful? Give feedback.
-
|
Nobody any idea, why PMM is completely ignoring my schedules at 5 o clock? |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Generally support topics get quicker attention on the Discord. There are comparatively far fewer people monitoring these issues. It seems like something's off with how PMM is seeing the time: This is clearly running in the 5th hour, but PMM doesn't seem to agree. An issue that sounds very similar to this has been fixed in nightly, so you could try the nightly image. https://discord.com/channels/822460010649878528/1074957642683912232 |
Beta Was this translation helpful? Give feedback.
-
|
With installing the nightly I can now see, that the scheduler works as expected. The hourly and the five o clock tasks are running fine. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm on Unraid via Docker container and have found several posts here to help me setting up a scenario, to run my watchlist collection every hour of a day.
But I must have get something wrong, because, PMM now wakes up every hour doing the whole bunch of things defined in the configs, not only the scheduled ones.
I have only used the schedule setting in my watchlist collection, which I include this way:
config.yml:And I was under the impression "daily is the default when schedule is not specified." (from the wiki) So the scheduler will take care ONLY for the hourly scheduled parts in the config when PMM wakes up each hour. That was a wrong assumption.
This is how I configured the docker container:
My watchlist config looks good in the validator:
watchlist.logAnd it is executed fine, but because the rest of the config takes about 12 hours to finish, the watchlist is only executed every 12 hours.
How can I set up PMM to run the watchlist every hour and all the rest daily?
Beta Was this translation helpful? Give feedback.
All reactions