calm nest
12/17 Kometa stopped running and began throwing "sub-attribute apikey is blank" in the logs for TMDB/Notifiarr. All API fields that are relevant are filled and validated but it is also showing failures for ntfy and Gotify which I do not use.
I've taken a backup of the config and attempted rebuilding from scratch with no luck, including removing the Docker containers for both Quickstart and Kometa proper and reinstalling. I've attached my redacted config.yaml and meta.log.
maiden marlinBOT
Welcome @calm nest!
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.
maiden marlinBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
marble rover
The config that generated that log [a redacted copy of which is included in the log] is not the config that you have uploaded here.
calm nest
that was the config that downloaded via quickstart when I clicked "download redacted config"
marble rover
The config that generated the log looks like an unmodified copy of the template config.
marble rover
that was the config that downloaded via quickstart when I clicked "download reda...
Sure, but that downlaoded config is not being used by Kometa in that log.
You will need to copy that downlaoded config into your active Kometa config folder.
calm nest
is there anything that i should look into? up until 12/17 everything was fine and it ran normally at 5am every morning. I just noticed last night it hadnt been running.
there is nothing but the template file showing in the Kometa container paths, its like it isnt making it from Quickstart to the Kometa container
marble rover
The config that Kometa is using appears to be an unmodified copy of the default config template.
Until that is addressed Kometa will continue to produce this error.
You need to replace that template config with your desired, complete config.
marble rover
there is nothing but the template file showing in the Kometa container paths, it...
Right, you need to move it there. Neither Kometa nor Quickstart will do that for you.
calm nest
it did previously though
i never moved configs around, quickstart took me through it start to finish
marble rover
Quickstart has an embedded version of Kometa that will run Kometa using the generated config.
This Kometa instance does not appear to be that embedded one, so it is using the standard config template.
Quickstart will not install a config in some random Kometa instance located elsewhere.
calm nest
i do not understand what changed after 12/17 then because i've only ever used QS. It was only today that i removed the container and reinstalled in an effort to reset things
i was under the impression i needed the base Kometa container in addition to quickstart, i can remove that then
marble rover
OK, the container that you created today. You have mapped a folder into that container as /config, correct?
calm nest
yes, the standard docker image via Unraid
marble rover
That doesn't answer the question I asked.
You have mapped a folder into that container as /config, correct?
marble rover
The screenshot shows a different folder from that config
calm nest
thats what was there originally and that was what was there when i pulled the container today
marble rover
OK, that doesn't change the fact that these are not the same folder:
/mnt/docker_cache/Kometa-Quickstart
and
/mnt/docker_cache/Kometa-Quickstart/config
You will have a file at /mnt/docker_cache/Kometa-Quickstart/config.yml.
What is in that file?
calm nest
i'm not disagreeing, just trying to follow what you're looking for.
and yes i do see my config in the root
marble rover
None of this is matching the log above.
I expect to see a config.yml there.
That's what the config details you have shown would point to.
calm nest
i dont understand how
marble rover
Oh, this embedded Kometa makes things so needlessly complex.
calm nest
is it because the command generated by QS is off? its looking deeper into the folder tree for it
im not sure why i didnt catch that earlier, i was blind to it
marble rover
Oh, wait, that log isn't from Docker, so the container you created has nothing to do with this.
Tha command line doesn't match the log above either.
calm nest
is it a bug in QS then?
marble rover
Nothing here makes any sense, so I can't say.
calm nest
that makes 2 of us
marble rover
@chilly fiber What's going on here?
The log above says:
[INFO] | Using /config/kometa/config/config.yml as config
That doesn't match the command line shown here:
The multiple levels of config folders isn't helping.
This error is happening because Kometa is not using the config that you are generating with Quickstart.
That's apparent because the config that generated the log did not come from Quickstart:
calm nest
i can manually move my config to that folder path and take a crack at it if you think that would help
still doesnt answer why the pathways in the generated command got all hinky sometime in the last 7 days
marble rover
It's counterproductive to go back in time and do forensics on what might have happened.
The specific reason for this specific error is clear.
How this system got into this state is not.
My recommendation would be to set up a regular Kometa container, then drag your generated config into that container's config folder and name it config.yml.
Point that container at a new empty directory, not anything to do with Quickstart.
calm nest
i appreciate the help, i'll have to work on that