dire jungleBOT
Welcome @golden echo!
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.
dire jungleBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
The following was shared by @golden echo 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.
I am getting the following error once I switched everything over to the new location kometateam/kometa:nightly. I dont think this is kometa related but not sure why switching over would cause this.
Apr 28 22:19:49 Hades nginx: 2024/04/28 22:19:49 [error] 10026#10026: *1250717 connect() to unix:/var/tmp/Kometa.sock failed (111: Connection refused) while connecting to upstream, client: XXXXX, server: XXXX.myunraid.net, request: "GET /logterminal/Kometa/ws HTTP/1.1", upstream: "http://unix:/var/tmp/Kometa.sock:/ws", host: (redacted by Luma)
craggy umbra
Not even sure why the need to kometa on traefik
cloud merlin
Kometa isn't listening on any port, so I'm not sure what you'd be using traefik for in this context. Can you say more about out what you're doing?
golden echo
Honestly your guess is as good as mine. I checked Traefik and PMM wasn’t using it as expected. But switching over to Kometa when I try launching the console it crashes after about 45 seconds and that’s what I get in my unraid log.
cloud merlin
Nothing there is anything Kometa is doing, so ¯_(ツ)_/¯
Kometa doesn't use nginx, doesn't provide anything nginx could connect to, etc.
golden echo
Does kometa perform differently under a private network?
That’s the only other thing I can think of, as I have everything running under a private network
PMM worked fine, just changed the rebrand stuff and now it’s doa unfortunately
cloud merlin
Kometa only makes outbound connections to Plex and other services; I don't think it cares about that. All basic python requests stuff.
cloud merlin
PMM worked fine, just changed the rebrand stuff and now it’s doa unfortunately
There haven't been any code changes around any of this in the rebrand.
golden echo
Just noticed this in the docker log that coincides with it crashing and the nginx error
On the 4th each time it crashes the docker
cloud merlin
That came up before, and I can't recall the fix; searching for the error will probably turn it up.
I think there's a string replace going insane and exhausting memory, but this is not an all-the-time result. Also not sure how the rebrand is related, but it seems to be somehow.
golden echo
I’ll search, develop and nightly are doing the same thing for me
That was the fix, so if people see nginx errors too it’s the same problem
craggy umbra
what was the fix?
cloud merlin
I recall it being something non-intuitive
golden echo
I deleted all the env. Variable commands I wasn’t using (named PMM) and changed the ones I was using from PMM to KOMETA
craggy umbra
nice
craggy umbra
I deleted all the env. Variable commands I wasn’t using (named PMM) and changed ...
!afnh
rancid glenBOT
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.