celest baneBOT
Welcome @amber sorrel!
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.
celest baneBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
The following was shared by @amber sorrel and was automatically redacted by Luma as it may have contained sensitive information.
If you feel this message should not have been redacted, resend it with !noredact in your message to avoid redaction.
here is my yaml
Movies:
collection_files:
- file: config/movies.yml
TV Shows:
collection_files:
- file: config/tv shows.yml
Anime:
collection_files:
- file: config/anime.yml
Anime Movies:
collection_files:
- file: config/anime movies.yml
plex:
url: http://192.168.68.61:32400
token: (redacted by Luma)
timeout: 60
db_cache:
clean_bundles: false
empty_trash: false
optimize: false
tmdb:
apikey: (redacted by Luma)
language: en
it says line 11, column 16 \t cannot start any token
The following was shared by @amber sorrel and was automatically redacted by Luma as it may have contained sensitive information.
amber sorrel
Movies:
collection_files:
- file: config/movies.yml
TV Shows:
collection_files:
- file: config/tv shows.yml
Anime:
collection_files:
- file: config/anime.yml
Anime Movies:
collection_files:
- file: config/anime movies.yml
plex:
url: http://192.168.68.61:32400
token: (redacted by Luma)
timeout: 60
db_cache:
clean_bundles: false
empty_trash: false
optimize: false
tmdb:
apikey: (redacted by Luma)
language: en```
!noredact
proven terrace
it says line 11, column 16 \t cannot start any token
\t is a tab character. YAML does not allow tabs. This is not a Kometa thing specifically.
amber sorrel
k gotcha thanks, i am using notepad so that doesnt help
proven terrace
I'd suggest moving to a YAML-aware editor.
amber sorrel
will do, could u tell me why its not refreshing missing metadata?
Refresh Metadata:
plex_search:
all:
episode_air_date: 7
item_refresh: true
build_collection: false
test: true``` TV Shows:
collection_files:
- file: config/tv shows.yml
Anime:
collection_files:
- file: config/anime.yml
plex:
url: http://192.168.68.61:32400
token: key
timeout: 60
db_cache:
clean_bundles: false
empty_trash: false
optimize: false
verify_ssl:
tmdb:
apikey: key
language: en
cache_expiration: 60
region:
settings:
run_order:
- operations
- metadata
- collections
- overlays
cache: true
cache_expiration: 60
asset_directory:
asset_folders: true
asset_depth: 0
create_asset_folders: false
prioritize_assets: false
dimensional_asset_rename: false
download_url_assets: false
show_missing_assets: true
show_missing_season_assets: false
show_missing_episode_assets: false
show_asset_not_needed: true
sync_mode: append
default_collection_order:
minimum_items: 1
item_refresh_delay: 0
delete_below_minimum: false
delete_not_scheduled: false
run_again_delay: 0
missing_only_released: false
only_filter_missing: false
show_unmanaged: true
show_unconfigured: true
show_filtered: false
show_options: false
show_missing: true
save_report: false
tvdb_language: default
ignore_ids:
ignore_imdb_ids:
playlist_sync_to_users: all
playlist_exclude_users:
playlist_report: true
custom_repo:
overlay_artwork_filetype: jpg
overlay_artwork_quality:
!noredact
proven terrace
It appears that nothing meets the criteria:
|=============================== Running Refresh Metadata Collection ================================|
| |
| Sync Mode: append |
| |
| Builder: plex_search: (2, "Plex Show Search\nSort By: ['title.asc']\nFilter:\n Match all of the following:\n Episode Air Date is in the last 7d Days", '?type=2&sort=titleSort&episode.originallyAvailableAt%3E%3E=-7d') |
| |
| Processing Plex Show Search |
| Sort By: ['title.asc'] |
| Filter: |
| Match all of the following: |
| Episode Air Date is in the last 7d Days |
| |
| 3 IDs Found |
| |
| |
|=========================== Items Found for Refresh Metadata Collection ============================|
| |
| |
|================== Updating Metadata of the Items in Refresh Metadata Collection ===================|
| |
| |
|====================================================================================================|
| Finished Refresh Metadata Collection |
| Collection Run Time: 0:00:00 |
i have an episode for an anime that was released yesterday and is missing metadata
proven terrace
I'm just reading the logs.
Possibly, since the thing has no metadata, Plex has no idea what the episode air date is. Perhaps try searching for things added to Plex in the last few days?
You could also turn on "show_missing" and maybe the log will show what those "## IDs Found" are.
The Anime library shows the same thing, BTW:
As another test, what do you get if you do this search directly in Plex:
Episode Air Date is in the last 7d Days
it shows the correct stuff that was aired in the last 7 days, including the show missing metadata im troubleshooting
amber sorrel
You could also turn on "show_missing" and maybe the log will show what those "##...
is that this in the config?
show_missing_episode_assets: true
amber sorrel
oh nvm i found show_missing: true it was true alreaduy
proven terrace
Not sure. Seems like Kometa's Plex search isn't turning anything up.
amber sorrel
how would i do this in the config to test?
Perhaps try searching for things added to Plex in the last few days?
proven terrace
how would i do this in the config to test?
`Perhaps try searching for things a...
Change the plex_search.
plex_search:
all:
episode_air_date: 7 <<< CHANGE THIS
hmm, seems like the same logs more or less
celest baneBOT
proven terrace
Maybe try show_filtered: true
amber sorrel
no good. it says its getting 17 ids which is the correct number from plex when i filtered in the webui. but its not refreshing the metadata. i feel like there is a disconnect between my anime.yml and config.yml myself.
now im getting /assets does not exist either after running posterizarr
celest baneBOT
proven terrace
Are you mapping a directory into the docker container at /assets? If not that message is totally expected and has nothing to do with posterizarr.
amber sorrel
yep sure did
amber sorrel
oh ya might not have done that let me recreate
proven terrace
what does docker exec kometa ls -al / show?
I suspect it will show no /assets there
amber sorrel
restarted container, still doesnt work. it is in there as well
proven terrace
You're still getting a message that /assets doesn't exist?
amber sorrel
yep
proven terrace
¯_(ツ)_/¯ permissions, maybe
celest baneBOT
celest baneBOT
celest baneBOT
clear hull
do each of these exist:
asset_directory: /assets/TV Shows
asset_directory: /assets/Anime
asset_directory: /assets/Movies
asset_directory: /assets/Anime Movies
if they do, i wonder if the additional mapping is causing confusion with Kometa?
i just have my Kometa mapped to /config and from there i use config/assets/movies for my asset directory
amber sorrel
do each of these exist:
` asset_directory: /assets/TV Shows`
` asset_d...
i moved it to /config/assets and that fixed it right up. thanks for the help there buddy.
u wouldnt happen to know why i cant get refresh metadata working would u?
celest baneBOT
proven terrace
Can't reproduce this:
collections:
Refresh Metadata:
plex_search:
all:
episode_added: 42
item_refresh: true
build_collection: false
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
proven terrace
My log looks the same as yours, it doesn't list the things it's refreshing metadata for, but if I watch Plex it refreshes the metadata on everything in that search.
They also show up in the Plex log:
and as evidence it's actually doing something, before and after
celest baneBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
The following was shared by @amber sorrel and was automatically redacted by Luma as it may have contained sensitive information.
its got to be something with my config, no?
amber sorrel
ive tried what bullmoose has in is as well (the git tv refresh) that doesnt work either
proven terrace
I would think it's something with Plex; there's not much in the config here.
clear hull
@amber sorrel this is what i use, and have no issues yaml collections: Refresh Metadata: plex_search: all: episode_air_date: 30 #7 item_refresh: true build_collection: false
celest baneBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
celest baneBOT
The following was shared by @amber sorrel and was automatically redacted by Luma as it may have contained sensitive information.
If you feel this message should not have been redacted, resend it with !noredact in your message to avoid redaction. See attached file for redacted content.
The following was shared by @amber sorrel and was automatically redacted by Luma as it may have contained sensitive information.
amber sorrel
ive tried everything
used bullmoose git, used collection refresh metadata, checked config up and down
celest baneBOT
proven terrace
I really don't think there's anything in the config here, since there's not much there and it seems to be running without error. Nothing appears in the Plex log when you run this?
I would do a run with --log-requests; if your log then looks like this:
|================== Updating Metadata of the Items in Refresh Metadata Collection ===================|
| |
| http://192.168.1.11:32400 "PUT /library/metadata/15306/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/14798/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/15230/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/15429/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/14567/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/14488/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/14524/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/15400/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/15203/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/15175/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/14986/refresh HTTP/1.1" 200 0 |
| http://192.168.1.11:32400 "PUT /library/metadata/14616/refresh HTTP/1.1" 200 0 |
Kometa is doing everything it is supposed to do and if Plex is not actually refreshing metadata on those items there isn't anything that Kometa can do about it.
celest baneBOT
The following was shared by @amber sorrel and was automatically redacted by Luma as it may have contained sensitive information.
im not getting anything with --log-requests like ur screenshot. this should be getting refreshed. this is command im running
docker run --rm -it -v "/docker-appdata/kometa/config:/config:rw" kometateam/kometa --run --log-requests
amber sorrel
i changed the 7 to 14 as it is past 7 days and that did nothing as well
so it looks like
Refresh Metadata:
plex_search:
all:
episode_air_date: 14
item_refresh: true
build_collection: false```You have that collection definition in your config; it doesn't belong there and no one is paying attention to it there. That's why no metadata is being refreshed in this run.
This:
collections:
Refresh Metadata:
plex_search:
all:
episode_air_date: 14
item_refresh: true
build_collection: false
Needs to be in its own yaml file like reitenth.yml and that file has to be referenced in the config as:
libraries:
Anime:
operations:
assets_for_all: true
collection_files:
- file: config/reitenth.yml
settings:
asset_directory: config/assets/Anime/
This is not correct:
Anime:
operations:
assets_for_all: true
collections: ## < none
Refresh Metadata: ## < of
plex_search: ## < this
all: ## < belongs
episode_air_date: 14 ## < here
item_refresh: true ## < in
build_collection: false ## < config.yml
settings:
asset_directory: config/assets/Anime/
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
proven terrace
You used to have it set up correctly, but you have made changes that are preventing it from working at all.
This is correct:
<#1260288885833859165 message>
The config shown in this log is not:
<#1260288885833859165 message>
amber sorrel
ok it seems to be running now but its not touching my test file.
the shy episodes id is 18382
proven terrace
So Kometa is issuing the metadata refresh requests to Plex successfully [22 of them]. From that point it's entirely in Plex' court and Kometa cannot do any more.
clear hull
ok it seems to be running now but its not touching my test file.
the shy episo...
!afnh
gritty adderBOT
Anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.