📝 If you want to review this again, .bugas:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
#movies.yml help
1 messages · Page 1 of 1 (latest)
Welcome @fossil basin!
It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
im having issues with seasonal collections. i have my movies.yml set up and the - file: config/Movies.yml command in the config. but it my logs keep saying its not scheduled to run?
**Rec 03** - ❌ **[ERROR]**
❌ [ERROR]
Error messages found in your attached log.
There is a very strong likelihood that Kometa did not complete all of what you wanted. Some [ERROR] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[error]#error]
10 line(s) with [ERROR] messages. Line number(s): 596, 612, 790, 806, 869, 885, 5080-5081, 5229-5230
Page 10/13
I don't see any scheduling problems in this log.
| Reading default: imdb
| Schedule: weekly(monday)
| This file not scheduled to run
|
| Reading default: tmdb
| Schedule: weekly(tuesday)
| This file not scheduled to run
|
| Reading default: letterboxd
| Schedule: weekly(wednesday)
| This file not scheduled to run
|
| Reading default: seasonal
| Template Variables: ...
|
| Reading default: separator_award
| Schedule: weekly(thursday)
| This file not scheduled to run
|
| Reading default: universe
| Schedule: weekly(friday)
| This file not scheduled to run
|
| Reading file: config/Movies.yml
Two of the files get loaded,
| Reading default: seasonal
| Reading file: config/Movies.yml
The rest don't because they aren't scheduled to run.
Then when Movies.yml gets processed, none of the collections inside it are scheduled to run, for example;
|============================ Validating Ring In The New Year Attributes ============================|
| Scheduled yearly on December 26th
|
| Collection Ring In The New Year not scheduled to run
|========================== Validating Celebrating Black Cinema Attributes ==========================|
| Scheduled yearly on February 1st
|
| Collection Celebrating Black Cinema not scheduled to run
|============================== Validating Best of Romance Attributes ===============================|
| Scheduled yearly on February 7th
|
| Collection Best of Romance not scheduled to run
...
None of the default seasonal collections are scheduled to run on 12/29, either.
What is this schedule supposed to mean?
schedule: yearly(12/26) 12/26 - 1/2
So what would be the correct configuration?
What do you want the schedule to do? A range of dates?
I just want movies.yml to run
Sure, but before I can tell you how to fix this:
schedule: yearly(12/26) 12/26 - 1/2
I have to know what you intend it to do.
Have the movies.yml create those seasonal collections
it will do so once these broken schedule lines are fixed.
So is this:
schedule: yearly(12/26) 12/26 - 1/2
intended to create the collections during that date range?
Yes
Alright I’ll try that out. Thank you very much
📝 If you want to review this again, .bugas:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Seem to be getting unkown error
| Validating Method: url_poster |
| Value: C:\Users\bugas\Kometa\config\posters\paintings\new_year.jpg |
| Traceback (most recent call last): |
| File "C:\Users\bugas\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\tenacity\__init__.py", line 478, in __call__ |
...
| requests.exceptions.InvalidSchema: No connection adapters were found for 'C:\\Users\\bugas\\Kometa\\config\\posters\\paintings\\new_year.jpg' |
You are using url_poster and providing the value: C:\Users\bugas\Kometa\config\posters\paintings\new_year.jpg
That is not a URL. It has no http [the schema], and so produces an InvalidSchema error.
You need to use file_poster if you are going to use a file path for the poster.
antwanchild used !aenh
@fossil basin, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.
Yah im trying to get https://github.com/jmxd/Kometa overlays to work but only the resolutions/audience ratings show up, the editions video/audio formats dont appear. is there a missing config to this?
You probably have missing files. That is not a file maintained by the Kometa staff
Are your files named using the TRaSH standards?
You could maybe speak to jmxd about any queries in the thread
https://discord.com/channels/822460010649878528/1248134055527059496
antwanchild used !aenh
@fossil basin, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.
so i somehow messed up and accidentally put mass_content_rating_update: mdb_content_rating_us_movie in the config which ended up with it like in the screen shot.
tried putting it back to mass_content_rating_update: mdb
but it wont revert
Probably need to see a log of this “won’t revert”
i just get no item edits
📝 If you want to review this again, .bugas:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
**User Info**
Author of Linked Message: bugas
Person who Invoked the Command: bugas
File Name: meta.log
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Plex Configuration - Section 3
Page 08: Rec 01 - ❌🔒 BLANK API KEY ERROR
Page 09: Rec 02 - ❌ MY ANIME LIST CONNECTION ERROR
Page 10: Rec 03 - ⚠️ [WARNING]
Page 1/10
ran the reset attribute and that worked. but mdb mdb_commonsense or anything else apply. just says no item edits
nm none of the attributes do anything now
📝 If you want to review this again, antwanchild:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
**Rec 01** - ❌🔒 **BLANK API KEY ERROR**
❌🔒 BLANK API KEY ERROR
An API key is required for certain services, and it appears to be blank in your configuration.
Make sure to provide the required API key to enable proper functionality.
For more information on configuring API keys, [https://kometa.wiki/en/latest/config/trakt/?q=api]
In the Kometa discord thread, type !wiki for more information and search for the service with the missing apikey
2 line(s) with BLANK API KEY errors. Line number(s): 293, 26979
Page 8/10
@fossil basin the way you have the schedule, is the reason why mdb isn't happening. Kometa is already running daily, no need to tell those items to run daily
for this, i would remove the schedule and try again
I agree that the schedule is not needed [no specified schedule is the same as daily], but I don't think that's what's causing this since the operations do seem to be running.
Are you using a paid mdblist key?
antwanchild used !aenh
@fossil basin, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.