thorn nestBOT
Welcome @tough nova!
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.
thorn nestBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
Hello,
I am attempting to use Kometa on Linux Mint with Docker. I am also using Plex in docker. I believe that I have followed all of the instructions correctly but none of my changes are being reflected on my Plex page.
When examining my Kometa Docker log, the only things that appear to be of consequence is
"2024-10-31 06:54:25
2024-10-31 06:54:26 [custom-init] No custom files found, skipping...
2024-10-31 06:54:26 [ls.io-init] done."
I am including my 2 log files minus API keys. Please let me know what the problem is!
dim basin
It seems to be behaving as expected.
It's waiting until 3AM to run, and the last line in that log indicates that it will run in about 7 hours:
| Current Time: 19:59 | 7 Hours and 1 Minute until the next run at 03:00 | Runs: 03:00
None of this has anything to do with Kometa:
2024-10-31 06:54:25 [migrations] started
2024-10-31 06:54:25 [migrations] no migrations found
2024-10-31 06:54:25 usermod: no changes
2024-10-31 06:54:25 ───────────────────────────────────────
2024-10-31 06:54:25
2024-10-31 06:54:25 ██╗ ███████╗██╗ ██████╗
2024-10-31 06:54:25 ██║ ██╔════╝██║██╔═══██╗
2024-10-31 06:54:25 ██║ ███████╗██║██║ ██║
2024-10-31 06:54:25 ██║ ╚════██║██║██║ ██║
2024-10-31 06:54:25 ███████╗███████║██║╚██████╔╝
2024-10-31 06:54:25 ╚══════╝╚══════╝╚═╝ ╚═════╝
2024-10-31 06:54:25
2024-10-31 06:54:25 Brought to you by linuxserver.io
2024-10-31 06:54:25 ───────────────────────────────────────
2024-10-31 06:54:25
2024-10-31 06:54:25 To support the app dev(s) visit:
2024-10-31 06:54:25 Kometa: https://github.com/sponsors/meisnate12
2024-10-31 06:54:25
2024-10-31 06:54:25 To support LSIO projects visit:
2024-10-31 06:54:25 https://www.linuxserver.io/donate/
2024-10-31 06:54:25
2024-10-31 06:54:25 ───────────────────────────────────────
2024-10-31 06:54:25 GID/UID
2024-10-31 06:54:25 ───────────────────────────────────────
2024-10-31 06:54:25
2024-10-31 06:54:25 User UID: 1000
2024-10-31 06:54:25 User GID: 1000
2024-10-31 06:54:25 ───────────────────────────────────────
2024-10-31 06:54:25 Linuxserver.io version: v2.1.0-ls27
2024-10-31 06:54:25 Build-date: 2024-10-30T05:33:23+00:00
2024-10-31 06:54:25 ───────────────────────────────────────
2024-10-31 06:54:25
2024-10-31 06:54:26 [custom-init] No custom files found, skipping...
2024-10-31 06:54:26 [ls.io-init] done.
That's all part of the linuxserver image.
The official Kometa inage won't have any of that.
The config file seems fine for the most part.
If you want the script to run immediately rather than waiting until 3AM, you can add an env var to the container:
KOMETA_RUN = True
Then the script will run immediately when the container starts and when finished the container will exit.
One final note, we will generally recommend you use the official image rather than any third-party image like LSIO.
tough nova
Thanks. I will change to the official image. Based off of my config file though, I would expect that things will change immediately once the script it run? Is that correct?
dim basin
That has nothing to do with the config.yml.
Kometa can run is two ways:
Those are controlled by env vars or runtime flags, and the same config works either way.
tough nova
ok i just downloaded the official image and ran it and it gave a lot of outputs but still no change on my plex interface.
trim owl
if you didnt tell kometa to run right now, this is expected
by default it waits until 5am to do its run
dim basin
That's still the LSIO image [according to that log, which looks like the same one as before], and it's still waiting to run
You need to add an env var to the container in order to tell Kometa to run immediately.
Nothing's going to show up in Plex until the config gets processed, which as you have it set up won't happen for another 7 hours.
Have you gone through the docker walkthrough in the wiki? That should give you results immediately as you go through the demo steps.
https://kometa.wiki/en/nightly/kometa/install/docker/
tough nova
It actually uploaded the old kometa log. I will replace it shortly.
potent bobcatBOT
Thanks for using Kometa
tough nova
ok here is the updated log
im running kometateam/kometa:latest image
frigid rose
ok here is the updated log
im running kometateam/kometa:latest image
There might be some bad formatting in your mal config section. It doesn't look like the client_secret is being redacted correctly (so you probably want to delete this log).
client_id: (redacted by Luma)
client_secret:XXXXXXXXXXXXXXXXX```
From the config you posted there might be a missing space between the ":" and "X" (where your config secret actually is)ok so I should recheck the spacings in the file?
frigid rose
I would just add a space there if there isn't and rerun
tough nova
ok let me try that
it seems to have done something!
its caching my library right now
frigid rose
That's a good sign then. You probably still should delete that last log above. I don't use mal but I assume that client secret is something unique to you and meant to be kept private.
tough nova
ok deleted it
potent bobcatBOT
antwanchild used !aenh
@tough nova, 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.